Azure MCP Server

Microsoft's Azure MCP server provides AI agents with comprehensive cloud management capabilities across Microsoft Azure resources, virtual machines, and resource groups. It enables agents to query Azure Resource Manager, monitor service health, evaluate provisioning templates, and automate enterprise cloud operations.

Start for free

Azure MCP Server

Benefits with Ory + Azure MCP Server

Microsoft's Azure MCP server gives your agents access to a wide range of Azure services, from storage, databases, and Key Vault to monitoring and resource management, under the identity the session uses. That breadth is useful for operations and risky when an agent acts on the wrong resource. Ory Agent Security lets agents look up resources while changes stay with the few agents you approve.

View documentation

Use Cases

— 01 use case

Agent IAM

Cost and health reviewers at Read, storage and messaging agents at Write, VM and secret handling at Admin, and Block for agents without Azure work.

Explore Agent IAM

Core Functionality

— 04 capabilities

Read, write, admin, or no access
Ory Agent Security classifies every tool on the Azure MCP server as read, write, or admin, so you can give each user, team, or agent type only the level it needs: read for agents that look up resources and monitoring data, write for agents that create resources or send messages, admin for platform owners' agents, and no access for agents with no reason to reach Azure.
Enforced before execution
Ory Agent Security checks each tool call against the user, the agent acting for them, and any sub-agent inside the agent harness, so a denied secret read stops before it reaches your subscriptions, with nothing to roll back and no gateway to deploy.
Observe, then enforce
Observe mode shows which agents call Azure services and for whom without blocking anything, so you can apply Ory's pre-built policy for the Azure MCP server and enforce it on your own schedule.
Complete audit trail
Every allow and deny decision on the Azure MCP server streams to your SIEM through OpenTelemetry with the user, agent, and action attached, so you can show which agent touched a secret or resource and which user it acted for.