Guidance changes
Observed changes to selected Microsoft guidance. Review in My radar · Timelines and exceptions
469 of 469 selected pages have a baseline. 404 pages have an observed change; the newest was seen 1d ago.
Coverage and checks
469 of 469 selected pages have a baseline · 404 with observed changes · 469 current checks
Observed changes
RSSWeek of 26 Oct 2026
- Global Secure Access Internet Access traffic forwarding profile
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 · 4 added · 0 removed
- Added link: Acquire traffic with wildcard destinations
#acquire-traffic-with-wildcard-destinations-preview - Added link: Configure cloud firewall for remote networks
how-to-configure-cloud-firewall - Added link: Configure cloud firewall for Global Secure Access clients
how-to-configure-cloud-firewall-clients - Added link: Configure cloud firewall for Global Secure Access clients (preview)
how-to-configure-cloud-firewall-clients
21 new passages (about 420 words).
New sections: Apply security policies to acquired traffic · Acquire traffic with wildcard destinations (preview)
NewApply security policies to acquired traffic [added: Acquisition rules determine which traffic the Internet Access profile forwards to Global Secure Access. They don't define a cloud firewall Allow or Block decision.]
Before: No saved wording on this side.
After: Acquisition rules determine which traffic the Internet Access profile forwards to Global Secure Access. They don't define a cloud firewall Allow or Block decision.
NewApply security policies to acquired traffic [added: After configuring acquisition, configure the security policies required for that traffic. Use cloud firewall to allow or block connections based on the supported destination, port, and protocol conditions. Ensure the acquisition configuration covers the traffic that your firewall rules are intended to protect.]
Before: No saved wording on this side.
After: After configuring acquisition, configure the security policies required for that traffic. Use cloud firewall to allow or block connections based on the supported destination, port, and protocol conditions. Ensure the acquisition configuration covers the traffic that your firewall rules are intended to protect.
17 more changed passages · see them all
Microsoft's commit: docs: clarify unsupported DNS acquisition for client Cloud Firewall
Observed 27 Oct 21:25 UTC · current page · MIT
- Added link: Acquire traffic with wildcard destinations
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.