{
  "format": "changeintel.gsa-web-filtering-v2",
  "graphShapeDocumented": false,
  "note": "Neutral review format. Create the rule in the Microsoft Entra admin center: Global Secure Access \u003E Secure \u003E Web Filtering Policies (V2).",
  "rules": [
    {
      "name": "ChangeIntel Microsoft Entra sign-in and admin",
      "action": "Allow",
      "destinations": [
        {
          "type": "url",
          "value": "*.partner.microsoftonline-p.cn",
          "purpose": "No purpose given; Common, Allow category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of partner.microsoftonline-p.cn but not partner.microsoftonline-p.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 9. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "*.partner.microsoftonline.cn",
          "purpose": "No purpose given; Common, Allow category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of partner.microsoftonline.cn but not partner.microsoftonline.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 10. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "*.msauth.cn",
          "purpose": "No purpose given; Common, Default category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of msauth.cn but not msauth.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 13. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "*.msauthimages.cn",
          "purpose": "No purpose given; Common, Default category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of msauthimages.cn but not msauthimages.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 13. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "*.msftauth.cn",
          "purpose": "No purpose given; Common, Default category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of msftauth.cn but not msftauth.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 13. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "*.msftauthimages.cn",
          "purpose": "No purpose given; Common, Default category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of msftauthimages.cn but not msftauthimages.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 13. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "login.microsoftonline.com",
          "purpose": "No purpose given; Common, Default category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 13. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "*.auth.microsoft.cn",
          "purpose": "No purpose given; Common, Allow category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "A *. wildcard matches subdomains of auth.microsoft.cn but not auth.microsoft.cn itself; list the apex separately only if a source publishes it.",
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 17. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "login.partner.microsoftonline.cn",
          "purpose": "No purpose given; Common, Allow category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 10. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        },
        {
          "type": "url",
          "value": "microsoftgraph.chinacloudapi.cn",
          "purpose": "No purpose given; Common, Allow category",
          "required": true,
          "sources": [
            "https://endpoints.office.com/endpoints/China"
          ],
          "caveats": [
            "V2 matching broadens: this FQDN becomes a URL destination that matches the address and its sub-paths, not only the exact host as a V1 FQDN rule did.",
            "Not determined (unknown): The destination is listed in Microsoft 365 endpoint set 7. This endpoint evidence is from the China source cloud. The commercial Global Secure Access routing guidance used here does not establish a profile or web-filtering outcome for this catalog. Microsoft documents separate deployment availability limits for sovereign environments. The source cloud does not identify your tenant deployment; verify that deployment\u0027s supported Global Secure Access capabilities and actual forwarding profile. Confirm in the Global Secure Access client: Advanced diagnostics, Forwarding profile."
          ]
        }
      ]
    }
  ],
  "notes": [
    "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).",
    "V2 has no standalone FQDN type: FQDNs are expressed as URL destinations, and a URL destination matches the address and its sub-paths.",
    "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.",
    "V2 runs before V1. A V2 Block is terminal; a V2 Allow isn\u0027t, so a V1 policy can still block the same traffic.",
    "Without TLS inspection, HTTPS traffic is evaluated by Server Name Indication (SNI); only unencrypted HTTP exposes the full URL."
  ]
}