Skip to content

Login with User-Assigned Managed Identity broken #205

@NickKeller

Description

@NickKeller

Running the MCP server in an AKS cluster, and receiving this error at startup

aks-mcp-server-deployment-5c474d4bbc-58vc7 mcp-server 2025/09/12 17:10:27 OAuth Config: Using client ID from environment variable AZURE_CLIENT_ID
aks-mcp-server-deployment-5c474d4bbc-58vc7 mcp-server 2025/09/12 17:10:27 OAuth Config: No CORS origins configured - cross-origin requests will be blocked for security
aks-mcp-server-deployment-5c474d4bbc-58vc7 mcp-server 2025/09/12 17:10:27 Initializing AKS MCP service...
aks-mcp-server-deployment-5c474d4bbc-58vc7 mcp-server 2025/09/12 17:10:27 Azure client initialized successfully
aks-mcp-server-deployment-5c474d4bbc-58vc7 mcp-server 2025/09/12 17:10:27 Using User-assigned Managed Identity authentication.
aks-mcp-server-deployment-5c474d4bbc-58vc7 mcp-server Initialization error: azure cli authentication failed: user-assigned managed identity login failed: ERROR: Passing the managed identity ID with --username is no longer supported. Use --client-id, --object-id or --resource-id instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions