Howto Arc Sign In Windows
Doc updateThe documentation wording about Microsoft Entra joining Arc-enabled machines and disconnecting them from another domain was updated.
Day in brief
Linux broker 2.0.2 now uses Entra join for device trust
The most consequential update affects Microsoft Single Sign-On for Linux: version 2.0.2 and later uses Microsoft Entra join instead of device registration for device trust, and existing upgraded devices must be re-joined and re-enrolled. New Entra ID guidance also details enhanced synchronization for sourcing sAMAccountName. Most remaining updates are mechanical example-ID, browser-reference, or wording changes.
- Linux broker 2.0.2 switches device trust from registration to join
Entra ID · GeneralMicrosoft Single Sign-On for Linux version 2.0.2 and later uses Microsoft Entra join for device trust. Existing upgraded devices must be re-joined and re-enrolled, with the documented upgrade process covering broker-state removal, reinstallation, and device re-join.
- Enhanced synchronization can source sAMAccountName for hybrid users
Entra ID · SecurityNew guidance documents sourcing hybrid users’ sAMAccountName from onPremisesSamAccountName. Existing domains retain current behavior until the setting is enabled; enabling it updates existing hybrid users during synchronization. Cloud-only users without the source value continue using mailNickname-based generation.
- Arc sign-in guidance limits the scenario to machines without another domain
Entra ID · AuthenticationThe revised guidance states that enabling sign-in joins an Arc-enabled machine to Microsoft Entra and is intended for machines not planned to join another domain, including on-premises Active Directory or Microsoft Entra Domain Services. Administrators should confirm domain-join plans before enabling the capability.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
14 updates
Microsoft Entra ID
12 updatesHowto Arc Sign In Windows
Doc updateThe how-to documentation revised its guidance explaining that enabling the capability joins an Arc-enabled machine to Microsoft Entra and is intended for machines not joined to another domain.
Howto Arc Sign In Windows
Doc updateThe guidance on enabling sign-in for Arc-enabled machines was revised, including their Microsoft Entra join behavior and domain-joining scenario.
Howto Arc Sign In Windows
Doc updateThe documentation fixes a typo in the sentence explaining that an Arc-enabled machine becomes Microsoft Entra joined and updates nearby truncated wording.
Howto Arc Sign In Windows
Doc updateThe documentation now states that this capability is intended for Arc-enabled machines not planned to join another domain, such as on-premises Active Directory or Microsoft Entra Domain Services.
Clean broker state including certificates (requires sudo)
Feature updateAction requiredMicrosoft Single Sign-on for Linux version 2.0.2 and later uses Microsoft Entra join for device trust instead of device registration. The documentation also adds MSAL integration support guidance and updates device removal terminology.
Howto Update Permissions
Doc updateThe permission-management examples now use app registration identifier `ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0` instead of `00001111-aaaa-2222-bbbb-3333cccc4444` when adding or removing Microsoft Graph permissions.
Primary Refresh Token
Doc updateThe documentation now references the Chrome Windows 10 Accounts extension and Mozilla Firefox v91+ Windows SSO setting.
Whats New Linux
Feature updateAction requiredStarting with broker version 2.0.2, Microsoft Single Sign-on for Linux uses Microsoft Entra join instead of registration for device trust. Existing upgraded devices must be re-joined and re-enrolled.
SAM Account Name
Public previewEnhanced synchronization can source sAMAccountName for hybrid users from onPremisesSamAccountName in Microsoft Entra ID. Existing domains retain current behavior until enabled; enabling updates existing hybrid users during synchronization, while cloud-only users without the source value continue using mailNickname-based generation.
Breaking Changes
Doc updateThe example request now uses client ID `ffffffff-eeee-dddd-cccc-bbbbbbbbbbb0` instead of `00001111-aaaa-2222-bbbb-3333cccc4444`.
Manage Device Identities
Feature updateThe documentation now states that the “Users may join devices to Microsoft Entra ID” setting applies to Windows 10 or newer, macOS, and Linux. It also adds troubleshooting guidance to verify registration or join settings when users encounter errors.
Microsoft Entra External ID
1 updateMigrate Passwords Just In Time
Doc updateThe password migration documentation now uses a different example API application identifier.
Netskope Integration
Doc updateThe Netskope integration example now uses different values for the tenantId and userId fields.