VoiceLake UC Analytics by Metropolis

A governed, read-only connection to VoiceLake data in Microsoft Power BI.

VoiceLake answers bounded analytics questions against a Power BI semantic model that the signed-in user is already permitted to read. It cannot edit Power BI or Fabric, start a refresh or sync, call a UC provider API, or run arbitrary DAX.

Before you connect

Use a Microsoft work or school account with workspace access and Build permission on the semantic model.
The model name must begin with Call Analytics . Other models remain invisible.
During Microsoft sign-in, choose the account that has permission to the intended model.

Connect and select a model

Connect VoiceLake and complete Microsoft authorization.
Ask to list the VoiceLake models you can use.
If more than one is visible, select one explicitly. VoiceLake never silently chooses the first model.

Example requests

Summarize call and contact-center activity for the previous UTC day.
Show the top 20 queues by queued contacts for the last seven days.
Compare supported platform activity for the previous 24 hours.
Show the busiest locations and their answer rates.
Check data freshness or explain a governed metric.

Safety and privacy limits

The default window is one day and the maximum window is 31 days.
The maximum result size is 500 rows.
Results are aggregate by default and include provenance for the selected model and query window.
Phone numbers, email addresses, personal names tied to calls, tokens, internal identifiers, raw query text, and upstream payloads are not returned.
An unavailable metric is reported as unavailable, not as zero.

Disconnect and delete connection state

Remove the VoiceLake connection from your OpenAI product. To revoke Microsoft access, remove the VoiceLake MCP application grant at myapplications.microsoft.com or ask your tenant administrator. To request deletion of remaining connector authorization state, contact Metropolis support.

Support

Visit metropolis.com/support.php or email support2026@metropolis.com. Include the UTC time, connector version, and safe error text. Do not send tokens, customer data, or internal identifiers.