Guidance changes
Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions
469 of 469 selected pages have a baseline. 401 pages have an observed change; the newest was seen today.
Coverage and checks
469 of 469 selected pages have a baseline · 401 with observed changes · 469 current checks
Observed changes
RSSWeek of 2 Nov 2026
-
May need admin actionCheck whether new requirements apply to your setup; check the roles and permissions you grant.
1 new passage (about 60 words), 1 removed passage (about 60 words).
NewRequire device to be marked as compliant [added: Microsoft Authenticator requires UserAuthenticationMethod.ReadWrite access to register credentials. When this permission is used in a delegated context by Microsoft Authenticator, access required for credential registration isn't blocked by the Require device to be marked as compliant grant control. This exception doesn't apply to application permissions. Requests using the UserAuthenticationMethod.ReadWrite application permission remain subject to the Require device to be marked as compliant check.]
Before: No saved wording on this side.
After: Microsoft Authenticator requires UserAuthenticationMethod.ReadWrite access to register credentials. When this permission is used in a delegated context by Microsoft Authenticator, access required for credential registration isn't blocked by the Require device to be marked as compliant grant control. This exception doesn't apply to application permissions. Requests using the UserAuthenticationMethod.ReadWrite application permission remain subject to the Require device to be marked as compliant check.
RemovedRequire device to be marked as compliant [removed: Similarly, the Require device to be marked as compliant doesn't block Microsoft Authenticator app access to the UserAuthenticationMethod.Read scope. Authenticator needs access to the UserAuthenticationMethod.Read scope during Authenticator registration to determine which credentials a user can configure. Authenticator needs access to UserAuthenticationMethod.ReadWrite to register credentials, which doesn't bypass the Require device to be marked as compliant check.]Before: Similarly, the Require device to be marked as compliant doesn't block Microsoft Authenticator app access to the UserAuthenticationMethod.Read scope. Authenticator needs access to the UserAuthenticationMethod.Read scope during Authenticator registration to determine which credentials a user can configure. Authenticator needs access to UserAuthenticationMethod.ReadWrite to register credentials, which doesn't bypass the Require device to be marked as compliant check.
After: No saved wording on this side.
Microsoft's commit: Update Microsoft Authenticator access requirements
Observed 5 Nov 15:42 UTC · current page · MIT
- Microsoft 365 Copilot Copilot requirements
May need admin actionCheck whether new requirements apply to your setup.
Changed article references · 1 added · 0 removed
- Added link: Operating system requirements
#operating-system-requirements
6 new passages (about 100 words), 1 edited passage (10 words changed).
New section: Operating system requirements
Also changed: Requirements at a glance
EditedRequirements at a glance … app-specific experiences Required for app-specific experiences [added: Operating system requirements for the Microsoft Copilot app Required Required] Supported browser and cookies Required for …
Before: … app-specific experiences Required for app-specific experiences Supported browser and cookies Required for …
After: … app-specific experiences Required for app-specific experiences Operating system requirements for the Microsoft Copilot app Required Required Supported browser and cookies Required for …
NewOperating system requirements [added: The Microsoft Copilot app is supported on the following operating systems:]
Before: No saved wording on this side.
After: The Microsoft Copilot app is supported on the following operating systems:
3 more changed passages · see them all
Observed 5 Nov 02:11 UTC · current page
- Added link: Operating system requirements
- Microsoft 365 connectivity The cloud.microsoft domain
May need admin actionCheck your firewall and proxy allow lists; check whether new requirements apply to your setup; check whether a default changed for your tenant or devices.
Changed article references · 2 added · 4 removed
- Removed link: Introducing cloud.microsoft: a unified domain for Microsoft 365 apps and services
https://techcommunity.microsoft.com/t5/microsoft-365-blog/introducing-cloud-microsoft-a-unified-domain-for-microsoft-365/ba-p/3804961 - Removed link: Microsoft 365 URLs and IP address ranges
urls-and-ip-address-ranges?view=o365-worldwide - Removed link: Microsoft 365 network guidance on domains and service endpoints
urls-and-ip-address-ranges?view=o365-worldwide - Removed link: hundreds of domains
urls-and-ip-address-ranges?view=o365-worldwide - Added link: Microsoft 365 TLS decryption guidance
network-intermediation?view=o365-worldwide - Added link: Microsoft 365 endpoints
urls-and-ip-address-ranges?view=o365-worldwide
25 new passages (about 730 words), 15 removed passages (about 640 words).
New sections: Unified cloud.microsoft domain · What is cloud.microsoft? · Why cloud.microsoft domain unification matters · What cloud.microsoft means for enterprise security and networking and 1 more
Also changed: Unified cloud.microsoft domain for Microsoft 365 apps · Benefits of a unified domain · Security considerations · Requirements for admins and 1 more
NewUnified cloud.microsoft domain [added: cloud.microsoft is Microsoft's unified, purpose-managed domain for Microsoft 365, Microsoft Copilot, and other Microsoft SaaS experiences in the commercial cloud.]
Before: No saved wording on this side.
After: cloud.microsoft is Microsoft's unified, purpose-managed domain for Microsoft 365, Microsoft Copilot, and other Microsoft SaaS experiences in the commercial cloud.
NewUnified cloud.microsoft domain [added: The cloud.microsoft domain provides a consistent and durable domain foundation for Microsoft SaaS. Customers can use it to identify Microsoft services, help users recognize official product URLs, configure network policies, and support domain-dependent integrations as Microsoft SaaS products and experiences evolve.]
Before: No saved wording on this side.
After: The cloud.microsoft domain provides a consistent and durable domain foundation for Microsoft SaaS. Customers can use it to identify Microsoft services, help users recognize official product URLs, configure network policies, and support domain-dependent integrations as Microsoft SaaS products and experiences evolve.
18 more changed passages · see them all
Observed 5 Nov 01:22 UTC · current page · CC BY 4.0
- Removed link: Introducing cloud.microsoft: a unified domain for Microsoft 365 apps and services
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.