For Claude users who need to work with Azure resources, start with Microsoft’s Azure MCP Server. Claude Desktop has an installation path using Microsoft’s downloadable .mcpb extension bundle; Claude Code has a documented Azure plugin command. For an organization-managed remote connection, Microsoft describes using Azure API Management (APIM) with Microsoft Entra ID and OAuth 2.0. Choose Foundry MCP Server instead when the work is specifically with Microsoft Foundry services, not general Azure resource management.
Which Microsoft MCP server should you use with Claude?
Microsoft’s main option for general Azure work is Azure MCP Server. It implements the Model Context Protocol (MCP), allowing compatible clients and agents to interact with Azure resources through natural-language requests. Microsoft’s documentation describes support for a broad range of Azure services and tools, including integration with Azure CLI and Azure Developer CLI. The actions Claude can access depend on the server version, tools enabled for the client, and the authenticated user’s Azure permissions.
Foundry MCP Server is a separate, cloud-hosted option for giving agents secure tool access to Microsoft Foundry services. It is not simply another name for Azure MCP Server: choose it for Foundry-focused workflows, and choose Azure MCP Server for broader Azure resource and service operations. Microsoft’s Foundry getting-started guidance includes setup in Visual Studio Code; the available material does not establish a Claude-specific installation path for Foundry MCP Server.
| Need | Microsoft option | What to know |
|---|---|---|
| Interact with Azure resources and services | Azure MCP Server | Microsoft documents Claude Desktop and Claude Code connection paths. Entra ID authentication and Azure subscription permissions determine the usable scope. |
| Access Microsoft Foundry services | Foundry MCP Server | A distinct, cloud-hosted MCP implementation. Microsoft’s cited getting-started instructions cover Visual Studio Code; confirm the host and connection method you intend to use. |
| Offer a remote MCP endpoint to Claude under enterprise controls | An MCP backend exposed through Azure API Management | APIM can provide a governance layer for identity, authorization, monitoring, observability, and scaling. The endpoint and policies are deployment-specific. |
Microsoft’s registry currently describes Azure MCP Server 2.0 as generally available. Server versions, marketplace contents, client support, and tool availability can change, so check the current Microsoft and Anthropic installation material before rolling out or automating a setup.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
How Claude connects to Azure MCP Server
The basic arrangement has four parts: Claude is the MCP client; Azure MCP Server exposes tools; Microsoft Entra ID authenticates the user; and Azure role-based access control (RBAC), including subscription permissions and scope, determines which Azure resources and operations are accessible. The server does not grant Claude permissions that the signed-in user does not already have. It makes eligible tools available through the MCP connection.
There are two documented Claude paths for Azure MCP Server, suited to different working styles:
- Claude Desktop: install Microsoft’s downloadable
.mcpbbundle for the matching operating system and architecture. Microsoft recommends dragging the bundle into Claude Desktop or using Claude Desktop’s extension installation settings. - Claude Code: use the Azure plugin in Anthropic’s official plugin marketplace. The documented command is
/plugin install azure@claude-plugins-official. Check that the plugin name and availability are still current in the marketplace when you install it.
Microsoft also documents package-manager and HTTP configurations for compatible clients. Those are options for other supported deployment or host arrangements; do not assume they are interchangeable with the Claude Desktop bundle or the Claude Code plugin. Follow the current client-specific instructions for the client and server version you are using.
Rank #2
Install it in Claude Desktop
- Choose the server and platform. For general Azure access, obtain the Azure MCP Server
.mcpbbundle for the operating system and architecture in use. The bundle is a software extension, not a physical product. - Install the bundle. Drag the downloaded bundle into Claude Desktop, or use Claude Desktop’s extension installation settings, as Microsoft’s guide recommends.
- Authenticate with the intended Azure identity. Azure MCP Server uses Microsoft Entra ID through the Azure Identity library. Sign in with the account intended to perform the work and verify that it has access to the right Azure subscription.
- Confirm the authorization boundary. Check the user’s Azure RBAC assignments and subscription permissions before asking Claude to use tools that can change resources. Start with the narrowest required scope; do not use a broad administrative identity just to make a setup succeed.
- Check what the client exposes. Confirm the connection is available in Claude and inspect the tools offered by the installed server and client. The list may vary with server version, enabled tools, host support, and Azure permissions.
Microsoft’s installation guide provides bundles for Windows, macOS, and Linux architectures. That establishes the documented bundle route for those platforms; it does not mean every Claude Desktop version or organizational device policy will accept every bundle. If installation is blocked, check the client version, architecture, extension policy, and the current Microsoft guide rather than substituting an unverified package.
Install it in Claude Code
- In Claude Code, run
/plugin install azure@claude-plugins-official. - Check that the Azure plugin is listed in Anthropic’s official plugin marketplace and that its displayed name matches the command. Marketplace contents can change.
- Complete the Azure authentication flow with the Entra ID identity that should be used for the task.
- Verify the accessible subscription and the tools available to the signed-in user before issuing a request that could modify Azure resources.
Microsoft’s MCP Registry describes Azure MCP Server 2.0 as generally available and documents the Azure plugin path. The plugin command is more useful than a hand-written client configuration when using this documented route; do not combine it with a separate HTTP or package-manager setup unless the client’s current instructions call for that.
Use least privilege before enabling write-capable work
Authentication answers who is signed in; authorization answers which resources and operations that identity may use. Azure MCP Server uses Entra ID and Azure permissions, and its available tools reflect the user’s subscription permissions. Claude’s natural-language interface does not bypass Azure RBAC.
- Use an Entra ID account intended for the job, rather than a personal or all-purpose administrator identity.
- Grant access at the narrowest Azure RBAC scope that supports the task, such as the required resource or subscription scope, according to your organization’s policy.
- Separate read-only investigation from operations that create, change, or delete resources. Confirm the permissions needed for a task before allowing write-capable actions.
- Review the available tools and the signed-in identity when results are unexpectedly missing or when a request would have significant effects.
- Apply your organization’s normal approval, audit, and change-control requirements. MCP provides an interface to tools; it is not a replacement for governance.
The exact tools and operations exposed in a session are not a fixed universal list. They can depend on the server version, which tools are enabled, client support, and the user’s Azure access. Treat that as an authorization and change-management concern when you upgrade the server or expand the set of connected services.
Local connection or remote enterprise endpoint?
A local extension or plugin is a direct fit when an individual developer is connecting Claude to Azure through the documented client setup. A remote endpoint becomes more relevant when an organization needs to expose an MCP backend to Claude under centrally managed authentication and policies. Microsoft’s APIM guidance specifically covers securely exposing and governing MCP servers and their backends for clients and agents including Claude.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →| Consideration | Local Claude setup | Remote endpoint behind APIM |
|---|---|---|
| Connection model | Install the Azure MCP Server bundle in Claude Desktop or the Azure plugin in Claude Code. | Claude connects to an MCP endpoint exposed through an organization-managed gateway. |
| Identity and authorization | Entra ID authentication and the user’s Azure RBAC and subscription permissions constrain access. | APIM can validate JWT identity and apply authentication and authorization policies; Entra ID and OAuth 2.0 are part of Microsoft’s Claude-focused pattern. |
| Governance and operations | Manage client installation, server version, user access, and enabled tools. | APIM adds a gateway layer for observability, monitoring, control, and scaling; the backend and policies still need appropriate ownership. |
| Best fit | A developer using documented Claude Desktop or Claude Code integration. | An organization that needs centralized controls around a remote MCP backend. |
For the remote pattern, Microsoft describes Azure API Management as an OAuth 2.0 gateway powered by Entra ID for custom Claude integrations. In practice, the organization must configure the MCP backend, endpoint exposure, identity provider, authorization rules, and monitoring to match its environment. The cited guidance establishes the architecture and capabilities, not a universal APIM configuration or a one-click deployment for every MCP server.
Common setup problems and how to narrow them down
- The extension or plugin is not available. The client may not support the expected install path, or the bundle, plugin listing, or marketplace name may have changed. Confirm that you are following the current Claude-specific Microsoft instructions and, for Claude Code, verify the marketplace entry before retrying the documented command.
- Authentication fails or the wrong account is active. Azure MCP Server uses Entra ID. Complete authentication again with the intended identity and confirm that the account is allowed to sign in under your organization’s policies.
- The server connects, but a subscription or resource is missing. A connection does not confer Azure access. Check the active subscription, the signed-in identity, and the applicable Azure RBAC permissions and scope.
- A tool or action is not offered. The available tools can reflect the server version, enabled tools, Claude host support, and Azure permissions. Check each of those factors rather than assuming the missing action is a Claude failure.
- A request to change a resource is denied. Confirm that the operation is supported by the enabled tools and that the user has the required authorization at the relevant scope. Do not resolve a denial by granting broad access without reviewing the least-privilege requirement.
- A remote connection fails or is rejected by policy. For an APIM-fronted setup, check endpoint reachability, OAuth/Entra ID configuration, JWT validation, and authorization policies with the gateway owner. A valid Claude connection alone does not establish that the backend or gateway policy is configured correctly.
- A setup stops working after an update. Recheck the installed server version, plugin availability, client support, and tool list. Keep changes to server versions and permissions within your organization’s normal review process.
Performance, reliability, and cost considerations
The Microsoft material covered here does not establish a general latency benchmark, throughput figure, or fixed cost for using Azure MCP Server with Claude. Actual performance and cost depend on the Azure services and operations being called, the MCP deployment, network path, and any gateway or hosting components. Budget and monitor those underlying services rather than assuming MCP itself has a universal per-request price.
For reliability, treat the client, MCP server, identity provider, Azure service, and (for remote setups) gateway as separate parts of the path. A successful installation does not prove that every tool call will succeed: authentication, authorization, service availability, network access, and resource state can each affect the result. For remote deployments, Microsoft identifies APIM observability and monitoring as governance capabilities; decide what to monitor and who owns the backend and gateway before making the endpoint available broadly.
A separate MCP option for Claude: website screenshots
If the task is to capture website screenshots or PDFs—not to manage Azure resources—ScreenshotNeo is a more relevant MCP alternative to try first. It is a website screenshot API and MCP server for developers, made by Yorker Media, with the MCP tools take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients. It does not replace Azure MCP Server for Azure resource operations.
For a direct API call instead of setting up a browser capture flow, use cURL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for its parameters and connection details. Before capture, it accepts the cookie or consent banner like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and each response reports the page verdict and billing status in X-Page-Verdict and X-Billed headers. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 screenshots. Every feature is available on every plan.
Sign up for ScreenshotNeo’s free plan to get 1,000 screenshots a month with no card.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
