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

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

RSS
‹ November 2026 ›
MonTueWedThuFriSatSun1234567389101111213141516171181192021222324252627282930

Saturday 7 November 2026 · day in brief

3 changes to 3 pages

3 may need admin action

Global Secure Access 3

← 30 Oct10 Nov →All days

Week of 2 Nov 2026

  1. 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

    1. 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 Accesstroubleshoot-global-secure-access-client-diagnostics-health-check#quic-not-supported-for-internet-access
      • Added link: Control QUIC traffic on UDP port 443how-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

      Changed wording view
      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

    2. 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 443how-to-configure-cloud-firewall-clients#control-quic-traffic-on-udp-port-443
      • Added link: RFC 9114, section 3.1https://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

      Changed wording view
      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

    3. 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 clientshow-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

      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.

      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

Quoted wording: © Microsoft Corporation · source and applicable license beside each change.

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 22 Nov 22:52 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current