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 substantive changes center on a preview routing behavior, telephony sign-in verification guidance, and a coordinated clarification of Entra application deactivation. Global Secure Access Connector Groups now documents Performance mode, which selects the connector with the lowest measured network latency, while limiting connector load balancing to Microsoft Entra Private Access applications. A new Entra ID authentication article covers Arkose Labs checks before SMS or voice delivery, and related app pages distinguish tenant-local, app-registration, and Microsoft disablement states.
Global Secure Access · AuthenticationThe Connector Groups guidance adds preview Performance mode, which routes user traffic to the connector with the lowest measured network latency. It also clarifies that connector load balancing applies only to Microsoft Entra Private Access applications, not application proxy applications.
Entra ID · AuthenticationNew authentication guidance explains when users may encounter Arkose Labs anti-bot verification before receiving SMS messages or voice calls, along with the user experience, network requirements, and help-desk guidance.
Entra ID · AuthenticationThe sign-in article explicitly states that disabling user sign-in sets the service principal’s `accountEnabled` property to `false` and changes Activation status to Deactivated. It also provides steps to restore tenant-local sign-in while noting that other deactivation conditions can still apply.
Entra ID · DeveloperThe Application Properties guidance identifies tenant-local sign-in disablement, app registration deactivation, and Microsoft disablement as separate causes of Deactivated status. These conditions can overlap and must be remediated independently.
Entra ID · Microsoft identity platformThe app-registration guidance distinguishes deactivating an app registration from disabling sign-in on a tenant-local service principal. Reactivating the app registration does not automatically restore tenant-local sign-in.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The documentation explains when users may encounter Arkose Labs anti-bot verification before receiving SMS messages or voice calls, including user experience, network requirements, and help-desk guidance.
The article now explains that disabling sign-in sets the service principal’s `accountEnabled` property to `false` and changes Activation status to Deactivated. It also adds steps to restore tenant-local sign-in and notes that other deactivation conditions can still apply.
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.
The article now distinguishes deactivating an app registration from disabling sign-in on a tenant-local service principal. It also explains that activation status includes tenant-local and Microsoft disablement, and that reactivating the app registration does not automatically restore tenant-local sign-in.
The documentation adds Performance mode, which routes user traffic to the connector with the lowest measured network latency. It also clarifies that connector load balancing applies only to Microsoft Entra Private Access applications, not application proxy applications.
