Microsoft Fabric
Lets agents list and work with Fabric workspaces, lakehouses, warehouses and items through a service principal.
Connect it with: Service account. Microsoft Fabric's own documentation: https://learn.microsoft.com/en-us/rest/api/fabric/articles/get-started/create-entra-app.
What agents can do
Connect Microsoft Fabric so the agents working your tasks can reach it. With it connected, they can:
- List the workspaces the service principal is a member of, and the items in each (lakehouses, warehouses, notebooks, pipelines, semantic models).
- Create, update or delete Fabric items in workspaces where the service principal holds the Contributor role or higher.
- Run notebooks and data pipelines on demand and poll their job status.
- Read item definitions to review or version a notebook or pipeline.
Before you start
- A Microsoft Fabric capacity (trial, F SKU or Power BI Premium P SKU) and a workspace on it.
- An app registration in Microsoft Entra ID with a client secret: Azure portal > Microsoft Entra ID > App registrations > New registration.
- A Fabric administrator who checks Admin portal > Tenant settings > Developer settings > Service principals can call Fabric public APIs is on for the app (scope it to a security group the app belongs to). Creating workspaces or connections also needs Service principals can create workspaces, connections, and deployment pipelines.
- The app added to each workspace agents should reach: open the workspace > Manage access > Add people or groups, search for the app's name, and give it Contributor (Viewer is enough for read-only work).
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Microsoft Fabric
Jaah connects to Microsoft Fabric with a service account, not with a sign-in button.
Connect with an API key
Find each value first:
- Tenant ID: Azure portal > Microsoft Entra ID > Overview > Tenant ID (a GUID, or a domain such as yourcompany.onmicrosoft.com).
- Client ID: Azure portal > Microsoft Entra ID > App registrations > your app > Overview > Application (client) ID.
- Client secret: Your app > Certificates & secrets > Client secrets > New client secret; copy the Value column (not the Secret ID) right after creating it.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Microsoft Fabric card.
- Name the secret and choose who can use it.
- Fill in Tenant ID, Client ID, Client secret.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Microsoft Fabric with a service account, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah first signs in at POST https://login.microsoftonline.com/<Tenant ID>/oauth2/v2.0/token with the client ID and secret, then calls Microsoft Fabric's API once with the token it got back (GET https://api.fabric.microsoft.com/v1/workspaces), and shows whether Microsoft Fabric accepted it, or which value Microsoft Fabric refused and the status it answered. Jaah also tests automatically when you save or reconnect.
The last result and its time stay on the secret's page, so you can see whether it still works without testing again.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: tenant_id, client_id, client_secret.
Tell the agent in your task description which secret to use, for example “use the Microsoft Fabric secret org/microsoft-fabric”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Microsoft Fabric once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Microsoft Fabric's side too, delete the service account's key in its cloud console.
Limitations
- A service principal sees only the workspaces it was added to; My workspace is never reachable.
- Some Fabric APIs do not support service principals yet; Microsoft lists the supported identities on each API's reference page.
- Client secrets expire (at most two years); create a new one and replace it in Jaah before the old one lapses.
- Agents can do only what the connected Microsoft Fabric service account and its roles allow.
Troubleshooting
Test says Microsoft Fabric rejected the client ID and client secret (400) or (401) - check both
The tenant, client ID or secret is wrong, or the secret expired. Check the Tenant ID on Microsoft Entra ID > Overview, the Application (client) ID on the app's Overview, and paste the secret's Value (not its Secret ID).
Test says Microsoft Fabric rejected the access token it issued (401) or (403)
Entra issued a token but Fabric refused the app. Turn on Service principals can call Fabric public APIs in Admin portal > Tenant settings > Developer settings, and make sure the app is in the security group that setting names. The change can take up to 15 minutes to apply.
The Test passes but agents see no workspaces
The app is not a member of any workspace. Open each workspace > Manage access > Add people or groups and add the app with Contributor or Viewer.
Still stuck? Select Test and read the result: it names the value Microsoft Fabric refused and the status it answered.
FAQ
Why a service principal and not a sign-in button?
A service principal keeps working when the person who set it up leaves or changes their password, and its access is limited to the workspaces you add it to. Fabric supports it for unattended automation, which is how agents work.
Can I reuse the app registration I use for Power BI?
Yes. One app registration can serve both; add a Microsoft Fabric secret and a Power BI secret that carry the same values, and turn on each product's service principal tenant setting.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Microsoft Fabric account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.