Managing GitHub Copilot access to your organization's network

Learn how to use subscription-based network routing to control Copilot access to your network.

Who can use this feature?

Organization owners

Copilot Business

In this article

Note

Copilot subscription-based network routing is currently in public preview and subject to change. This feature will be enabled for all users on November 4, 2024.

About Copilot subscription-based network routing

As an organization owner, you can use your network firewall to explicitly allow access to GitHub Copilot Business, and/or block access to GitHub Copilot Individual. This allows you to control which GitHub Copilot plans your members can use within your network.

Configuring Copilot subscription-based network routing will affect the following GitHub Copilot features:

  • Code completions in Visual Studio Code, Visual Studio, JetBrains IDEs, and Vim/NeoVim
  • Copilot Chat in Visual Studio Code, Visual Studio, and JetBrains IDEs
  • Copilot Chat on GitHub
  • GitHub Mobile Apps
  • Copilot in the CLI

On November 4, 2024, we will enable Copilot subscription-based network routing for all users. This will ensure that users are accessing GitHub Copilot through an endpoint that is specific to their Copilot subscription. Only Copilot Business users will be able to connect to the Copilot Business endpoint and only Copilot Enterprise users will be able to connect to the Copilot Enterprise endpoint.

Optionally, if you are a customer with a GitHub account representative and you want to block access to Copilot Individual on your network before November 4, ask your representative about enabling Copilot subscription-based network routing ahead of this date.

Important steps to ensure continued access to GitHub Copilot

Between now and November 4, you should ensure that your firewall allows access to all of the hostnames listed in "Configuring your proxy server or firewall for Copilot."

Configuring Copilot subscription-based network routing for your enterprise

Before November 4, 2024, you should perform the following steps to ensure users can continue to access GitHub Copilot.

  1. Ensure your members have updated to at least the minimum version of their Copilot client listed below.

    • For Visual Studio Code, use Copilot Chat version 0.17 or later.
    • For JetBrains IDEs, use Copilot version 1.5.6.5692 or later.
    • For Visual Studio, use version VS 2022 17.11 or later.

  2. Update your corporate network firewall to include one, or both, of these paths in your allowlist:

    • For a Copilot Business subscription, add *.business.githubcopilot.com

    • For a Copilot Enterprise subscription, add *.enterprise.githubcopilot.com

    Note

    The * indicates a wildcard character. A wildcard is necessary as there are multiple subdomains required for GitHub Copilot to function correctly.

  3. Update your corporate network firewall to include *.individual.githubcopilot.com in your blocklist.