Bridge Azure Connector

Connect Claude Code to Microsoft Azure cloud services for managing resources, deployments, storage, and monitoring through a unified MCP server interface.

When to Use This MCP Server

Connect this server when you need to:

• Manage Azure resources including virtual machines, app services, storage accounts, and databases directly from your Claude Code development session
• Monitor Azure service health, query Application Insights telemetry, and review deployment logs without switching to the Azure Portal
• Automate Azure infrastructure provisioning and configuration changes as part of your development workflow using natural language commands

Consider alternatives when:

• You are working exclusively with AWS or Google Cloud Platform, which have their own dedicated MCP server integrations
• You need complex ARM template or Bicep deployments that require the full Azure CLI with interactive prompts and multi-step wizard flows

Quick Start

Configuration

Copy
name: bridge-azure-connector
type: mcp
category: devtools

Example Connection

Copy
claude mcp:connect bridge-azure-connector

Available Tools

list-resources:      Enumerate Azure resources by subscription, resource group, or type
manage-storage:      Create containers, upload blobs, and manage Azure Storage accounts
query-insights:      Query Application Insights for logs, metrics, and performance data
manage-app-service:  Deploy, configure, and monitor Azure App Service applications
manage-functions:    Deploy and test Azure Functions with trigger configuration

Core Concepts

Azure MCP Integration Overview

Aspect	Details
Transport	stdio-based MCP server communicating with Azure Management REST APIs
Authentication	Azure Active Directory service principal or managed identity credentials
Scope	Subscription-level access to resource management, monitoring, and deployment
API Version	Targets stable Azure API versions with automatic version negotiation
Multi-Tenant	Supports multiple Azure subscriptions and tenants in a single session

Azure MCP Architecture

Claude Code IDE
    |
    v
[MCP Client] --stdio--> [Azure MCP Server]
                              |
                              v
                     [Azure AD Authentication]
                              |
                    +---------+---------+
                    |         |         |
                    v         v         v
              [Resource   [Monitor  [Storage
              Manager]    APIs]     APIs]
                    \         |         /
                     [Azure Subscription]

Configuration

Parameter	Type	Default	Description
AZURE_TENANT_ID	string	required	Azure Active Directory tenant ID for authentication
AZURE_CLIENT_ID	string	required	Service principal application (client) ID
AZURE_CLIENT_SECRET	string	required	Service principal client secret for credential authentication
AZURE_SUBSCRIPTION_ID	string	required	Default Azure subscription ID for resource operations
default_resource_group	string	none	Default resource group to scope operations when not specified

Best Practices

1. Use Least-Privilege Service Principals - Create a dedicated service principal with only the permissions needed for your development tasks. Avoid using Owner or Contributor roles on the entire subscription; instead, scope permissions to specific resource groups.

2. Set a Default Resource Group - Configure default_resource_group to avoid accidentally creating or modifying resources in the wrong resource group. This is especially important in subscriptions with production and development resources coexisting.

3. Query Application Insights for Debugging - Use query-insights to pull application logs, exception traces, and performance metrics during debugging sessions. This keeps your debugging context within Claude Code rather than requiring context-switching to the Azure Portal.

4. Store Credentials Securely - Keep AZURE_CLIENT_SECRET in environment variables or a secret manager, never in MCP configuration files. Rotate service principal credentials regularly and use certificate-based authentication for production environments.

5. Tag Resources Created via MCP - When creating Azure resources through the MCP server, include descriptive tags like environment=dev and created-by=mcp to track which resources were provisioned through automated workflows versus manual Portal operations.

Common Issues

1. Authentication Fails with Invalid Tenant - Verify that AZURE_TENANT_ID matches the directory containing your subscription. Multi-tenant organizations may have subscriptions in different directories, requiring the correct tenant ID for each.

2. Insufficient Permissions for Operation - The service principal may lack required RBAC role assignments. Check the Azure Portal's Access Control (IAM) blade for the target resource to verify the service principal has the necessary permissions.

3. Resource Not Found in Default Subscription - If a resource exists in a different subscription than the configured default, specify the subscription ID explicitly in your request. Use list-resources to search across all accessible subscriptions.