{"id":497,"date":"2026-10-16T11:55:40","date_gmt":"2026-10-16T09:55:40","guid":{"rendered":"https:\/\/dataguide.tech\/?p=497"},"modified":"2026-11-12T23:17:44","modified_gmt":"2026-11-12T22:17:44","slug":"one-prompt-one-workspace-agentic-microsoft-fabric-admin","status":"publish","type":"post","link":"https:\/\/dataguide.tech\/index.php\/2026\/10\/16\/one-prompt-one-workspace-agentic-microsoft-fabric-admin\/","title":{"rendered":"One Prompt, One Workspace: Agentic Microsoft Fabric Admin"},"content":{"rendered":"\n
\n

Status check, verified October 2026.<\/strong> The Fabric Core MCP Server is out of preview: Microsoft listed it as generally available in the September 2026 Fabric update. The tool set is still growing, though. At the time of writing it has no tools for capacity assignment, Git or Spark settings, which is why fab<\/code> and az<\/code> show up below, and the Fabric skills and the Fabric CLI ship updates often. If something here doesn’t behave the way I describe, check the Microsoft Learn docs<\/a> before assuming your setup is broken. I date-stamp every post in this series and update them when things move.<\/p>\n<\/blockquote>\n\n\n\n

If you’re a Fabric admin, you know this message by heart: “Hey, can I get a new workspace?”<\/p>\n\n\n\n

For the person asking, it’s one workspace. For you, it’s a workspace, a repository, a capacity assignment, the Git connection, security groups, sometimes a custom Spark pool, and quite often a lakehouse and an environment on top. All the stuff nobody else cares about. They just want it ready by tomorrow.<\/p>\n\n\n\n

In this post I’ll show how to hand that whole routine over to an LLM, with Claude Code doing the work through the Fabric MCP, the Fabric CLI and the Azure CLI. By the end, the full sequence is a single prompt.<\/p>\n\n\n\n

One prerequisite: the tool setup from my previous post, Agentic Development in Microsoft Fabric, Part 1: The Setup<\/a>. If you haven’t configured it yet, go there first. Everything below builds on it.<\/p>\n\n\n\n

Before you start<\/h2>\n\n\n\n

On top of the setup from part one, this post needs a few more things:<\/p>\n\n\n\n

    \n
  • Azure CLI (az<\/code>).<\/strong> Used by the second auth option below, by the Fabric skills, which call the Fabric REST API through az rest<\/code>, and for anything outside Fabric itself, like looking up a security group in Entra. Install steps are in the AZ CLI approach section.<\/li>\n\n\n\n
  • Fabric CLI (fab<\/code>).<\/strong> The MCP can’t assign a capacity or create a Spark pool yet, so the agent falls back to fab<\/code> for those steps. The Git skill uses it under the hood too. It’s a Python package and needs Python 3.10 or newer:
    pip install ms-fabric-cli
    fab auth login<\/code><\/pre>
    Confirm it landed with fab --version<\/code>.<\/p><\/li>\n\n\n\n
  • A Git repository<\/strong> in Azure DevOps or GitHub that you can push to. More on that in the repository part.<\/li>\n<\/ul>\n\n\n\n
    Then permissions. The agent acts as you, so it can only do what your account can do. Miss one of these and the agent will look broken when it isn’t:<\/p>\n\n\n\n
      \n
    • Creating workspaces<\/strong> needs the Create workspaces<\/em> tenant setting to include you (Admin portal \u2192 Tenant settings \u2192 Workspace settings). Many organisations restrict it to a security group.<\/li>\n\n\n\n
    • Assigning a capacity<\/strong> needs Contributor permissions on that capacity, or capacity admin. Being admin of the workspace isn’t enough.<\/li>\n\n\n\n
    • Adding groups to a workspace and connecting Git<\/strong> need the Admin role on the workspace. You get that automatically on anything you create yourself.<\/li>\n\n\n\n
    • Registering an Entra app<\/strong> (only for the first auth option below) needs either the Users can register applications<\/em> setting or the Application Developer role. Some tenants also require an Entra admin to grant consent for the permissions you add.<\/li>\n<\/ul>\n\n\n\n
      Signing in to the Fabric MCP<\/h2>\n\n\n\n
      First things first: the agent needs to log in to the Fabric MCP. That sounds trivial. It isn’t, at least not when OAuth is enforced and your LLM isn’t GitHub Copilot.<\/p>\n\n\n\n
      GitHub Copilot<\/h3>\n\n\n\n
      With GitHub Copilot in VS Code it’s painless. The first time the LLM tries to reach the Fabric MCP, it asks you to authorize and opens the browser. Log in to your account and you’ll see this:<\/p>\n\n\n\n
      \"Pasted<\/figure>\n\n\n\n
      Claude Code and other LLMs<\/h3>\n\n\n\n
      External LLMs like Anthropic’s Claude are a different story. Claude asks you to authorize the same way, but the attempt ends with this error:<\/p>\n\n\n\n
      Bash<\/span>