Microsoft Entra Agent ID
Monitoring

Manage Client Id Metadata Document Clients

In brief

The documentation now describes default, strict, and open tenant consent postures for CIMD clients, including their approval and OAuth-scope behavior. It also warns that unrestricted consent can enable consent phishing and unauthorized data access.

What Entra admins need to know

Review the documented consent posture for your organization and use the strict posture where client onboarding requires administrative review. No mandatory action or deadline is stated.

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 Entra administrator, I want to control and monitor CIMD clients in my tenant so that users can connect approved MCP clients without bypassing organizational consent and security policies.

Before enabling CIMD scenarios, review Client ID Metadata Documents in Microsoft Entra ID, including the limitations and governance considerations.

Prerequisites

To manage CIMD clients, you need:In this article

  • A Microsoft Entra tenant in which CIMD support is available.Choose a tenant posture

    Choose a tenant posture

    Before you configure CIMD, decide whoTenant consent policy determines whether users can add CIMD clients to a tenant and which delegated permissions they can grant. Review the default behavior, then choose a strict or open posture for your organization. Prefer the strict posture when your organization requires review before a new CIMD client to your tenant.can access its data.

    ApproachPosture Behavior Consider when
    Administrator-curatedDefault Disable user-initiatedUsers can add CIMD use. clients and grant a limited set of scopes, such as openid and Microsoft Graph User.Read. Risk-based step-up consent requires administrator approval for other permissions.Your organization allows self-service onboarding for basic scopes but requires administrator approval for additional permissions.
    StrictAn administrator reviewsadds each client, createsapproved CIMD client through consent, the admin center, or Microsoft Graph, then grants its agent identity, and grants the required permissions.OAuth scopes for all users. Users don't approve new CIMD clients or additional scopes. Your organization requires a security or application-onboarding review before creating an identity.review.
    Policy-controlledOpenAn administrator enables user consentLet users add for selected OAuth permissions, including for unverified clients, and disables risk-based step-up consent. The policy applies to CIMD and non-CIMD clients when the client and requested delegated permissions satisfy consent policy. Permissions outside the policy still require an administrator.that match its conditions. Each user consents for their own access. Your organization permits low-riskaccepts self-service integrations and monitors newly created identities.onboarding of unverified clients within a reviewed permission boundary.

    Both postures use consent policy to control user-initiated creation. Neither posture automatically grants a CIMD client access to every resource. Consent grants and tenant policy continue to determine which delegated permissions the client can use.

    Disable user-initiated CIMD use

    To prevent users from adding CIMD clients:

    1. Sign in to the Microsoft Entra admin center

      Understand the default posture

      Under the default consent policy, users can sign in to any CIMD client and create an agent identity in the tenant. They can grant only a limited set of OAuth scopes, such as openid and Microsoft Graph User.Read. Risk-based step-up consent is enabled by default and prevents users from granting other permissions to CIMD clients without administrator approval.

      Configure the strict posture

      To prevent users from adding CIMD clients to a tenant, update your tenant's consent settings to block user consent to unverified apps. Entra treats CIMD clients as unverified apps. Use one of the following two approaches:

      • Consent settings: Sign in to the Microsoft Entra admin center as a Global Administrator.

      • Browse to Entra ID > Enterprise apps > Consent and permissions > User consent settings.
      • Disable Select AllowDo not allow user consent, then select Save. This blocks user consent for unregistered appsto all apps, including verified apps. See Configure user consent.

      • Consent policy: As a Privileged Role Administrator, configure and agents using Client ID Metadata Documents.

      • Select Save.

    Whenassign a custom user consent forpolicy that requires clientApplicationsFromVerifiedPublisherOnly to be true. CIMD clients is disabled, users can't approve a new CIMD client themselves. During preview, the admin consent request workflow is disabled for Agent ID, including CIMD clients. Arrange a manual handoff: the user or client owner supplies the CIMD URL, target resource, and requested delegated scopes to an administrator, who adds the client and grants the required permissions before the user retries.

    Disablingbe publisher verified, so this blocks user consent to CIMD and other unverified apps while allowing verified apps that meet the policy's other conditions. See Manage app consent policies.

Review all assigned user consent policies: a verified-publisher requirement doesn't delete existing CIMD-backed agent identities oroverride another policy that allows unverified apps. These settings don't revoke existing consent grants.grants or delete existing identities. Review and revoke thoseexisting grants separately if you wantneed to stop use of clients that are already approved.previously approved access.

Enable user-initiated CIMD use with a custom consent policyConfigure the open posture

