* Manage your accounts in one central location.
Documentation-focused day: Entra ID security and SAML guidance sharpened, while an ADAL-to-MSAL page was removed
3 February was primarily a Microsoft Learn maintenance day, with no new items or Message Center notices in the supplied record. The most consequential content consists of an Entra ID Recommendations entry for a preview GPO privilege-risk condition, clearer SAML ID requirements, and an ID Governance scenario for generating ServiceNow tickets during manual provisioning. The ADAL-to-MSAL recommendation page was removed, but the evidence does not establish that the migration recommendation or product support status was retired. No supplied item supports calling this a feature launch, general-availability event, or tenant-wide behavior change.
- Entra ID Recommendations includes a preview GPO privilege-risk entry
Entra ID · Fundamentals
The updated Recommendations page identifies the case where a Group Policy Object assigns unprivileged identities to local groups with elevated privileges. The supplied row includes “Users” and is marked “Preview,” making this security guidance rather than evidence that a new detection or enforcement control was deployed.
- SAML documentation clarifies the required ID handling
Entra ID · Standards
The Single Sign On SAML Protocol guidance states that ID is required, that Microsoft Entra ID uses it to populate InResponseTo, and that ID must not begin with a number. It gives prefixing a GUID with a string such as “ID” as a common strategy. This is an implementation clarification, not evidence of changed protocol behavior.
- Entitlement Management documents a ServiceNow ticketing workflow
ID Governance · Governance
The updated Ticketed Provisioning scenario shows how custom extensibility and a Logic App can automatically generate ServiceNow tickets when users receive assignments but still need manual provisioning for application access. It documents an automation pattern rather than announcing native ticketed provisioning or a new availability tier.
- The ADAL-to-MSAL recommendation page was removed
Entra ID · Microsoft identity platform
A Microsoft Entra documentation page titled “Recommendation Migrate From Adal To Msal” was removed. The supplied evidence does not say whether the content moved, was superseded, or whether ADAL/MSAL support status changed, so this should be treated as documentation removal—not proof that the migration recommendation itself was retired.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
9 updates
Microsoft Entra ID
7 updates* Manage your accounts in one central location.
Connect Version History
Updated|[2.5.3.0](#2530)|31 July 2026 (12 months after release of 2.5.76.0)|
Recommendations
Updated| Group Policy Object (GPO) assigns unprivileged identities to local groups with elevated privileges | Users | Preview | Yes | N/A |
Whats New
UpdatedFor guidance, see:
A Microsoft Entra documentation page was updated: Recommendation Migrate From Adal To Msal.
Single Sign On Saml Protocol
Updated| `ID` | Required | Microsoft Entra ID uses this attribute to populate the `InResponseTo` attribute of the returned response. ID must not begin with a number, so a common strategy is to prepend a string like "ID" to the string representation of a GUID. For example, `id6c1c178c166d486687be4aaf5e482730` is a valid ID. |
Microsoft Entra ID Governance
1 updateScenario: In this scenario you learn how to use custom extensibility, and a Logic App, to automatically generate ServiceNow tickets for manual provisioning of users who have received assignments and need access to apps.
Install Windows Client
UpdatedThe Global Secure Access client secures network traffic at the end-user device. This article describes how to download and install the Windows client.
