Managing PAC File Deployments
Integrating the Secure Access PAC file or custom PAC files on the user devices in your organization so that all browser-based traffic is proxied is straightforward. For more information, see:
- Deploy the Secure Access PAC File for Windows
- Deploy the Secure Access PAC File for macOS
- Customize the Secure Access PAC File
- Upload Custom PAC Files to Secure Access
Note: Microsoft has deprecated PAC file support for the file:// and ftp:// protocols in Windows 10 on Edge. Hosting the PAC file on the local machine with the Edge browser is not supported. For more information, see Windows 10 does not read a PAC file referenced by a file protocol.
We recommend that you bypass these domains in your environment for traffic with TCP on ports 80 and 443:
- ocsp.int-x3.letsencrypt.org
- isrg.trustid.ocsp.identrust.com
- *.opendns.com
- *.sse.com
- *.umbrella.com
- *.okta.com
- *.oktacdn.com
- *.pingidentity.com
- secure.aadcdn.microsoftonline-p.com