Microsoft Power BI

Query semantic models in Power BI with natural language, run DAX, and read model and report metadata

Power BI comes as two complementary connectors:

  • Microsoft Power BI connects your assistant to Microsoft's official Power BI Model Context Protocol server. The assistant runs DAX queries, reads the model schema (tables, measures, relationships), and retrieves report metadata.
  • Microsoft Power BI Discovery finds your content: it lists workspaces, semantic models, reports, report pages, and dashboards with their IDs. The query tools need a semantic model ID as input — Discovery is how the assistant finds the right one without you pasting IDs from URLs.

Connect both for the best experience: Discovery finds the model, the query connector answers questions about its data.

Access is read-only and runs in the context of the signed-in user. Your Power BI workspace permissions and the model's row-level security continue to apply.

When to Use

Ideal for:

  • Asking for metrics from a semantic model in natural language
  • Having DAX queries drafted and executed
  • Understanding the model schema: tables, columns, measures, and relationships
  • Reading report metadata
  • Finding workspaces, models, reports, and dashboards and their IDs (Discovery)

Not suited for:

  • Writing changes to models, reports, or data (access is read-only)
  • Models you do not have Build permission on

Requirements

  1. A Fabric/Power BI tenant where an administrator has enabled the tenant setting "Users can use the Power BI Model Context Protocol server endpoint (preview)"
  2. Build permission on the semantic model you want to query
  3. A Microsoft account to connect

The Discovery connector only needs the Microsoft account — it works without the tenant preview setting.

Note

The Power BI MCP server is a Microsoft preview feature. Its scope and behavior may still change on Microsoft's side.

Setup

Enable the tenant setting: A Fabric/Power BI tenant admin enables "Users can use the Power BI Model Context Protocol server endpoint (preview)" in the admin portal.

Ensure Build permission: You need Build permission on the semantic model.

Enable the connector: Select Power BI under the connectors in the assistant editor and save the assistant.

Connect: Click "Connect" in the "Connectors" dialog or under "Connections" and sign in with your Microsoft account. Depending on tenant policy, admin consent may be required.

Note

There is nothing to configure beyond the toggle: meinGPT connects to Microsoft's Power BI MCP server using a Microsoft app that meinGPT registers and maintains — you do not create an Azure AD app registration or enter a Tenant ID, Client ID, or Client Secret. Each person who wants to use the connector signs in individually under "Connections" (step 4); an org admin only turns the connector on for the assistant.

Available Features

Query models

"What was revenue per region last quarter?"
"Show me the top 5 products by gross margin"

Run DAX

"Run a DAX query that returns revenue per month for 2025"

Read schema and metadata

"Which tables and measures exist in this model?"
"How are the 'Sales' and 'Customers' tables related?"

Discover content (Discovery connector)

"Which Power BI datasets do I have access to?"
"List the reports in the Sales workspace"

Permissions

  • Access is read-only
  • Tool calls run with the signed-in user's permissions
  • The model's workspace permissions and row-level security apply

Privacy and Security

  • Authentication uses your Microsoft account
  • meinGPT stores no Microsoft passwords; the access token is stored encrypted
  • All data is transmitted encrypted
  • You can revoke the connection at any time under "Connections" in meinGPT or in your Microsoft account settings

Troubleshooting

Tool fails to load, or errors when the assistant tries to use it

  • Check Requirement 1: a Fabric/Power BI tenant admin must enable "Users can use the Power BI Model Context Protocol server endpoint (preview)" in the Power BI admin portal. Without it, calls to Microsoft's MCP server fail even after you've connected your Microsoft account.
  • Check that you (or the person testing the assistant) have clicked "Connect" under "Connections" and completed Microsoft sign-in — enabling the connector on the assistant (step 3) does not connect any account by itself.
  • Confirm you have Build permission on the semantic model you're querying.

If "Microsoft Power BI Discovery" works but "Microsoft Power BI" doesn't, the tenant setting from Requirement 1 is the most common cause — Discovery doesn't need it.

Was this page helpful?