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

This page's changes and edits · All guidance changes

Microsoft's edit ·

Use Custom Acquire and cloud firewall instead of disabling browser QUIC (#14776)

Microsoft's commit message in MicrosoftDocs/entra-docs · commit 866f302 · +29 −20 lines · also on GitHub

Source wording view
⋯ 1 unchanged line
22 title: "Troubleshoot the Windows Global Secure Access client: Health check"
33 description: Troubleshoot the Global Secure Access client using the Health check tab in the Advanced diagnostics utility.
44 ms.topic: troubleshooting
5 −ms.date: 02/24/2026
5 +ms.date: 11/06/2026
66 ms.reviewer: lirazbarak
77 ms.custom: sfi-image-nochange
8 +ai-usage: ai-assisted
89 # Customer intent: I want to troubleshoot the Global Secure Access client using the Health check tab in the Advanced diagnostics utility.
910 ---
1011 # Troubleshoot the Global Secure Access client for Windows: Health check tab
⋯ 316 unchanged lines
327328 :::image type="content" source="media/troubleshoot-global-secure-access-client-diagnostics-health-check/troubleshoot-health-check-filtered-logs.png" alt-text="Screenshot of the Event Viewer showing a filtered log list.":::
328329 1. Save the filtered log as a file and attach the log file to the support ticket.
329330
330 −### QUIC not supported for Internet Access
331 −Since QUIC isn't yet supported for Internet Access, traffic to ports 80 UDP and 443 UDP can't be tunneled.
331 +<a id="quic-not-supported-for-internet-access"></a>
332 +
333 +## Troubleshoot QUIC acquisition and blocking
334 +
335 +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.
336 +
337 +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.
338 +
332339 > [!TIP]
333340 > QUIC is currently supported in Private Access and Microsoft 365 workloads.
334341
335 −Administrators can disable QUIC protocol triggering clients to fall back to HTTPS over TCP, which is fully supported in Internet Access.
342 +### Configure acquisition and enforcement
336343
337 −### Disable QUIC in Microsoft Edge
338 −To disable QUIC in Microsoft Edge:
339 −1. Open Microsoft Edge.
340 −1. Paste `edge://flags/#enable-quic` in the address bar.
341 −1. Set the **Experimental QUIC protocol** drop-down to **Disabled**.
344 +1. 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`.
345 +1. 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.
346 +1. 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.
347 +1. Keep **Default Acquire** enabled for TCP ports `80` and `443` so that applications that support fallback can connect over HTTPS using TCP.
342348
343 −### Disable QUIC in Chrome
344 −To disable QUIC in Google Chrome:
345 −1. Open Google Chrome.
346 −1. Paste `chrome://flags/#enable-quic` in the address bar.
347 −1. Set the **Experimental QUIC protocol** drop-down to **Disabled**.
349 +For prerequisites and detailed steps, see [Configure cloud firewall for Global Secure Access clients](how-to-configure-cloud-firewall-clients.md#control-quic-traffic-on-udp-port-443).
348350
349 −### Disable QUIC in Mozilla Firefox
350 −To disable QUIC in Mozilla Firefox:
351 −1. Open Firefox.
352 −1. Paste `about:config` in the address bar.
353 −1. In the **Search preference name field**, paste `network.http.http3.enable`.
354 −1. Toggle the **network.http.http3.enable** option to **false**.
351 +### Verify effective QUIC blocking
352 +
353 +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.
354 +
355 +> [!NOTE]
356 +> 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.
357 +
358 +1. 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.
359 +1. From a browser with QUIC enabled, make a new connection to a QUIC-capable destination covered by the acquisition and firewall rules.
360 +1. 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.
361 +1. Confirm that the application falls back to HTTPS over TCP and that the expected inspection or filtering applies.
362 +
363 +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.
355364
356365 ## Related content
357366 - [Install the Global Secure Access client for Windows](how-to-install-windows-client.md)
⋯ 1 unchanged line

Microsoft's Markdown source from MicrosoftDocs/entra-docs, © Microsoft Corporation, under MIT. Changed lines with up to 3 unchanged lines around each; ChangeIntel kept this copy 7 Nov 03:43 UTC. The commit date is when the source changed, which can be hours or days before Learn published it.

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 02:37 UTC · 274 of 275 readable · 258 fully read · 11 waiting for GitHub's hourly limit · documentation 445/469 current