Daily.Entra.NewsThe period contains 15 documentation updates, no new items, no Message Center notices, and one removed page. The most consequential changes are targeted guidance for regional moves of user-assigned managed identities, narrowly scoped Conditional Access allow scenarios, the Group Source of Authority (SOA) preview, Secure Enclave handling for Apple SSO, and requestor-answer visibility in access-package approvals. Nothing supplied establishes a new Entra launch, general-availability event, or tenant-wide behavior change. The removed “Whatis” page is not identified as a retired capability.
Workload ID · GeneralThe Workload ID article instructs administrators to copy permissions assigned to a user-assigned managed identity and warns that listing Azure role assignments may not capture permissions granted through a service-specific option. For a regional move, migration owners should verify those grants before proceeding; this is migration guidance, not evidence of a platform behavior change.
Entra ID · Conditional AccessThe updated Secure Access Conditional Access article explicitly covers scenarios in which access must be allowed for a small, specific group. Administrators managing tightly scoped exceptions should review the guidance, but the supplied change does not establish a new control or a change to Conditional Access evaluation.
Entra ID · FundamentalsThe updated cloud-first SOA article provides or points to prerequisites, supported scenarios, and step-by-step guidance for architects and administrators. The title still labels the capability Preview, and the record does not say availability or behavior changed; use it to validate an evaluation or migration plan rather than treating it as a new launch.
Entra ID · GeneralThe updated article directs administrators to recommended steps if Secure Enclave needs to be disabled. This is security and operational guidance for deployments using the Apple SSO plugin; the evidence does not indicate a new plugin capability or a change in enforcement.
ID Governance · GovernanceAfter requestor information is configured in an access package policy, the updated guidance says administrators can view the requestor’s responses and links to the procedure. This clarifies an existing ID Governance workflow; it is not evidence of a new rollout.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
Learn about Source of Authority (SOA), including prerequisites, supported scenarios, and step-by-step guidance for IT Architects and Administrators.
- [Manage Microsoft Entra groups and group membership](/entra/fundamentals/how-to-manage-groups)
- [Manage Microsoft Entra groups and group membership](/entra/fundamentals/how-to-manage-groups)
- [Manage Microsoft Entra groups and group membership](/entra/fundamentals/how-to-manage-groups)
A Microsoft Entra documentation page was updated: Whatis.
If for any reason Secure Enclave needs to be disabled, follow these recommended steps:
These articles provide additional information on working with groups in Microsoft Entra ID.
For more information on Microsoft Entra groups, see:
For more information on Microsoft Entra groups:
|-----|-----|
npx create-react-app reactspa --template typescript
1. Run `sudo apt remove --purge aadlogin` (Ubuntu/Debian), `sudo yum remove aadlogin` (RHEL), or `sudo zypper remove aadlogin` (openSUSE or SLES).
There are scenarios when it's necessary to allow access for a small, specific group.
For more information on Microsoft Entra groups, see:
After you configure requestor information in your access package's policy, can view the requestor's responses to the questions. For guidance on seeing requestor information, see [View requestor's answers to questions](entitlement-management-request-approve.md#view-requestors-answers-to-questions).
1. Copy user-assigned managed identity assigned permissions. You can list [Azure role assignments](/azure/role-based-access-control/role-assignments-list-powershell) but that may not be enough depending on how permissions were granted to the user-assigned managed identity. You should confirm that your solution doesn't depend on permissions granted using a service specific option.
