Cross-product topic

Developer

A cross-product view of Microsoft Entra changes related to Developer.

Latest Developer changes

Netskope Coexistence

Developer

The fifth Netskope coexistence scenario is now correctly numbered as item 5.

Application Properties

Developer

The documentation now states that tenant administrators cannot reverse Microsoft disablement by enabling tenant-local sign-in or reactivating the app registration.

Application Properties

Developer

The documentation now explains that Deactivated can result from tenant-local sign-in disablement, app registration deactivation, or Microsoft disablement. It also documents the related properties and clarifies that these conditions can overlap and must be remediated independently.

Delegate App Roles

Developer

The documentation now links to the “Restricting who can create applications and agents” section in two references, including the application registration error guidance.

Delegate application and agent management administrator permissions

Developer

The article now covers application and agent creation and management. It documents the **Users can create agent blueprints** setting, which administrators can turn off to restrict agent blueprint creation to administrators and Agent ID Developers.

Assign User Or Group Access Portal

Developer

The enterprise application page received spelling corrections in its user, group, and app-role assignment guidance.

Call Api Azure Services

Developer

The documentation corrects spelling errors, including “credentials,” and adds missing punctuation to a step describing token credentials and Azure SDK clients.

Palo Alto Coexistence

Developer

The service connection link text now uses “configuring” instead of the misspelled “configurating.”

Samples and guides for integrating apps with External ID

Developer

The page now links to a sample for listing and registering passkeys and documents delegated permissions for those operations. It also warns that deletion uses high-privilege application permissions and a client secret in browser code.

Authorization Agent Id

Developer

The documentation now describes blocked highly privileged directory roles for agent identities without the obsolete custom-role restriction wording.

Create content policies for network content filtering

Developer

The documentation now clarifies Basic content filtering and Scan with Purview descriptions, including that scanning can audit or block selected file and text content based on conditions.

Add app roles and get them from a token

Developer

The page now documents a shared default limit of 700 app roles and exposed delegated permission scopes per application or service principal, including counting rules, existing objects above the limit, and design guidance.

App Manifest

Developer

The documentation now states that app roles and exposed delegated permission scopes share a default limit of 700 permission definitions per application or service principal. Disabled definitions count, and this limit is separate from the aggregate manifest limit.

Create content policies for network content filtering

Developer

The documentation now describes real-time controls for content shared with generative AI applications, unmanaged cloud apps, and other internet destinations. It adds details about Basic content filtering and Purview-based inspection of files and text.

Microsoft Graph App Manifest

Developer

The documentation now states that app roles and exposed delegated permission scopes share a default limit of 700 definitions per application or service principal. Disabled definitions count, and this limit is separate from the aggregate manifest limit.

Microsoft Entra cloud-first identity guidance

Developer

The guide now focuses on phased transitions of user and group source of authority to Microsoft Entra ID while maintaining application access. It also updates readiness content and LDAP-binding application guidance, including provisioning cloud-managed users and groups back to on-premises AD or using Microsoft Entra Domain Services.

End-user experiences for applications

Developer

The documentation now states that these legacy preview and experience settings no longer affect app launchers or user behavior and are being removed from the Microsoft Entra admin center.

Publish App Gallery

Developer

The app gallery publishing documentation now refers to the Microsoft Partner One ID and identifies Microsoft Partner Network (MPN) ID as its former name.

Prerequisites to validate and publish your app

Developer

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.

Grant Admin Consent

Developer

The documentation examples now show revised object IDs for Microsoft Graph and other resource APIs while retaining the same consent scenarios and permissions.

Grant Admin Consent

Developer

The guide now uses different Microsoft Graph resource API object IDs in delegated- and application-permission consent examples; the documented permissions and consent type remain unchanged.

Manage App Consent Policies

Developer

The consent policy documentation now lists revised application IDs for Apple Mail, Spark Email, eM Client, Android-Samsung, Android-Mail, and Thunderbird.

Manage App Consent Policies

Developer

The consent-policy documentation now lists new application IDs for Apple Mail, Spark Email, eM Client, Android-Samsung, Android-Mail, and Thunderbird.

What If Tool

Developer

The Conditional Access What If tool table now uses a different sample UserId in all four examples.

Grant Admin Consent

Developer

The grant-admin-consent documentation updates the resource API object IDs shown in delegated- and application-permission examples.

Manage App Consent Policies

Developer

The documented application IDs for Apple Mail, Spark Email, eM Client, Android-Samsung, Android-Mail, and Thunderbird were replaced.

What If Tool

Developer

The Conditional Access What If tool documentation replaces the sample UserId in four example rows with a new sample identifier.

Howto Update Permissions

Developer

The permission-addition and permission-removal examples now use different sample object and client IDs.

Howto Update Permissions

Developer

The add and remove permission examples now use app registration ID `ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0` instead of `00001111-aaaa-2222-bbbb-3333cccc4444`.

Howto Update Permissions

Developer

The Microsoft Graph Update application example now uses a different app registration object ID when adding the documented delegated permissions.

Howto Update Permissions

Developer

The examples for adding and removing Microsoft Graph permissions now use app registration identifier `00001111-aaaa-2222-bbbb-3333cccc4444` instead of the previous sample identifier.

