Microsoft Entra ID
Standards

Breaking Changes

In brief

The breaking-changes documentation now uses a different client application ID in its OAuth authorization URL and description.

What Entra admins need to know

No action is required; administrators referencing the example should use the updated client application ID.

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.

Example request

https://login.microsoftonline.com/contoso.com/oauth2/authorize?resource=https://gateway.contoso.com/api&response_type=token&client_id=00001111-aaaa-2222-bbbb-3333cccc4444ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0&... In this example, the resource tenant (authority) is contoso.com, the resource app is a single-tenant app called gateway.contoso.com/api for the Contoso tenant, and the client app is 00001111-aaaa-2222-bbbb-3333cccc4444ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0. If the client app has a service principal within Contoso.com, this request can continue. If it doesn't, however, then the request will fail with the error above.

If the Contoso gateway app were a multitenant application, however, then the request would continue regardless of the client app having a service principal within Contoso.com.

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…