Troubleshooting
If the network traffic for the organization is not using the reserved IP that Secure Access assigned to your organization, we recommend that you review your Secure Access deployments, configuration settings, and policy rules.
- Ensure that destinations are not added in policy rules where you enabled remote browser isolation (RBI).
- Ensure that destinations are available on HTTP/TCP port 80 or HTTPS/TCP 443.
Secure Access does not provide the reserved IP for web sites that load over QUIC. - Ensure that web traffic on the reserved IP appears in the Activity Search report, and that the traffic egresses through the region of data centers where Secure Access provisioned the organization's reserved IP.
- Some 'find my IP' sites read the original IP in the proxy's HTTP X-Forwarded-For (XFF) header and show that IP instead of the organization's reserved IP. We recommend that you use the Activity Search report to verify that the network traffic is using the organization's reserved IP.
- Secure Access excludes Microsoft Update traffic on the organization's reserved IP.
- Ensure that the organization's network connects to the region of data centers where Secure Access provisioned the reserved IP.