Prerequisites to validate and publish your app

Developer

The article now covers prerequisites for validating and publishing apps, with updated wording and links. Detailed portal submission, request tracking, implementation, and update/removal instructions were removed.

Prerequisites to validate and publish your app

Developer

The documentation separates shared prerequisites from SSO and SCIM requirements, with dedicated guidance for each capability. Applications supporting both must complete validation for both.

Howto Update Permissions

Developer

The permission-management examples now use app registration identifier `ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0` instead of `00001111-aaaa-2222-bbbb-3333cccc4444` when adding or removing Microsoft Graph permissions.

Agent Tokens

Developer

The user delegation section now spells out “on-behalf-of (OBO)” on first use. No feature behavior or requirements changed in the supplied diff.

Call Api Azure Services

Developer

The code sample now uses `<your-tenant-id>` instead of `<your-tenant>` for the `TenantId` value.

Call Api Custom

Developer

The documentation updates its C# examples, including distinct method names for UPN and object ID calls, a revised controller constructor signature, and clearer user-data method names.

Call Api Custom

Developer

The documentation now spells out “on-behalf-of (OBO)” on first use in the token scenario guidance. The referenced method is unchanged.

Call Api Microsoft Graph

Developer

The Agent ID Microsoft Graph documentation now labels sample variables as `usersAppOnly` and `usersOnBehalfOfUser`, clarifying the scenarios they represent.

Call Api Microsoft Graph

Developer

The documentation adds Microsoft Graph and Microsoft.Identity.Web imports, changes sample calls from Applications to Users, and clarifies that configured scopes must match the Graph resources used. Examples use User.Read and User.ReadBasic.All.

Call Api Microsoft Graph

Developer

The documentation adds an OpenID Connect using directive and renames two C# sample variables: `applications` to `applicationsForUser` and `me` to `meByOid`.

Call Api Microsoft Graph

Developer

The `TenantId` example value changed from `<my-test-tenant>` to `<your-tenant-id>` for clearer documentation.

Configure Third Party Agents

Developer

The third-party agents documentation now labels the sidecar setup link “Configure Microsoft Entra ID Auth SDK for agent identities” instead of “Configure Entra ID Auth SDK.”

Create Delete Agent Identities

Developer

The documentation updates the C# sample’s imports, endpoint structure, downstream API call, and model declarations to provide valid create-agent-identity code.

Microsoft Entra Sdk For Agent Identities

Developer

The documentation now identifies app-only tokens as using client credentials, expands on-behalf-of to OBO, and consistently uses the `agent-identity-client-id` placeholder in request examples.

Microsoft Entra Sdk For Agent Identities

Developer

The documentation replaces “Entra ID Auth SDK” with “Microsoft Entra ID Auth SDK” in two descriptions. The endpoint formats and behavior are unchanged.

Secure an Amazon Bedrock agent with Microsoft Entra Agent ID

Developer

The Amazon Bedrock integration guide now consistently uses “Microsoft Entra ID Auth SDK (sidecar)” in its description, explanations, container reference, and links. No behavior or availability change is described.

Grant Agent Access Microsoft 365

Developer

The documentation now lists how an agent with its own identity can communicate through Outlook email, OneDrive and SharePoint comments, Teams chats, and Teams channels, including the permissions required for inbound and outbound communication.

Connect with the required scope

Developer

After creating a new application proxy application, grant admin consent for the **User.Read** delegated permission in the Microsoft Entra admin center or using the Microsoft Graph PowerShell.

V2 Protocols Oidc

Developer

1. Under Redirect URIs, add the redirect URI of your application. For example, `https://localhost:8080/`.

Validate Agent Tokens Downstream Api

Developer

Learn how to validate Microsoft Entra Agent ID tokens in a downstream API by checking the signature, issuer, audience, and agent identity marker claim.

Configure Third Party Agents

Developer

- [Configure Entra ID Auth SDK (sidecar) for agent identities](microsoft-entra-sdk-for-agent-identities.md)

Add app roles and get them from a token

Developer

Learn how to add app roles to an application registered in Microsoft Entra ID. Assign users and groups to these roles, and receive them in the 'roles' claim in the token.

Application Discovery

Developer

Use Application discovery to detect the applications accessed by users and create separate private applications.

Configure app multi-instancing

Developer

Learn about multi-instancing, which is needed for configuring multiple instances of the same application within a tenant.

Configure how users consent to applications

Developer

Configure user consent settings in Microsoft Entra ID to control when and how users grant permissions to your organization's data. Secure your environment with step‑by‑step guidance.

Configure the F5 BIG-IP Easy Button for Header-based and LDAP SSO

Developer

Learn to configure the F5 BIG-IP Access Policy Manager (APM) and Microsoft Entra ID for secure hybrid access to header-based applications that also require session augmentation through Lightweight Directory Access Protocol (LDAP) sourced attributes.

Don't validate access tokens for Microsoft Graph

Developer

Include file warning that access tokens for Microsoft Graph should be considered opaque and should never be validated by customer code. Only Microsoft Graph validates Microsoft Graph access tokens.

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…