Microsoft Entra ID
Standards

Client ID Metadata Documents in Microsoft Entra ID (preview)

In brief

The page now explains CIMD’s role in AI agents connecting to MCP servers and adds compatibility tables for tested clients and Microsoft MCP servers, including supported and unsupported entries.

What Entra admins need to know

Administrators can check CIMD compatibility before deploying MCP integrations and verify that custom clients host metadata at a stable HTTPS URL on a controlled domain.

This editorial summary was generated by AI from the documentation changes. Verify important details in the full Microsoft Learn article.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

#customer-intent: As an identity architect or developer, I want to understand how Microsoft Entra ID supports Client ID Metadata Documents so that I can decide whether CIMD is appropriate for my MCP client scenario.

Client ID Metadata Documents in Microsoft Entra ID (preview)

Client ID Metadata Documents (CIMD) are a new way to register OAuth clients with Entra ID. CIMD is primarily used by AI agents that need to connect to remote MCP servers.

Why CIMD

AI agents may use many different MCP servers to perform work. Some of these MCP servers may be secured by Entra's OAuth server — e.g. WorkIQ, Azure Storage MCP, or enterprise-built MCP servers. Others may be secured by a different OAuth server — e.g. GitHub, Workday, Slack. For general purpose AI agents, it's impractical to know all MCP servers it will use, and therefore impractical to know all OAuth servers the AI agent will encounter. The AI agent needs a way to dynamically register itself with an OAuth server and obtain a client ID.

Client ID Metadata Documents (CIMD) let an OAuth client identify itself by using an HTTPS URL as its OAuth client_id value instead of a preassignedpre-registered client ID. TheA JSON document at that public URL contains the client's OAuth metadata. Microsoftmetadata, such as its redirect URIs and client credentials. This allows an OAuth server, such as Entra ID retrievesID, to fetch the JSON document and validatesuse it to securely issue access tokens to the document, represents the client as an agent identity in the tenant, and issues tokens under the tenant's existing consent and security policies.client.

CIMD is useful when a client must connect to many authorization servers with which it has no prior relationship. For example, an MCP clientAI agent can discover remote Model Context Protocol (MCP) servers at runtime, and each server might use a different authorization server. Requiring every client to be registered with every authorization server doesn't scale.

CIMD is defined by the OAuth Client ID Metadata Document specification. The MCP authorization specification recommends CIMD for clients that don't have another supported registration mechanism.

How CIMD works with Microsoft Entra ID

A typical CIMD authorization flow has the following steps:

An MCP client that discovers many remote servers at runtime is the primary scenario.

CIMD-enabled clients

The following table lists clients that have been tested and validated against Entra's CIMD support.

ClientClient ID Metadata DocumentPreview compatibility
Claude Codehttps://claude.ai/oauth/claude-code-client-metadataSupported.
Claudehttps://claude.ai/oauth/mcp-oauth-client-metadataSupported.
Codexhttps://chatgpt.com/oauth/codex/client.jsonSupported.
ChatGPThttps://chatgpt.com/oauth/client.jsonNot supported. Its confidential-client authentication flow isn't supported by the Microsoft Entra preview.
Visual Studio Codehttps://vscode.dev/oauth/client-metadata.jsonNot supported. Microsoft first-party clients do not use CIMD.
GitHub Copilothttps://github.com/copilot/desktop/client-metadata.jsonNot supported. Microsoft first-party clients do not use CIMD.
Custom client built with the official MCP SDKsHost a metadata document at a stable HTTPS URL on a domain you control.Supported.
Custom client implementationHost a metadata document at a stable HTTPS URL on a domain you control.Supported.

CIMD-enabled MCP servers

The following table is a non-exhaustive list of Microsoft MCP servers that have confirmed CIMD support.

MCP serverRemote MCP server URLCIMD testing status
Custom enterprise-built MCP server--Supported, see guide here.
Microsoft MCP for IT Adminshttps://mcp.svc.cloud.microsoft/adminNot supported yet.
Azure Management MCP (ARM)https://mcp.management.azure.comNot supported yet.
Azure DevOps MCPhttps://mcp.dev.azure.com/{organization}Not supported yet.
Work IQ MCPhttps://workiq.svc.cloud.microsoft/mcpNot supported yet.
Fabric IQ MCPhttps://fabriciq.svc.cloud.microsoft/v1/mcp/fabriciqNot supported yet.
Foundry MCPhttps://mcp.ai.azure.comNot supported yet.
Microsoft Sentinel MCPhttps://sentinel.microsoft.com/mcp/data-explorationNot supported yet.
Dataverse MCPhttps://{dataverseOrgName}.crm.dynamics.com/api/mcpNot supported yet.

Supported capabilities and limitations

The following table summarizes the capabilities and limitations of CIMD-backed agent identities. | Acting as an OAuth resource or token audience | Not supported | | ID tokens or SAML tokens for user sign-in | Not supported | | Shared client secrets | Not supported | | Confidential-client authentication, including private_key_jwt | Not supported during preview; keys in the metadata document aren't processed | | Microsoft first-party clients using CIMD | Not supported; use the existing first-party registration process | | Publisher verification or Microsoft 365 certification | Not supported | | Multiple agent identities sharing one blueprint | Not supported | | Agent user accounts | Not supported |

  • No app-only tokens: CIMD clients can't use the client credentials grant.
  • Audience restriction: Microsoft Entra ID doesn't issue tokens whose audience is the CIMD client.

Consent and permissions for clients using CIMD

UnderEntra treats clients using CIMD as unverified, and honors existing tenant consent policy. This means that the default recommended consent policy,following rules apply:

Tenant SettingWhat users can consent to
Default consent policyUsers can sign-in to CIMD clients. This creates an agent identity in the tenant. Users can only grant a very limited set of OAuth scopes to low-riskCIMD clients, such as openid and User.Read in Microsoft Graph. Risk-based step up prevents users from granting any other permissions to CIMD clients.
Do not allow user consentIn tenants that have disabled user consent via the Do not allow user consent setting in Entra Admin Center, users cannot consent to CIMD clients. This means they cannot add CIMD clients to their tenant, nor can they grant OAuth permissionsscopes to CIMD clients.
Other consent policyUsing consent policy, tenants can allow users to consent to CIMD clients. Administrators have fine-grained control over the conditions when user consent is allowed.

Admin controls for CIMD clients. Sensitive

Tenants can prevent users from adding CIMD clients or granting them new permissions require administrator consent. For administrator guidance, see Manage CIMD clients in Microsoft Entra IDvia consent policy. Use either of these approaches:

  • Block all user consent, via the Do not allow user consent setting in Entra Admin Center.
  • Allow user consent only for apps from verified publishers.

Either of these policies will prevent non-admin users from adding CIMD clients to a tenant. Follow Manage app consent policies to configure consent policy in your tenant.

To enable the use of a specific agent or client using CIMD, administrators can individually add agent identities to their tenant by providing the CIMD URL. This can be done via Entra Admin Center or Microsoft Graph APIs. See Managing CIMD clients.

Governance considerations

  • Entra doesn't provide a tenant-managed domain allowlist or blocklist for CIMD URLs.
  • Losing control of the document URL or its domain can affect every tenant that trusts that client identity.

UseAlways use least-privilege delegated permissions, preapprove clients that need sensitive access, monitor their sign-ins, and remove identities that are no longer required.

Related content

Daily Entra.News

Get daily email updates

Get a concise summary of the latest Microsoft Entra updates delivered straight to your inbox.

Loading the secure signup form…