Items marked (preview) in this article are currently in public preview. This preview is provided without a service-level agreement, and we don’t recommend it for production workloads. Certain features might not be supported or might have constrained capabilities. For more information, see Supplemental Terms of Use for Microsoft Azure Previews.
For information on optimizing tool usage, see best practices.
Usage support
| Microsoft Foundry support | Python SDK | C# SDK | JavaScript SDK | Java SDK | REST API | Basic agent setup | Standard agent setup |
|---|---|---|---|---|---|---|---|
| Fabric IQ | ✔️ | ✔️ | ✔️ | — | ✔️ | ✔️ | ✔️ |
Prerequisites
Virtual network (VNet) integration is not supported. Your Foundry project must not use a VNet-restricted endpoint.
Fabric IQ isn’t available in regions where Power BI is the only Fabric workload. Confirm your Fabric workspace is in a region that supports the full Fabric stack — see Microsoft Fabric region availability.
- A Microsoft Fabric license that grants access to the Fabric items your agent queries. Users who invoke Fabric IQ through your agent must also have this license.
- An active Microsoft Foundry project with a deployed model.
- Azure RBAC roles:
- Foundry User role on the Foundry project for the developer identity, the agent’s runtime identity, and any user identity involved in OAuth flows.
- Foundry Project Manager role on the Foundry project for creating a Foundry connection to the Fabric IQ endpoint.
- Foundry Toolkit: Install Visual Studio Code and Foundry Toolkit for Visual Studio Code.
How it works
- Your agent dispatches a tool call — When the agent model identifies a task that requires Fabric data, it emits a tool call to the
fabric_iq_previewtool. - Fabric IQ processes the request — Fabric IQ receives the natural-language query and routes it based on the target item type:
- Ontology — The Natural Language to Ontology (NL2Ontology) layer converts the query into a structured ontology query against your enterprise entities, relationships, and data bindings.
- Fabric data agent — The query goes directly to the data agent for conversational Q&A over ontology-grounded data.
- Power BI semantic models — Fabric IQ queries the semantic model’s measures and hierarchies to return analytics results.
- The result is returned to your agent — Fabric IQ returns the synthesized response. Your agent incorporates it into its reply to the user. All requests run in the context of the signed-in user and honor Fabric permissions and governance policies.
Connect to Fabric IQ
Find your Fabric IQ server details
Fabric IQ exposes different MCP endpoint URLs depending on the type of Fabric item you’re connecting to. The value you supply asserver_url follows one of these patterns:
| Fabric item type | server_url pattern | Supported authentication |
|---|---|---|
| Power BI semantic model | https://{host}/v1/mcp/fabricaihub/integrations/m365 | BYO Entra app, managed OAuth |
| Ontology | https://{host}/v1/mcp/dataPlane/workspaces/{workspaceId}/items/{itemId}/ontologyEndpoint | BYO Entra app |
| Data agent | https://{host}/v1/mcp/workspaces/{workspaceId}/dataagents/{dataAgentId}/agent | BYO Entra app, managed OAuth |
{host}— The Fabric API host, typicallyapi.fabric.microsoft.com{workspaceId}— The GUID of your Microsoft Fabric workspace{itemId}/{dataAgentId}— The GUID of the specific Fabric item
For Power BI semantic models, we recommend restricting the tool surface with
allowed_tools so the agent reasons over the schema and runs queries directly instead of pre-generating DAX. Set allowed_tools to:GetInstructionsDiscoverArtifactsGetReportMetadataGetSemanticModelSchemaExecuteQueryValueSearch
GenerateQuery. This list lets the agent discover artifacts, inspect the semantic model schema, execute queries, and search for values, without an intermediate query-generation step.server_label, use any short lowercase identifier with hyphens, for example fabriciq-ontology. This label appears in approval prompts when the model calls the tool.
Add the Fabric IQ tool to your agent
Authentication and security
Fabric IQ uses Microsoft Entra ID delegated authentication (On-Behalf-Of, OBO). All requests run in the context of the signed-in user. Application-only (app-only) authentication isn’t supported. Microsoft Fabric permissions and data governance policies are enforced automatically — Fabric IQ can never surface data that the signed-in user isn’t already permitted to see. The authentication method available depends on the Fabric item type:- Ontology — BYO Entra app only. You must register a dedicated Entra application with Power BI delegated permissions.
- Data agent — BYO Entra app (with data agent scopes) or managed OAuth.
- Power BI semantic model — BYO Entra app or managed OAuth.
Set up your Entra app for ontology (one-time, per organization)
An Entra admin must complete the following steps before you can create a Fabric IQ connection for an ontology item in Foundry.Create the app registration
- Go to the Microsoft Entra admin center. In the left navigation, select Entra ID > App registrations.
- Select New registration. Give the app a descriptive name and set Supported account types to Accounts in this organizational directory only. Select Register.
- Copy the Application (client) ID. You need this value when creating the Foundry connection.
- Select API permissions > Add a permission > Microsoft APIs. Find and select Power BI Service, select Delegated permissions, and add the following permissions:
Item.Execute.AllItem.Read.All