Use a custom permission grant policy when you wantTo enable users to add CIMD clients to your tenant and grant them specific permissions, update your tenant's consent policy:

  1. Define a custom consent policy. Limit consent to a controlled set of permissions. The following Microsoft Graph PowerShell example:

    1. Creates a CIMD-specific permission grant policy.
    2. Adds an include condition that allowsresource applications and reviewed delegated permissions classified as low impact.that allow user consent. Set clientApplicationsFromVerifiedPublisherOnly to false so CIMD clients can qualify. See Manage app consent policies.

    3. Assigns

      Apply the policy to all users. Assign it to the default user role without removing existing policy assignments.

    The CIMD condition is available onusing the Microsoft Graph beta endpoint.

    Connect-MgGraph -Scopes @(
        "Policy.ReadWrite.PermissionGrant",
        "Policy.ReadWrite.Authorization"
    )
    
    $policyId = "contoso-user-consent-cimd-low"
    
    # Create a custom permission grant policy for CIMD clients.
    $policy = @{
        id = $policyId
        displayName = "Allow low-impactsteps in Configure user consent. Review other assigned policies and remove broader user consent for CIMD clients"
        description = "Users can consent to delegated permissions classified as low impact for CIMD clients."
    }
    
    Invoke-MgGraphRequest `
        -Method POST `
        -Uri "https://graph.microsoft.com/beta/policies/permissionGrantPolicies" `
        -Body ($policy | ConvertTo-Json)
    
    # Add an include condition that matches only CIMD clients.
    $condition = @{
        permissionType = "delegated"
        permissionClassification = "low"
        resourceApplication = "any"
        permissions = @("all")
        clientApplicationIds = @("all")
        clientApplicationTenantIds = @("all")
        clientApplicationPublisherIds = @("all")
        clientApplicationsFromVerifiedPublisherOnly = $false
        cimdClientApplications = @{
            "@odata.type" = "#microsoft.graph.allCimdClientApplications"
        }
    }
    
    Invoke-MgGraphRequest `
        -Method POST `
        -Uri "https://graph.microsoft.com/beta/policies/permissionGrantPolicies/$policyId/includes" `
        -Body ($condition | ConvertTo-Json -Depth 4)
    
    # Preserve existing assignments and add the CIMD-specific policy.
    $authorizationPolicy = Invoke-MgGraphRequest `
        -Method GET `
        -Uri "https://graph.microsoft.com/v1.0/policies/authorizationPolicy"
    
    $assignments = @(
        $authorizationPolicy.defaultUserRolePermissions.permissionGrantPoliciesAssigned
    )
    $assignmentId = "managePermissionGrantsForSelf.$policyId"
    
    if ($assignments -notcontains $assignmentId) {
        $assignments += $assignmentId
    }
    
    $update = @{
        defaultUserRolePermissions = @{
            permissionGrantPoliciesAssigned = $assignments
        }
    }
    
    Invoke-MgGraphRequest `
        -Method PATCH `
        -Uri "https://graph.microsoft.com/v1.0/policies/authorizationPolicy" `
        -Body ($update | ConvertTo-Json -Depth 4)
    

    If you already have a custom policy for user consent, add the CIMD include condition to that policy instead of creating another policy. Don't edit a Microsoft-managed policy; built-in policies can't be changed.would bypass your restrictions.

  2. The example uses permissionClassification = "low". Only permissions classified as low impact can be granted under this condition. Review your tenant's permission classifications before assigning the policy.

    To verify the update, listTurn off risk-based step-up consent. After verifying the policy's include conditions and confirm restrictions, follow Configure risk-based step-up consent to disable the check that the authorization policy contains the assignment:otherwise requires administrator approval for nonbasic CIMD permissions.

    GET https://graph.microsoft.com/beta/policies/permissionGrantPolicies/contoso-user-consent-cimd-low/includes
    
    GET https://graph.microsoft.com/v1.0/policies/authorizationPolicy
    

    To disable this custom CIMD policy later, remove managePermissionGrantsForSelf.contoso-user-consent-cimd-low from permissionGrantPoliciesAssigned and update the authorization policy again. Preserve every unrelated assignment in the collection.

    For more information about how include and exclude condition sets are evaluated, see Manage app consent policies.

    Add a CIMD client in the admin center

    In the administrator-curated posture, review a client and create its agent identity before users connect.

Add a CIMD client

In the strict posture, review a client and create its agent identity before users connect.

Add via Admin Center

Before you begin, obtain the CIMD URL from the client owner. Use an account in your Microsoft Entra tenant with a role that can create agent identities, such as Global Administrator, Agent ID Administrator, or AI Administrator.

To add a trusted client before a user connects:

  1. Sign in to the Microsoft Entra admin center.
  2. Browse to Entra ID > Agents > Agent identities.
  3. Select Add CIMD client (Preview)agent identity.
  4. Enter the client's CIMD URL and continue.
  5. Review the metadata retrieved from the document.
  6. Complete the creation process.
  7. Grant only the delegated permissions required by the protected resource. During preview, use the sign-in and consent endpoints or Microsoft Graph, not the portal permissions experience.

Add via Microsoft Graph

CreatingBefore you begin, obtain the identity doesn't by itself authorize access to every resource. Consent grants and tenant policy continue to determine which delegated permissionsCIMD URL from the client owner. Use an account in your Microsoft Entra tenant with a role that can use.create agent identities, such as Global Administrator, Agent ID Administrator, or AI Administrator.

Add a CIMD client with Microsoft Graph

You can create the tenant-local agent identity by using the Microsoft Graph beta endpoint. Administrator-created identities require at least one owner or sponsor. This example binds a sponsor user from the target tenant; replace <sponsor-user-object-id> with the user's object-ID GUID.

POST https://graph.microsoft.com/beta/servicePrincipals/microsoft.graph.agentIdentity

{
  "displayName": "Contoso Agent",
  "clientIdMetadataDocumentUrl": "https://client.contoso.com/oauth/client-metadata.json",
  "[email protected]": [
    "https://graph.microsoft.com/v1.0/users/<sponsor-user-object-id>"
  ]
}

Microsoft Entra ID retrieves and validates the document before creating the identity. A successful response resembles:

{
  "agentIdentityBlueprintId": "aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee",
  "displayName": "Contoso Agent",
  "clientIdMetadataDocumentUrl": "https://client.contoso.com/oauth/client-metadata.json",
  "isClientIdMetadataDocumenthasClientIdMetadataDocument": true
}

List CIMD clients

The agentIdentityBlueprintId value is derived for identity and correlation purposes. CreatingCIMD clients appear alongside other agent identities in your tenant. Use the admin center to browse identities or Microsoft Graph to retrieve a CIMD client doesn't createCIMD-only list.

List via Admin Center

Sign in with a separately manageable agent identity blueprint.

The request fails if the URL isn't HTTPS, the document can't be retrieved or validated, its client_id doesn't exactly match the URL, or the canonical URL already identifies another agent identityMicrosoft Entra user account in the tenant.tenant you want to inspect.

Find CIMD clients with
  1. Sign in to the Microsoft Entra admin center.
  2. Browse to Entra ID > Agents > Agent identities.
  3. Add the filter Has Client ID Metadata Document.
  4. Select the identity to review its details, owners, sponsors, granted permissions, and sign-in logs.

List via Microsoft Graph

To list all CIMD-backed agent identities, use an advanced query:

GET https://graph.microsoft.com/beta/servicePrincipals/microsoft.graph.agentIdentity?$filter=isClientIdMetadataDocumenthasClientIdMetadataDocument eq true&$count=true
Authorization: Bearer {token}
ConsistencyLevel: eventual

The app ID shown in logs is derived from the CIMD URL. The client has no home application tenant. For more information, see Microsoft Entra Agent ID logs.

Respond to a compromised or untrusted client

If a CIMD client, its signing material, or its domain might be compromised:

  1. Disable the agent identity to stop new token issuance.
  2. Revoke its delegated permission grants.
  3. Revoke affected user sessions when required by your incident-response process.
  4. Review sign-in and audit logs for unexpected activity.
  5. Delete the agent identity when you no longer need investigation data or a disabled record.
  6. Contact the client owner through a trusted channel.

If the publisher loses control of the CIMD URL or moves the document, don't update the existing identity to a new URL. The URL is immutable. Review and onboard the new URL as a new client, then grant permissions again.

Understand governance gaps

The external CIMD document remains the source of truth for OAuth client configuration. Microsoft Entra ID doesn't copy the complete configuration to an application object.

Consider the following governance gaps:

  • App management policy doesn't evaluate configuration that exists only in the CIMD document.
  • Inventory and recommendations that inspect stored application credentials or redirect URIs might not include CIMD metadata.
  • CIMD clients can't be publisher verified or Microsoft 365 certified.
  • There is no tenant-managed domain allowlist or blocklist for CIMD URLs.
  • CIMD clients can't be used for app-only authentication or as protected resources.

Maintain an independent inventory of approved CIMD URLs and review it regularly.

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…