Public mode

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

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

GSA Windows client health check

Full guidance and history · All guidance changes

Global Secure Access · Official Microsoft guidance

Observed content change

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 clientshow-to-configure-cloud-firewall-clients#control-quic-traffic-on-udp-port-443
Changed wording view
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.
NewConfigure acquisition and enforcement
[added: In the Internet Access traffic forwarding profile, enable Custom Acquire and add a rule for the intended destinations with protocol UDP and destination port 443. Default Acquire only acquires TCP ports 80 and 443.]
Before: No saved wording on this side.
After: In the Internet Access traffic forwarding profile, enable Custom Acquire and add a rule for the intended destinations with protocol UDP and destination port 443. Default Acquire only acquires TCP ports 80 and 443.
NewConfigure acquisition and enforcement
[added: Create an enabled cloud firewall rule for those destinations with protocol UDP, destination port 443, and action Block. The rule blocks all matching UDP port 443 traffic, not only QUIC.]
Before: No saved wording on this side.
After: Create an enabled cloud firewall rule for those destinations with protocol UDP, destination port 443, and action Block. The rule blocks all matching UDP port 443 traffic, not only QUIC.
NewConfigure acquisition and enforcement
[added: Link the firewall policy to a security profile, enable the policy link, and apply the profile to the intended users through an enabled Conditional Access policy. Review matching rule and security profile priorities.]
Before: No saved wording on this side.
After: Link the firewall policy to a security profile, enable the policy link, and apply the profile to the intended users through an enabled Conditional Access policy. Review matching rule and security profile priorities.
NewConfigure acquisition and enforcement
[added: 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 Default Acquire enabled for TCP ports 80 and 443 so that applications that support fallback can connect over HTTPS using TCP.
NewConfigure acquisition and enforcement
[added: For prerequisites and detailed steps, see Configure cloud firewall for Global Secure Access clients.]
Before: No saved wording on this side.
After: For prerequisites and detailed steps, see Configure cloud firewall for Global Secure Access clients.
NewVerify effective QUIC blocking
[added: Browser QUIC settings don't establish whether cloud firewall blocks traffic. If your client version reports that QUIC is enabled in a browser, verify acquisition and enforcement with the following steps instead of disabling QUIC. These are manual troubleshooting steps, not an automated Health check test for cloud firewall.]
Before: No saved wording on this side.
After: Browser QUIC settings don't establish whether cloud firewall blocks traffic. If your client version reports that QUIC is enabled in a browser, verify acquisition and enforcement with the following steps instead of disabling QUIC. These are manual troubleshooting steps, not an automated Health check test for cloud firewall.
NewVerify effective QUIC blocking
[added: Note Until the client health check is updated to recognize cloud firewall enforcement, it can still report a QUIC failure because QUIC is enabled in the browser. You can ignore this specific failure only after you verify traffic acquisition and a matching cloud firewall Block decision by following these steps. Continue to investigate all other failed health checks.]
Before: No saved wording on this side.
After: Note Until the client health check is updated to recognize cloud firewall enforcement, it can still report a QUIC failure because QUIC is enabled in the browser. You can ignore this specific failure only after you verify traffic acquisition and a matching cloud firewall Block decision by following these steps. Continue to investigate all other failed health checks.
NewVerify effective QUIC blocking
[added: Use Advanced diagnostics to confirm that the client acquires the test connection through the Internet Access traffic forwarding profile. Acquisition rules don't override traffic bypass exclusions.]
Before: No saved wording on this side.
After: Use Advanced diagnostics to confirm that the client acquires the test connection through the Internet Access traffic forwarding profile. Acquisition rules don't override traffic bypass exclusions.
NewVerify effective QUIC blocking
[added: From a browser with QUIC enabled, make a new connection to a QUIC-capable destination covered by the acquisition and firewall rules.]
Before: No saved wording on this side.
After: From a browser with QUIC enabled, make a new connection to a QUIC-capable destination covered by the acquisition and firewall rules.
NewVerify effective QUIC blocking
[added: In Global Secure Access > Monitor > Traffic logs, open Connections. Find the UDP port 443 connection by its test time and destination, and confirm a logged Block decision. Review the associated security profile, policy, and rule information where available.]
Before: No saved wording on this side.
After: In Global Secure Access > Monitor > Traffic logs, open Connections. Find the UDP port 443 connection by its test time and destination, and confirm a logged Block decision. Review the associated security profile, policy, and rule information where available.
NewVerify effective QUIC blocking
[added: Confirm that the application falls back to HTTPS over TCP and that the expected inspection or filtering applies.]
Before: No saved wording on this side.
After: Confirm that the application falls back to HTTPS over TCP and that the expected inspection or filtering applies.
NewVerify effective QUIC blocking
[added: A UDP timeout alone doesn't prove cloud firewall enforcement. If you can't correlate the test connection with a logged Block decision, blocking isn't verified. Check acquisition, bypass exclusions, policy applicability, and rule priorities.]
Before: No saved wording on this side.
After: A UDP timeout alone doesn't prove cloud firewall enforcement. If you can't correlate the test connection with a logged Block decision, blocking isn't verified. Check acquisition, bypass exclusions, policy applicability, and rule priorities.
RemovedQUIC not supported for Internet Access
[removed: Since QUIC isn't yet supported for Internet Access, traffic to ports 80 UDP and 443 UDP can't be tunneled.]
Before: Since QUIC isn't yet supported for Internet Access, traffic to ports 80 UDP and 443 UDP can't be tunneled.
After: No saved wording on this side.
RemovedQUIC not supported for Internet Access
[removed: Administrators can disable QUIC protocol triggering clients to fall back to HTTPS over TCP, which is fully supported in Internet Access.]
Before: Administrators can disable QUIC protocol triggering clients to fall back to HTTPS over TCP, which is fully supported in Internet Access.
After: No saved wording on this side.
RemovedDisable QUIC in Microsoft Edge
[removed: To disable QUIC in Microsoft Edge:]
Before: To disable QUIC in Microsoft Edge:
After: No saved wording on this side.
RemovedDisable QUIC in Microsoft Edge
[removed: Open Microsoft Edge.]
Before: Open Microsoft Edge.
After: No saved wording on this side.
RemovedDisable QUIC in Microsoft Edge
[removed: Paste edge://flags/#enable-quic in the address bar.]
Before: Paste edge://flags/#enable-quic in the address bar.
After: No saved wording on this side.
RemovedDisable QUIC in Microsoft Edge
[removed: Set the Experimental QUIC protocol drop-down to Disabled.]
Before: Set the Experimental QUIC protocol drop-down to Disabled.
After: No saved wording on this side.

Source: Microsoft source · © Microsoft · MIT.

Read the current Microsoft source · Link to this observation · Compare any two versions

Other changed sections

Observation details
Observed by ChangeIntel
7 Nov 01:34 UTC
Source update metadata
6 Nov 23:34 UTC
Microsoft's latest commit in that period
Use Custom Acquire and cloud firewall instead of disabling browser QUIC (#14776) · committed 6 Nov 18:34 UTC · View diff
First observed on this installation
6 Oct 16:26 UTC
Last successful check
today 02:48 UTC
Next check due
17 Nov 02:48 UTC

Observation time is not publication time, and a comparison does not establish an effective date. Full source bodies are not published; this page holds generated summaries, section headings and, as the page's license allows, Microsoft's changed wording. A documentation edit does not confirm feature availability in an environment. Article references show literal targets and labels, including relative addresses; image bytes are not captured or compared.

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 16 Nov 03:41 UTC · 274 of 275 readable · 259 fully read · 11 waiting for GitHub's hourly limit · documentation 447/469 current