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
RSSNovember 2026 in brief
6 changes to 5 pages
6 may need admin action
Global Secure Access 6
Pick a day to list only its changes.
Week of 16 Nov 2026
- Global Secure Access GSA known limitations
May need admin actionCheck your firewall and proxy allow lists.
1 new passage (about 20 words).
NewInternet Access limitations [added: Cloud firewall supports up to 1,000 rules per tenant and a combined total of 500 sources and destinations per rule.]
Before: No saved wording on this side.
After: Cloud firewall supports up to 1,000 rules per tenant and a combined total of 500 sources and destinations per rule.
Microsoft's commit: Document cloud firewall rule and endpoint limits
Observed 18 Nov 23:26 UTC · current page · MIT
- Global Secure Access GSA Windows client release history
May need admin actionCheck the dates against your plans.
6 new passages (about 50 words).
New section: Version 2.35.136 (preview)
Also changed: Functional changes · Other changes · Version 2.34.222
NewVersion 2.35.136 (preview) [added: Released for download on November 16, 2026.]
Before: No saved wording on this side.
After: Released for download on November 16, 2026.
NewFunctional changes [added: Adds support for Device Access for pre-logon scenarios (preview).]
Before: No saved wording on this side.
After: Adds support for Device Access for pre-logon scenarios (preview).
3 more changed passages · see them all
Microsoft's commit: Add Windows client 2.35.136 release notes (#14988)
Observed 17 Nov 22:50 UTC · current page · MIT
Week of 9 Nov 2026
- Global Secure Access Private network connector release history
May need admin actionCheck your firewall and proxy allow lists; check whether a default changed for your tenant or devices; check the dates against your plans.
6 new passages (about 100 words).
New section: Version 1.5.5130.0
Also changed: Release status · New features and improvements
NewRelease status [added: Nov 9, 2026: Released for download. This version is only available for install via the download page in the Microsoft Entra admin center.]
Before: No saved wording on this side.
After: Nov 9, 2026: Released for download. This version is only available for install via the download page in the Microsoft Entra admin center.
NewNew features and improvements [added: Performance and diagnostics: Added 24-hour CPU and memory history and improved health reporting accuracy.]
Before: No saved wording on this side.
After: Performance and diagnostics: Added 24-hour CPU and memory history and improved health reporting accuracy.
3 more changed passages · see them all
Microsoft's commit: Update version release notes for 1.5.5130.0
Observed 10 Nov 04:19 UTC · current page · MIT
Week of 2 Nov 2026
3 pages · shared source commit 7 Nov 2026 · 3 changes 3 may need admin action · 0 read to decide · 0 no action expected
microsoftdocs/entra-docs · commit
866f302a2dc3c5cf66a6fdc76cd575e3fe766e79- Global Secure Access GSA known limitations
May need admin actionCheck your firewall and proxy allow lists; check whether a default changed for your tenant or devices.
Changed article references · 1 added · 1 removed
- Removed link: QUIC not supported for Internet Access
troubleshoot-global-secure-access-client-diagnostics-health-check#quic-not-supported-for-internet-access - Added link: Control QUIC traffic on UDP port 443
how-to-configure-cloud-firewall-clients#control-quic-traffic-on-udp-port-443
2 new passages (about 100 words), 3 removed passages (about 90 words).
Changed in: QUIC not supported for Internet Access
NewQUIC not supported for Internet Access [added: End-to-end QUIC forwarding isn't supported in Internet Access. Cloud firewall for clients supports QUIC acquisition and blocking in preview.]
Before: No saved wording on this side.
After: End-to-end QUIC forwarding isn't supported in Internet Access. Cloud firewall for clients supports QUIC acquisition and blocking in preview.
NewQUIC not supported for Internet Access [added: Keep QUIC enabled in browsers. Use Custom Acquire to acquire UDP traffic on destination port 443 for the intended destinations, and use cloud firewall to block that traffic. Apply the firewall policy through the security profile for the intended users. Applications that support fallback can then use HTTPS over TCP. Default Acquire on TCP port 443 doesn't acquire UDP port 443, and an Allow rule doesn't enable supported end-to-end QUIC forwarding. For configuration and verification steps, see Control QUIC traffic on UDP port 443.]
Before: No saved wording on this side.
After: Keep QUIC enabled in browsers. Use Custom Acquire to acquire UDP traffic on destination port 443 for the intended destinations, and use cloud firewall to block that traffic. Apply the firewall policy through the security profile for the intended users. Applications that support fallback can then use HTTPS over TCP. Default Acquire on TCP port 443 doesn't acquire UDP port 443, and an Allow rule doesn't enable supported end-to-end QUIC forwarding. For configuration and verification steps, see Control QUIC traffic on UDP port 443.
3 more changed passages · see them all
Microsoft's commit: Use Custom Acquire and cloud firewall instead of disabling browser QUIC (#14776)
Observed 7 Nov 04:47 UTC · current page · MIT
- Removed link: QUIC not supported for Internet Access
- Global Secure Access GSA Windows client prerequisites and installation
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 · 2 removed
- Removed image: Screenshot of the tab for configuring Microsoft Edge and Chrome settings.
media/how-to-install-windows-client/edge-chrome-profile.png - Removed link:
media/how-to-install-windows-client/edge-chrome-profile.png#lightbox - Added link: Control QUIC traffic on UDP port 443
how-to-configure-cloud-firewall-clients#control-quic-traffic-on-udp-port-443 - Added link: RFC 9114, section 3.1
https://www.rfc-editor.org/rfc/rfc9114.html#section-3.1
7 new passages (about 270 words), 5 edited passages (47 words changed), 1 removed passage (about 40 words).
New section: Disable DNS over HTTPS in Microsoft Edge and Chrome by using Intune
Also changed: Control QUIC with cloud firewall · Configure settings for Microsoft Entra Internet Access by using Intune · Configure Firefox browser settings · Disable QUIC in Microsoft Edge and Chrome by using Intune
NewControl QUIC with cloud firewall [added: Keep QUIC enabled in users' browsers. To prevent QUIC connections from bypassing Microsoft Entra Internet Access inspection, use Custom Acquire to acquire UDP traffic on destination port 443 for the intended destinations, and use a cloud firewall Block rule for the same traffic. Keep Default Acquire enabled for TCP ports 80 and 443 so that applications that support fallback can connect over HTTPS using TCP.]
Before: No saved wording on this side.
After: Keep QUIC enabled in users' browsers. To prevent QUIC connections from bypassing Microsoft Entra Internet Access inspection, use Custom Acquire to acquire UDP traffic on destination port 443 for the intended destinations, and use a cloud firewall Block rule for the same traffic. Keep Default Acquire enabled for TCP ports 80 and 443 so that applications that support fallback can connect over HTTPS using TCP.
NewControl QUIC with cloud firewall [added: Note This example acquires and blocks UDP port 443, commonly used for HTTP/3 over QUIC. RFC 9114, section 3.1 permits HTTP/3 on any UDP port. If applications or servers use other destination ports, configure corresponding traffic acquisition and cloud firewall block rules. Blocking UDP port 443 alone doesn't block QUIC on other ports.]
Before: No saved wording on this side.
After: Note This example acquires and blocks UDP port 443, commonly used for HTTP/3 over QUIC. RFC 9114, section 3.1 permits HTTP/3 on any UDP port. If applications or servers use other destination ports, configure corresponding traffic acquisition and cloud firewall block rules. Blocking UDP port 443 alone doesn't block QUIC on other ports.
9 more changed passages · see them all
Microsoft's commit: Use Custom Acquire and cloud firewall instead of disabling browser QUIC (#14776)
Observed 7 Nov 03:43 UTC · current page · MIT
- Removed image: Screenshot of the tab for configuring Microsoft Edge and Chrome settings.
- Global Secure Access GSA Windows client health check
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 · 1 added · 0 removed
- Added link: Configure cloud firewall for Global Secure Access clients
how-to-configure-cloud-firewall-clients#control-quic-traffic-on-udp-port-443
17 new passages (about 450 words), 17 removed passages (about 120 words).
New sections: Troubleshoot QUIC acquisition and blocking · Configure acquisition and enforcement · Verify effective QUIC blocking
Also changed: QUIC not supported for Internet Access · Disable QUIC in Microsoft Edge · Disable QUIC in Chrome · Disable QUIC in Mozilla Firefox
NewTroubleshoot QUIC acquisition and blocking [added: Keep QUIC enabled in Microsoft Edge, Chrome, and Firefox. To prevent QUIC connections from bypassing Internet Access inspection, acquire and block the traffic with Custom Acquire and cloud firewall instead of disabling QUIC in browsers.]
Before: No saved wording on this side.
After: Keep QUIC enabled in Microsoft Edge, Chrome, and Firefox. To prevent QUIC connections from bypassing Internet Access inspection, acquire and block the traffic with Custom Acquire and cloud firewall instead of disabling QUIC in browsers.
NewTroubleshoot QUIC acquisition and blocking [added: Cloud firewall for clients supports QUIC acquisition and blocking in preview, not end-to-end QUIC forwarding. An Allow rule for UDP port 443 doesn't enable supported end-to-end QUIC connectivity.]
Before: No saved wording on this side.
After: Cloud firewall for clients supports QUIC acquisition and blocking in preview, not end-to-end QUIC forwarding. An Allow rule for UDP port 443 doesn't enable supported end-to-end QUIC connectivity.
18 more changed passages · see them all
Microsoft's commit: Use Custom Acquire and cloud firewall instead of disabling browser QUIC (#14776)
Observed 7 Nov 01:34 UTC · current page · MIT
- Added link: Configure cloud firewall for Global Secure Access clients
Week of 26 Oct 2026
- Global Secure Access Internet Access web filtering (V2)
May need admin actionCheck whether new requirements apply to your setup; check whether a default changed for your tenant or devices.
8 new passages (about 320 words), 10 edited passages (96 words changed).
New section: Use the Continue default action (in preview)
Also changed: A single policy with multiple rules · Policies, rules, and security profiles · Author a web filtering policy · Before you migrate and 3 more
EditedA single policy with multiple rules In V2, each rule carries its own action, and the policy defines a default action for traffic that doesn't match
[removed: a][added: an enabled enforcement] rule. Allow and Block[removed: produce an outcome.][added: stop V2 web filtering evaluation.] The[removed: preview]Continue[removed: Evaluation][added: default] action [added: (in preview)] passes evaluation to the web filtering policy in the next applicable security[removed: profile.][added: profile, in profile-priority order. It doesn't pass evaluation to a different policy type, such as TLS inspection.]Before: In V2, each rule carries its own action, and the policy defines a default action for traffic that doesn't match a rule. Allow and Block produce an outcome. The preview Continue Evaluation action passes evaluation to the web filtering policy in the next applicable security profile.
After: In V2, each rule carries its own action, and the policy defines a default action for traffic that doesn't match an enabled enforcement rule. Allow and Block stop V2 web filtering evaluation. The Continue default action (in preview) passes evaluation to the web filtering policy in the next applicable security profile, in profile-priority order. It doesn't pass evaluation to a different policy type, such as TLS inspection.
EditedA single policy with multiple rules Aspect V1 (web content filtering) V2 (web filtering) Policies per security profile Multiple policies can be linked. Exactly one policy. Default action None. The policy acts only if a rule matches. Yes. Applied when no [added: enabled enforcement] rule matches. Allow and Block
[removed: are terminal.][added: stop V2 web filtering evaluation. The] Continue[removed: Evaluation is nonterminal and available in preview.][added: default action (in preview) evaluates the next applicable web filtering policy.] Where the action is defined On the policy. Rules carry destinations only. On each rule, plus a policy default action.Before: Aspect V1 (web content filtering) V2 (web filtering) Policies per security profile Multiple policies can be linked. Exactly one policy. Default action None. The policy acts only if a rule matches. Yes. Applied when no rule matches. Allow and Block are terminal. Continue Evaluation is nonterminal and available in preview. Where the action is defined On the policy. Rules carry destinations only. On each rule, plus a policy default action.
After: Aspect V1 (web content filtering) V2 (web filtering) Policies per security profile Multiple policies can be linked. Exactly one policy. Default action None. The policy acts only if a rule matches. Yes. Applied when no enabled enforcement rule matches. Allow and Block stop V2 web filtering evaluation. The Continue default action (in preview) evaluates the next applicable web filtering policy. Where the action is defined On the policy. Rules carry destinations only. On each rule, plus a policy default action.
15 more changed passages · see them all
Microsoft's commit: Use consistent Continue default action preview wording
Observed 30 Oct 04:27 UTC · current page · MIT
- Global Secure Access Internet Access cloud firewall
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Microsoft's commit: Draft: Separate client and remote-network cloud firewall documentation (#14695)
Observed 28 Oct 02:44 UTC · current page
- 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
Week of 19 Oct 2026
- Global Secure Access GSA explicit forward proxy
May need admin actionCheck your firewall and proxy allow lists.
1 edited passage (8 words changed).
EditedEnable Explicit Forward Proxy Go to Global Secure Access >
[removed: Session management, and then select the][added: Connect >] Explicit Forward Proxy[removed: tab].Before: Go to Global Secure Access > Session management, and then select the Explicit Forward Proxy tab.
After: Go to Global Secure Access > Connect > Explicit Forward Proxy.
Microsoft's commit: Feature/alexpav/efp portal blade change (#14664)
Observed 24 Oct 00:08 UTC · current page · MIT
- Global Secure Access GSA coexistence with Netskope
May need admin actionCheck your firewall and proxy allow lists.
33 new passages (about 590 words).
New sections: Microsoft Entra Private Access and Microsoft Entra Microsoft Access with Netskope Internet Access · Add a steering configuration for internet access
Also changed: Overview · Netskope Location Profiles · Microsoft Entra Private Access and Microsoft Entra Microsoft Access configuration · Netskope Internet Access configuration and 2 more
NewOverview [added: Microsoft Entra Private Access and Microsoft Entra Microsoft Access with Netskope Internet Access]
Before: No saved wording on this side.
After: Microsoft Entra Private Access and Microsoft Entra Microsoft Access with Netskope Internet Access
NewOverview [added: In the fifth scenario, Global Secure Access handles private application and Microsoft 365 traffic. Netskope only captures internet traffic.]
Before: No saved wording on this side.
After: In the fifth scenario, Global Secure Access handles private application and Microsoft 365 traffic. Netskope only captures internet traffic.
18 more changed passages · see them all
Microsoft's commit: Number fifth Netskope coexistence scenario correctly
Observed 22 Oct 23:53 UTC · current page · MIT
- Global Secure Access Manage Private Access traffic forwarding profiles
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
1 new passage (about 20 words).
NewKnown limitations [added: Switching to v2 is a non-reversible action. All previous configurations get carried over with no changes to end user traffic.]
Before: No saved wording on this side.
After: Switching to v2 is a non-reversible action. All previous configurations get carried over with no changes to end user traffic.
Microsoft's commit: Update note on switching to v2 for Private Access
Observed 20 Oct 18:42 UTC · current page · MIT
- Global Secure Access GSA Windows client release history
May need admin actionCheck your firewall and proxy allow lists.
9 new passages (about 110 words).
New section: Version 2.34.222
Also changed: Functional changes · Other changes
NewFunctional changes [added: Adds support for Web sign-in for Windows.]
Before: No saved wording on this side.
After: Adds support for Web sign-in for Windows.
NewFunctional changes [added: When Private Access is enabled and the device isn't directly connected to the corporate network, Windows Firewall doesn't activate the domain profile.]
Before: No saved wording on this side.
After: When Private Access is enabled and the device isn't directly connected to the corporate network, Windows Firewall doesn't activate the domain profile.
6 more changed passages · see them all
Microsoft's commit: Add Windows client 2.34.222 release notes
Observed 19 Oct 19:40 UTC · current page · MIT
Week of 12 Oct 2026
33 pages · same-day observations 18 Oct 2026 · 33 changes 0 may need admin action · 33 read to decide · 0 no action expected
- Global Secure Access Assign users and devices to traffic forwarding profiles
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Coexistence with Cisco Secure Access
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Create a Private Access traffic forwarding profile
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA Android client deployment
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA client EDR and antivirus coexistence
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA coexistence with Cisco Umbrella
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA coexistence with Netskope
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Microsoft's commit: Add Netskope coexistence scenario for Private and Microsoft Access
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA coexistence with Palo Alto Networks
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA coexistence with Zscaler
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA egress IP ranges
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA explicit forward proxy
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA iOS client deployment
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA macOS client prerequisites and installation
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA macOS client release history
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA Microsoft traffic profile
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA Microsoft traffic profile management
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA points of presence and IP addresses
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA traffic forwarding profiles
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access GSA Windows client health check
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access custom bypass rule script
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access Intune device compliance bypass script
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access MCP firewall
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access network content filtering
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access threat intelligence
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access TLS inspection
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access TLS inspection FAQ
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access TLS inspection policies
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access TLS inspection troubleshooting
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access traffic forwarding profile
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access web content filtering categories
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access web filtering (V2)
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Internet Access web filtering V1 to V2 migration
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
- Global Secure Access Manage Private Access traffic forwarding profiles
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 18 Oct 23:18 UTC · current page
17 pages · same-day observations 13 Oct 2026 · 17 changes 0 may need admin action · 17 read to decide · 0 no action expected
- Global Secure Access Global Secure Access overview
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA client platform support
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA deployment planning
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA known limitations
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA Microsoft traffic deployment
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA proxy configuration requirements
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA remote network connectivity
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA remote network equipment configuration
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA Windows client prerequisites and installation
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access GSA Windows client release history
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Internet Access cloud firewall
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Internet Access web content filtering
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Private Access sensor network requirements
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Private Access sensor release history
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Private network connector firewall requirements
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Private network connector release history
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
- Global Secure Access Private network connectors
Read to decideThe wording changed without matching a rule; read the changed passages to decide.
The page title or its body outside the tracked passages changed. Review the source for its effect.
Observed 13 Oct 09:16 UTC · current page
Week of 5 Oct 2026
- Global Secure Access GSA coexistence with Palo Alto Networks
Read to decideA few words changed without matching a rule; read the marked wording to decide.
1 edited passage (1 word changed).
EditedOverview Set up a service connection or ZTNA Connector for Prisma Access to allow access to private applications. To learn about setting up a service connection see the Palo Alto documentation for configur
[removed: at]ing a service connection. For the ZTNA Connector see the Palo Alto documentation for configuring a ZTNA Connector.Before: Set up a service connection or ZTNA Connector for Prisma Access to allow access to private applications. To learn about setting up a service connection see the Palo Alto documentation for configurating a service connection. For the ZTNA Connector see the Palo Alto documentation for configuring a ZTNA Connector.
After: Set up a service connection or ZTNA Connector for Prisma Access to allow access to private applications. To learn about setting up a service connection see the Palo Alto documentation for configuring a service connection. For the ZTNA Connector see the Palo Alto documentation for configuring a ZTNA Connector.
Observed 7 Oct 16:30 UTC · current page · MIT
Quoted wording: © Microsoft Corporation · source and applicable license beside each change.