Azure (local) logo

Azure (local)

Beta

Microsoft's Azure MCP server queries and operates Azure resources with the identity the developer's Azure CLI session already holds.

  • Developer Tools
  • Local
Runs
On the developer's Mac
Launched with
npx
Platform
macOS
Publisher
Microsoft

How it works

Every agent request passes through Ferentin policy before it reaches Azure (local).

It runs on the developer's Mac and talks to the AI client over stdio, so no network gateway sees it. Developers launch it with npx -y @azure/mcp.

Ferentin's endpoint agent finds Azure (local) in the MCP configuration of AI clients on managed Macs. An administrator adds it once from the local MCP catalog for every managed Mac that launches it this way. Each of its tools starts unvetted until it is approved. Ferentin records every tool call.

  1. AI agentAsks for something
  2. Ferentin policies
  3. Azure (local) MCP serverRuns on the developer's Mac
  4. Governed resultChecked, logged, returned

About Azure (local)

Microsoft's Azure MCP server queries and operates Azure resources with the identity the developer's Azure CLI session already holds.

Frequently asked about Azure (local)

How do I connect Azure (local) to Ferentin?
Enroll your Macs with the Ferentin endpoint agent, then add Azure (local) from the local MCP catalog in the Ferentin admin console. Every managed Mac that launches it the way the catalog names it is covered, and each of its tools starts unvetted until you approve it.
Is the Azure (local) integration generally available?
The Azure (local) integration is currently beta on Ferentin.