Global Secure Access client
The Global Secure Access service FQDNs and IP ranges Microsoft publishes for other proxies to bypass, so the client's own traffic isn't sent through them.
Managed device · pages read today 18:37 UTC · Global Secure Access
Where these entries come from
21 from 1 publisher page- Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler 1 section · 21 entries · read today 18:37 UTC
Changes in the last 90 days
None of these pages added or removed a destination in the sections this bundle reads.
ChangeIntel reads each page once a day: the destinations in its tables, lists and code blocks, under the sections named above. Entries follow the page; nothing is added that it does not publish.
Downloads
Built from the pages and endpoint sets above, as last readEntries with {tenantid} are left out of downloads until you fill in your value.
| Format | Destinations | Left out | Download |
|---|---|---|---|
| Plain list, one per line | 13 | 8 | Open |
| GSA V1 domain list | 5 | 16 | Open |
| GSA V1 Graph request body | 5 | 16 | Download |
| GSA V2 rules (review JSON) | 5 | 16 | Download |
| GSA V2 rules (CSV) | 5 | 16 | Download |
About these formats and checking them on a device
"Left out" counts entries a format cannot hold: IP ranges in web filtering, mid-name wildcards, URLs in a V1 domain list, and unfilled values. The V2 JSON is a review format; Microsoft publishes no Graph request shape for V2 rules yet. See how V1 and V2 evaluate.
The same entries are JSON at /api/v1/access-bundles/gsa-client. To check them from the workstation itself, run Test-ChangeIntelAccessBundle -Bundle gsa-client -Value @{ tenantid = '...' } from the ChangeIntel PowerShell module there: it resolves DNS and tries TCP and TLS to each published host, and reports certificate issuers that suggest TLS inspection.
The profile each destination goes to is inferred from Microsoft's published material, not confirmed. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile.
Not determined
21public material doesn't settle it; check the client's forwarding profile
| Destination | Why it's needed | Source |
|---|---|---|
13. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
13. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
150. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
150. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
150. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
150. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
151. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
6. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Internet Access profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
aps. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
auth. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
internet. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
m365. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
private. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |
{tenantid}. |
Global Secure Access service FQDNs and IPs bypasses | Learn about Security Service Edge (SSE) coexistence with Microsoft and Zscaler · Global Secure Access service FQDNs and IPs bypassesProfile not determined · possibly the Microsoft traffic profilePublished requirements contain unknown or mixed web and non-web transports; a single forwarding or web-filtering outcome is not established. Check the protocol and ports in the actual forwarding profile. |