Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
The strongest changes are new implementation guidance for securing Model Context Protocol servers with Microsoft Entra ID and integrating Entitlement Management with ServiceNow. The period also adds a specific managed-identity creation limit at 98% of tenant directory quota, improves PIM audit correlation guidance, and clarifies the Partner One ID requirement for App Gallery publishers. The passkey page now omits “(preview)” from its title and heading, with the supplied evidence indicating a label change.
Entra ID · StandardsA new Entra ID how-to explains registering an MCP server as an OAuth 2.0 protected resource, enabling v2 access tokens, and connecting MCP clients through Microsoft Entra Agent ID. An app registration with required permissions and an HTTPS MCP server are prerequisites.
Entra ID · GovernanceNew guidance covers ServiceNow access package requests, request history, and approvals, along with installation, configuration, licensing, and user workflows. Microsoft Entra ID Entitlement Management remains the system of record, and a Microsoft Entra ID P2 or Microsoft Entra Suite license is required.
Workload ID · GeneralThe updated guidance states that creating a managed identity is blocked when directory usage reaches or exceeds 98% of the tenant quota, including for new or recreated service principals. Existing identities and assignments continue to work; soft-deleted objects count toward the quota, and reducing usage or increasing the quota enables retries.
ID Governance · GovernanceRelated PIM activation and deactivation events can have different CorrelationId values. The updated audit-log guidance recommends roleAssignmentRequestId for tracing a complete request and adds Log Analytics query examples.
Entra ID · DeveloperThe publishing prerequisites now instruct app publishers to provide a Partner One ID associated with the Microsoft AI Cloud Partner Program organization listed as the publisher, and explain where to get help if the identifier is unknown.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The documentation now describes submission states from Draft through Published, with example review and publishing timelines measured in business days. It notes that actual times vary based on submission completeness and validation.
The app gallery listing documentation now uses the Partner Program URL without the `/en-US` locale segment.
The app gallery listing guide now uses shorter link text for the Microsoft AI Cloud Partner Program; the destination URL is unchanged.
The page title and heading no longer include “(preview).”
The documented password example now includes an exclamation mark at the end.
A new how-to explains registering an MCP server as an OAuth 2.0 protected resource, enabling v2 access tokens, and connecting MCP clients through Microsoft Entra Agent ID.
The app gallery publishing documentation now refers to the required identifier as a Partner One ID and notes that it was formerly called the Microsoft Partner Network (MPN) ID.
The documentation now instructs app publishers to provide a Partner One ID associated with their Microsoft AI Cloud Partner Program organization and explains how to find help if they do not know it.
The documentation now explains how Entitlement Management integrates with ServiceNow for access package requests, request history, and approvals. It covers licensing, installation, configuration, and user workflows.
The documentation explains that related PIM activation and deactivation events can have different CorrelationId values. It recommends using roleAssignmentRequestId to trace a complete request and adds Log Analytics query examples.
The documentation now directs administrators to the **Who can request access** section on the **Requests** tab, where selecting **Manager** enables managers to request access packages for employees.
The documentation now states that creating a managed identity is blocked when the resulting directory usage reaches or exceeds 98% of the tenant quota. This applies to new or recreated service principals; existing identities and assignments continue to work.
