Access bundles
What a locked-down admin workstation, managed device or server agent has to reach, one job at a time, with every destination traced to the page that publishes it. Download a bundle as a plain list or in Global Secure Access web filtering formats.
Managed device
Defender for Endpoint (streamlined)
Streamlined device connectivity for Microsoft Defender for Endpoint: core functionality, updates, certificate validation and the additional service URLs.Also for GCC High · DoD27 destinations
0 expected at web filtering
4 not expected at web filteringChecked today 18:37 UTCManaged device
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.21 destinations
0 expected at web filtering
0 not expected at web filteringChecked today 18:37 UTCManaged device
Intune-managed devices
What Intune-managed devices need: the Intune network endpoints page (core service, authentication, push notifications, Autopilot, Store, app and script delivery, Remote Help), the Autopilot service requirements and the Intune endpoint sets.252 destinations
4 expected at web filtering
24 not expected at web filteringA source page needs attentionChecked 30 Oct 07:16 UTCManaged device
Windows Update and Delivery Optimization
Windows Update, Delivery Optimization and Windows Autopatch for managed Windows devices.42 destinations
12 expected at web filtering
1 not expected at web filteringChecked 30 Oct 07:16 UTCManaged device
Windows 365 and Azure Virtual Desktop
What an end-user device needs to connect to Cloud PCs and Azure Virtual Desktop sessions, from the Azure Virtual Desktop end-user list, with the Microsoft Entra endpoint sets it points to.Also for GCC High · DoD90 destinations
3 expected at web filtering
37 not expected at web filteringChecked 30 Oct 07:16 UTCManaged device
Certificate revocation and issuers
Revocation (CRL and OCSP) and issuer hosts for the certificate authorities behind Microsoft's services, from the Azure CA details page, Defender's certificate validation list and the Microsoft 365 sets.Also for GCC High · DoD · 21Vianet (China)33 destinations
0 expected at web filtering
0 not expected at web filteringChecked 30 Oct 07:16 UTCManaged device
Microsoft Edge
Microsoft Edge updates, configuration, profile sign-in, sync, management and SmartScreen on a managed device; optional features such as Copilot, Rewards and feedback are not included.39 destinations
2 expected at web filtering
7 not expected at web filteringChecked today 18:37 UTCManaged device
Apple devices
What managed iPhone, iPad and Mac devices need from Apple's enterprise network list: device setup and activation, device management and push, software updates, apps, certificate validation and Apple Account sign-in.73 destinations
60 expected at web filtering
3 not expected at web filteringChecked today 18:37 UTCManaged device
Android Enterprise
The hosts Google lists for Android Enterprise devices: Google Play and updates, device policy, push and the management services.63 destinations
47 expected at web filtering
1 not expected at web filteringChecked today 19:41 UTCManaged device
Windows 365 Cloud PCs
What the network Cloud PCs are provisioned on needs for provisioning and health checks, from the Windows 365 network requirements.Also for GCC High · DoD15 destinations
0 expected at web filtering
0 not expected at web filteringChecked today 18:37 UTC
Global Secure Access web filtering: V1 and V2
What decides whether a destination gets through- Which profile takes it? GSA checks the always-on Microsoft Entra system profile (sign-in, Graph, certificate validation) and the Microsoft traffic profile (built from the Microsoft 365 endpoint list) before Internet Access. Microsoft documents that traffic the Microsoft traffic profile can acquire is acquired only there, even when a rule is set to Bypass. It publishes neither profile's host list, so bundles show how strongly the public material supports each call, and none of it is confirmed. Your tenant's real rules are in the GSA client: Advanced diagnostics, Forwarding profile.
- V2 runs first. A V2 Block is final. A V2 Allow is not: the request then goes to V1.
- V1 runs second and can still block what V2 allowed, including from a lower-priority profile. A destination that is allowed in V2 but still blocked usually has a V1 policy in the way.
- V2 matching is broader. A V1 domain rule matched the host; the same domain as a V2 URL destination matches the address and its paths.
- V1 FQDN destinations take the domain name only, without protocol, port or path. Use *.domain.com for subdomains; it doesn't match domain.com itself, so list both. Separate several FQDNs with commas and no spaces. How to configure Global Secure Access web content filtering
- In V1 the action is defined on the policy and rules carry destinations only; a V1 policy has no default action and acts only when a rule matches. Web filtering in Global Secure Access (V2)
- In V2 a security profile contains exactly one web filtering policy. Each rule carries its own Allow or Block action and the policy has a default action (Allow, Block, or the preview Continue Evaluation). Web filtering in Global Secure Access (V2)
- V2 has no standalone FQDN type: FQDNs are expressed as URL destinations, and a URL destination matches the address and its sub-paths. Web filtering in Global Secure Access (V2)
- A former exact-host FQDN evaluated with URL logic can match sub-paths of the address rather than only the exact host; review destinations to confirm they match the intended traffic. Web filtering in Global Secure Access (V2)
- V2 runs before V1. A V2 Block is terminal; a V2 Allow isn't, so a V1 policy can still block the same traffic. Web filtering in Global Secure Access (V2)
- Once any V2 web filtering policy exists, V1 policies can only be edited or deleted, not created. Migrate web content filtering policies from V1 to V2
- Up to 256 security profiles, 1,000 policies, 1,000 rules and 8,000 destinations (IP, FQDN, URL or web category) per tenant. The platform assumes ports 80 and 443. Known limitations for Global Secure Access: Internet Access limitations
- The URL filtering preview supports a maximum of 1,000 URLs per tenant. How to configure Global Secure Access web content filtering
- Without TLS inspection, HTTPS traffic is evaluated by Server Name Indication (SNI); only unencrypted HTTP exposes the full URL. How to configure Global Secure Access web content filtering
- The Microsoft traffic profile derives its rules from the Microsoft 365 IP and FQDN list, and traffic available in it can only be acquired there, not by the Internet Access profile. Learn about the Microsoft traffic profile
- Microsoft Graph (beta) creates a V1 policy with POST /networkaccess/filteringPolicies: fqdnFilteringRule rules hold fqdn destinations and the policy carries the action. Configure Microsoft Entra Internet Access using Microsoft Graph APIs