> For the complete documentation index, see [llms.txt](https://docs.natoma.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.natoma.ai/apps/power-bi.md).

# Power BI

{% hint style="warning" %}
**Early Access** — Reach out to your Natoma representative for access.
{% endhint %}

**Type:** Official

**Source Type:** Remote URL

**Source:** <https://api.fabric.microsoft.com/v1/mcp/powerbi>

**Description:** Power BI MCP server provides AI assistants with access to Microsoft Power BI through Microsoft Fabric's remote MCP endpoint. It enables exploring workspaces, datasets, reports, and dashboards through OAuth.

***

## Setup

Microsoft Entra ID does not support OAuth 2.0 Dynamic Client Registration, so an Entra admin must pre-register an application and supply the Client ID and Client Secret to Natoma. A Power BI admin must also enable the MCP tenant setting before users in the tenant can connect.

### Step 1: Enable the Power BI MCP tenant setting

A Microsoft Fabric / Power BI admin must enable the tenant setting that allows users to call the Power BI MCP endpoint.

1. Sign in to the [Power BI / Fabric admin portal](https://app.powerbi.com/admin-portal) as a user with the **Fabric administrator**, **Power Platform administrator**, or **Global administrator** role.
2. Open **Tenant settings** and locate **"Users can use the Power BI Model Context Protocol server endpoint (preview)"**.
3. Toggle it to **Enabled**, optionally scoped to specific security groups, and click **Apply**.

### Step 2: Register an Entra ID application

1. Open the [Microsoft Entra admin center](https://entra.microsoft.com/) and go to **Identity → Applications → App registrations → New registration**.
2. Name the app (e.g. `Natoma Power BI MCP`) and select the appropriate supported account types.
3. Under **Redirect URI**, choose **Web** and enter:

{% hint style="warning" %}
Use exactly this redirect URI — Natoma will not complete the OAuth flow if it doesn't match.
{% endhint %}

```
https://api.natoma.app/mcp/server/callback
```

4. Click **Register**, then copy the **Application (client) ID** from the overview page.

### Step 3: Grant Power BI API permissions

1. In the new app, open **API permissions → Add a permission → Power BI Service → Delegated permissions**.
2. Add the permissions needed for your use case (typically `Dataset.Read.All`, `Report.Read.All`, and `Workspace.Read.All` for read-only access).
3. Click **Grant admin consent for \<tenant>**.

### Step 4: Create a client secret

1. Open **Certificates & secrets → Client secrets → New client secret**.
2. Add a description, choose an expiry, and click **Add**.
3. Copy the secret **Value** immediately — it is only shown once.

### Step 5: Configure the connector in Natoma

1. Log in to Natoma as an Admin, navigate to **Apps**, and search for **Microsoft Power BI**.
2. Click **+** > **Allow Personal Connections**.
3. Enter the **Client ID** from Step 2 and the **Client Secret** from Step 4, then save.
4. Click **Test Connection** to verify the connection.

Each connecting user must also have a Power BI license (Pro, PPU, or access via a Premium capacity) and **Build** permission on at least one semantic model they want to query.