Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 270/272 feeds/APIs · 469/469 docs · 7/9 advisories · checked 19:50 UTC Customize Public modeDiscuss ChangeIntel on Discord

Conditional Access policies now apply to Windows Hello for Business and macOS Platform SSO registration

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

What the notice says

Microsoft’s text, with source markup removed
If your organization has Conditional Access policies scoped to Register security information, those policies will now apply when users set up Windows Hello for Business (WHfB) or register macOS Platform SSO credentials. Today, these registration flows enforce MFA, but do not evaluate your registration-targeting Conditional Access policies — meaning requirements like authentication strength, trusted locations, or other CA conditions aren't enforced when users enroll WHfB or macOS Platform SSO credentials. This change closes that gap. Organizations without these policies aren't affected. When this will happen • July 6, 2026: Gradual rollout begins. • July 13, 2026: Rollout complete for all tenants. How this affects your organization Users registering WHfB or macOS PSSO credentials will need to satisfy your registration-targeting Conditional Access policy requirements before completing enrollment. For example, a user might need to use an existing FIDO2 security key, approve a push notification in Microsoft Authenticator, or connect from a trusted network location — depending on what your policies require. Any Grant controls you've configured will apply. Users who don't meet the requirements will be blocked from completing registration until the conditions are met. Action recommended In Entra admin center > Protection > Conditional Access, find policies targeting Register security information. Review Grant controls — check what requirements users must satisfy during registration (authentication strength, trusted locations, MFA method). Consider whether users setting up a new device can meet your policy requirements — for example, make sure users have a FIDO2 security key or other qualifying credential available before they start device setup. Test with report-only mode before enforcement reaches your tenant. Update helpdesk docs — users may see a new authentication prompt during device setup. If you experience issues during the rollout window (July 6–July 13), contact Microsoft Support or your account team for assistance. Learn more: Require MFA for security info registration

What changed

Between archive captures, newest first

The archive supplies one version of this notice.

Linked documentation

Microsoft pages the notice links to

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
  • 1 linked page has not been read yet.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 19:50 UTC · 270 of 272 readable · 269 fully read · documentation 469/469 current