First-time errors
What a new user meets first, what the tool answers (kind) and exactly what to do. Every such answer carries this section's link in its hint.
kind | What happened | What to do, in order |
|---|---|---|
sign_in | The connector has no valid sign-in for this request (expired, revoked, or never completed) | In Claude: Customize → Connectors → Yours → Reconnect on Krusgraph, and finish the Microsoft sign-in with your work account. If it loops, your organisation requires multi-factor authentication for new apps: complete it when asked. |
consent | Your Microsoft Entra organisation has not consented to the app (Entra AADSTS65001), or the tool needs a permission the app has not been granted | Send your Entra admin the consent link on /start (it opens Microsoft's own page); after they click Accept, disconnect and reconnect the connector. For create_semantic_model, create_ontology, create_data_agent, create_silver_notebook and create_drift_monitor the answer names the missing scope (such as Item.ReadWrite.All or SemanticModel.ReadWrite.All); that is a permission the operator adds to the app, see docs/SCOPES.md; the dry runs work meanwhile. |
no_access | You can sign in, but this workspace or item is not shared with you (HTTP 403) | Ask the workspace owner for a role on the workspace: Viewer is enough for everything that reads and plans, Contributor for create_backend, create_views and the other creating tools. Then run the same request again; list_workspaces shows what you can see. |
capacity | The workspace has no active Fabric capacity (paused, not assigned, or expired trial) | In Fabric: Workspace settings → License info, assign a capacity or resume the paused one; a trial capacity is enough. Lakehouse SQL endpoints answer again a minute after the capacity is up. |
schema_not_found | The schema has no tables for this sign-in | A lakehouse without "Lakehouse schemas" has everything in dbo; one created with schemas has them by name (list_tables with another schema). Tables created minutes ago are not in the SQL analytics endpoint yet: open the endpoint in Fabric and refresh its metadata, then try again. |
sql_sign_in | The SQL analytics endpoint refused the token | Reconnect the connector; if it persists, the account lacks access to the item itself (share the lakehouse or warehouse, not only the workspace). |
Everything else (not_found, timeout, throttled, bad_input, …) is explained in the answer itself; the format is the same three fields.