Daily.Entra.NewsAll 12 recorded changes on 25 April were Microsoft Learn updates. There were no new or removed items and no Message Center notices. The most consequential clarifications concern Microsoft Entra ID OIDC redirect_uri handling and the Microsoft Entra Workload ID limitation on token lifetimes for managed identity service principals. Microsoft Entra External ID updates mainly refreshed existing B2B collaboration procedures rather than announcing a new capability.
Entra ID · AuthenticationThe updated v2 protocols page describes redirect_uri as recommended, requires it to exactly match one of the URIs registered for the app and be URL-encoded, and states that omitting it causes the endpoint to select a registered redirect URI at random. This is a documentation clarification of integration requirements, not evidence that endpoint behavior changed; app teams can use it when checking sign-in callback failures.
Workload ID · FundamentalsThe updated Configurable Token Lifetimes page explicitly says that configuring token lifetimes for managed identity service principals isn't supported. This clarifies the scope of the token-lifetime guidance; teams using managed identities should not assume that setting is available.
External ID · GeneralThe updated page explains how to give cloud B2B users access to on-premises apps through Microsoft Entra B2B collaboration. It is an updated how-to rather than a release signal, and the supplied evidence identifies no new prerequisite or migration requirement.
External ID · GeneralThe revised page shows how an administrator can add sponsors to guest users in Microsoft Entra B2B collaboration. This is an operational documentation update for guest administration; the record does not indicate that sponsor functionality is newly available or that existing tenants require a configuration change.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
| `redirect_uri` | Recommended | The redirect URI of your app, where authentication responses can be sent and received by your app. It must exactly match one of the redirect URIs you registered in the portal, except that it must be URL-encoded. If not present, the endpoint picks one registered `redirect_uri` at random to send the user back to. |
1. Log in to [Shopify Plus organization admin](https://shopify.plus). Navigate to **Users > Security**.
If you still can't resolve your problem, contact ServiceNow support, and ask them to turn on SOAP debugging to help troubleshoot.
Shows how an admin can add sponsors to guest users in Microsoft Entra B2B collaboration.
Learn about customizing the language experience in your user flows in Microsoft Entra External ID.
Learn how to give cloud B2B users access to on-premises apps with Microsoft Entra B2B collaboration.
Current limitations for Microsoft Entra B2B collaboration
Learn about how to customize the browser language for your app's authentication experience to provide a personalized sign-in.
Compare solutions for using Microsoft Entra External ID to work with people outside your organization, including B2B collaboration and Azure AD B2C.
author: garrodonnell
Give locally managed external partners access to both local and cloud resources using the same credentials with Microsoft Entra B2B collaboration.
- **Managed identities**: Configuring token lifetimes for [managed identity service principals](~/identity/managed-identities-azure-resources/overview.md) isn't supported.
