Daily.Entra.NewsDaily AI-generated highlights from Microsoft Learn and Message Center. Browse the archive from 15 April 2025 → About this project →
The period’s most substantive update expands the preview guidance for PIM custom extensions: administrators can collect business context and run asynchronous postapproval validation before assignment provisioning. A new Private Access guide covers local-network routing, while Entra customer sign-in and permissions references clarify configuration and role scope.
ID Governance · GovernanceThe updated guide describes postapproval extensions with deferred outcomes and asynchronous validation before assignment provisioning. It also covers collecting attributes such as cost center and project code, along with required Microsoft Graph permissions and endpoint configuration.
Private Access · GeneralA new guide explains how directly connected local resources can remain reachable while Private Access is enabled. Administrators can enable Allow local subnet bypass in the applicable traffic forwarding profile; users then enable Prefer Local Network in the Global Secure Access client to help route overlapping local-subnet traffic locally.
Entra ID · AuthenticationThe issuer URI must use the tenant ID or the tenant’s onmicrosoft.com domain. Custom verified domains aren’t supported, and domain_hint must use matching onmicrosoft.com values. The procedure also now tells administrators to refresh a user flow after provider configuration changes.
Entra ID · GeneralThe reference now states that Application Developer role holders can update applications they own, in addition to creating application registrations independently of the user registration setting.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The documentation now specifies tenant ID or the tenant’s onmicrosoft.com domain for the issuer URI, says custom verified domains aren’t supported, and requires matching onmicrosoft.com values for domain_hint. It also documents steps to refresh a user flow after provider configuration changes.
The permissions reference now states that Application Developer role holders can update applications they own, in addition to creating application registrations independently of the user registration setting.
The documentation adds postapproval extensions with deferred outcomes and asynchronous validation before assignment provisioning. It also describes collecting attributes such as cost center and project code, along with the required Graph permissions and endpoint configuration.
A new guide explains how directly connected local resources can remain reachable while Private Access is enabled, including routing behavior, prerequisites, and configuration steps.
