Learn how to allow certain traffic through your firewall or proxy server for Copilot to work as intended in your organization.
Who can use this feature?Proxy server maintainers or firewall maintainers
If your company employs security measures like a firewall or proxy server, you should add the following URLs, ports, and protocols to an allowlist to ensure Copilot works as expected:
GitHub public URLs Domain and/or URL Purposehttps://github.com/login/*
Authentication https://github.com/enterprises/YOUR-ENTERPRISE/*
Authentication for managed user accounts, only required with Enterprise Managed Users https://api.github.com/user
User Management https://api.github.com/copilot_internal/*
User Management https://copilot-telemetry.githubusercontent.com/telemetry
Telemetry https://default.exp-tas.com
Telemetry https://copilot-proxy.githubusercontent.com
API service for Copilot suggestions https://origin-tracker.githubusercontent.com
API service for Copilot suggestions https://*.githubcopilot.com
1 API service for Copilot suggestions https://*.individual.githubcopilot.com
2 API service for Copilot suggestions https://*.business.githubcopilot.com
3 API service for Copilot suggestions https://*.enterprise.githubcopilot.com
4 API service for Copilot suggestions
Depending on the security policies and editors your organization uses, you may need to allowlist additional domains and URLs. For more information on specific editors, see Further reading.
Every user of the proxy server or firewall also needs to configure their own environment to connect to Copilot. See Configuring network settings for GitHub Copilot.
Further readingRetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4