Assign Local Admin
Updatedauthor: owinfreyATL
Daily.Entra.NewsAll supplied activity consists of Microsoft Learn documentation updates: no new or removed entries and no Message Center notices are reported. The clearest operational clarification is in ID Governance licensing for guest users, where successful access-package request creation is billed when a policy requires Verified ID. Entra ID also has a security-update page concerning removal of KDFv1 support and a broad refresh of device-registration and hybrid-join guidance. Nothing supplied establishes a new feature, preview, GA change, or effective retirement date.
The updated guest-user licensing material says Entitlement Management requests are billed on successful request creation when the access-package policy requires a Verified ID. It specifically points to the v1.0 `identityGovernance/entitlementManagement/assignmentRequests` operation and related user access-package request/update operations. This is a licensing clarification in the supplied evidence, not proof of a new entitlement-management feature or SKU.
The updated security page is explicitly about removing KDFv1 algorithm support from Microsoft Entra authentication. It is a security and compatibility topic, but the supplied summary gives no affected authentication flows, timing, or deployment status. Administrators should not infer from this record alone that a tenant-wide retirement has occurred; review the full guidance before changing integrations.
Updates cover device registration and identity, Microsoft Entra hybrid-join planning and configuration, targeted deployment, Primary Refresh Token, stale-device management, and Windows or `dsregcmd` troubleshooting. The individual summaries mostly contain only an author marker, so this is best classified as documentation maintenance rather than evidence of new join behavior, availability, or a required configuration change.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
| Microsoft Entra registered | Federated/Managed | Windows current | Persistent/Non-persistent | Not Applicable |
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
- *What is my SLA for Microsoft Entra authentication?*
author: owinfreyATL
author: owinfreyATL
author: owinfreyATL
> [!IMPORTANT]
| Entitlement Management | [Guest uses verified ID for request](entitlement-management-verified-id-settings.md) | Bill on successful request creation when verified ID is required in the policy.<br>**API**<br> https://graph.microsoft.com/v1.0/identityGovernance/entitlementManagement/assignmentRequests when the access package policy requires a Verified ID. | User requests access package assignment, Create access package assignment user update request. |
>[!NOTE]