The documentation now describes validation for both single-tenant and multitenant OIDC applications, including configuration-specific endpoint requirements and eligibility guidance.
Keep up with Microsoft Entra
Daily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
Day in brief
Private Access v2 switch is irreversible; existing configurations and traffic carry over
This was a quiet period: two of four updates changed document ownership metadata, while two substantive guidance changes affected Private Access and Entra App Gallery onboarding. The Private Access update documents an irreversible v2 switch, and OIDC validation guidance now covers both single-tenant and multitenant applications.
- Private Access v2 switching is non-reversible
Private Access · GeneralThe Manage Private Access Profile guidance now states that switching to v2 cannot be undone. Previous configurations carry over without changes to end-user traffic.
- OIDC App Gallery validation covers both app architectures
Entra ID · StandardsValidation guidance now describes both single-tenant and multitenant OIDC applications, including configuration-specific endpoint requirements and eligibility guidance. Onboarding teams should use the configuration matching the app architecture and verify scopes, endpoints, and redirect URIs.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
4 updates
Microsoft Entra ID
3 updatesThe page author and manager metadata were changed.
The document author was changed from hkinyunyu to HildaK-pm.
Microsoft Entra Private Access
1 updateManage Private Access Profile
Doc updateThe documentation now notes that switching to v2 is non-reversible, while previous configurations carry over without changes to end-user traffic.