- Select Grant admin consent for {your-organization} in the Configured permissions panel. A Global Administrator must approve. This step allows users in your organization to authenticate through the Fabric IQ connection.
- Select Certificates & secrets > New client secret. Add a description and expiration. Select Add, then immediately copy the secret Value — it’s only shown once.
- Copy your Directory (tenant) ID from the Microsoft Entra ID overview page.
Fill in the Foundry connection values
In Microsoft Foundry, open your project and go to Settings > Connections > New connection > Fabric IQ. Fill in the following fields:| Field | Value |
|---|---|
| Client ID | Application (client) ID from step 3 |
| Client secret | Client secret value from step 6 |
| Authorization URL | https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/authorize |
| Token URL | https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token |
| Refresh URL | https://login.microsoftonline.com/{tenant-id}/oauth2/v2.0/token |
| Scopes | https://analysis.windows.net/powerbi/api/Item.Execute.All,https://analysis.windows.net/powerbi/api/Item.Read.All,offline_access |
{tenant-id} with your Directory (tenant) ID from step 7. Select Save to create the connection.
For data agent connections using BYO Entra, use the
DataAgent.Execute.All delegated permission instead of the Power BI scopes listed above. Add https://analysis.windows.net/powerbi/api/DataAgent.Execute.All as the scope in the Foundry connection, and grant admin consent for that permission in your app registration.Add the redirect URI to your app registration
After Foundry creates the connection, it displays an OAuth redirect URL. Add this URL to your app registration:- In the Microsoft Entra admin center, go to Entra ID > App registrations and select your app.
- Select Authentication > Add a platform > Web.
- Under Redirect URIs, paste the OAuth redirect URL from Foundry.
- Select Configure.
Data governance and compliance
Fabric IQ processes requests within the Microsoft Fabric compliance boundary for your workspace’s region. The following commitments apply when you route agent queries through Fabric IQ.Data residency
Fabric IQ retrieves and processes data within the region where your Microsoft Fabric workspace resides. Data doesn’t cross regional boundaries during query execution. The applicable region and its compliance scope are determined by your workspace location — see Microsoft Fabric region availability for the list of supported regions and the compliance frameworks each region satisfies.If your Foundry project is in a different Azure region than your Fabric workspace, query results are returned cross-region. Review Microsoft Fabric region availability and your organization’s data residency requirements before connecting a Fabric workspace in a different region.
Compliance certifications
Fabric IQ inherits Microsoft Fabric’s compliance certifications for the workspace region. For compliance documentation, audit reports, and the frameworks applicable to each region, see Microsoft Fabric region availability.Admin management
Grant admin consent
A Global Administrator must grant tenant-wide admin consent for the Entra app registration before users can authenticate with the Fabric IQ connection:- In the Microsoft Entra admin center, go to Entra ID > App registrations and select your app.
- Select API permissions.
- Select Grant admin consent for {your-organization} and approve. Each listed permission shows a green checkmark when consent is granted.
DataAgent.Execute.All also requires admin consent. If you use this permission for data agent connections, follow the same process.
Restrict network access
To restrict agent traffic to your private network, configure Foundry Agent Service with a virtual network. See Private networking for agents for setup instructions.Publish Fabric items before use
A Fabric admin must publish each Fabric item — ontology, data agent, or Power BI semantic model — before it can be consumed through Fabric IQ. Unpublished items aren’t reachable at the MCP endpoint, and requests against them fail. Confirm that the item is published in the Microsoft Fabric portal before configuring the Foundry connection.Troubleshoot
| Symptom | Likely cause | Fix |
|---|---|---|
404 or Not Found error when connecting | The server_url is incorrect or the Fabric item isn’t published. | Verify the workspace and item GUIDs in the Fabric portal URL. Confirm the item is published. |
| 401 Unauthorized | Admin consent hasn’t been granted or the Entra app is misconfigured. | Verify admin consent was granted for all required API permissions. Check that the client ID, secret, and scopes match what you configured in Foundry. |
CONSENT_REQUIRED error at runtime | The signed-in user hasn’t completed the OAuth flow for the connection. | Open the consent URL returned in the error, complete the OAuth flow in a browser, then retry. |
| Empty or incorrect results from ontology queries | Ontology entities, properties, or data bindings are incomplete. | Verify the ontology item is published and that entity types, properties, and data bindings are fully configured in Fabric IQ. |
| Poor-quality answers from Power BI semantic models | The model doesn’t have strong enough reasoning for complex measure queries. | Use a latest-generation model such as gpt-5.4 or opus 4.7. These models handle semantic model complexity significantly better than older models. |
| Agent never calls the Fabric IQ tool | The model doesn’t recognize when to delegate to Fabric IQ. | Add guidance in the system prompt, for example: “Use the Fabric IQ tool for any question about business data, entities, metrics, or organizational knowledge.” |