# Setting up GitHub Copilot for your enterprise

> Enable GitHub Copilot across your enterprise so developers can write code faster.

- 网址：https://funcoding.ai/agents/github-copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-enterprise/
- 来源：GitHub Copilot 官方文档原文（英文），CC-BY-4.0 许可，同步于 2026-10-11
- 官方原文：https://docs.github.com/en/copilot/how-tos/copilot-on-github/set-up-copilot/enable-copilot/set-up-for-enterprise

---
## Enable GitHub Copilot

**Enterprise owners** can set up Copilot Business or Copilot Enterprise for their enterprise.

* If **you're on GitHub.com and pay by credit card or PayPal**, you can [subscribe here](https://github.com/github-copilot/purchase?ref_product=copilot&ref_type=purchase&ref_style=button).

<div class="callout callout-note">

If you are currently in a trial of GitHub Enterprise Cloud, you must convert to a paid enterprise before you can purchase GitHub Copilot.

</div>

* For **any other payment method and enterprises on GHE.com**, [contact GitHub's Sales team](https://github.com/enterprise/contact?ref_product=copilot&ref_type=engagement&ref_style=text).

## Set policies

You will use enterprise policies to manage two aspects of governance:

* **Availability**: Which Copilot features, models, and MCP servers are available in your enterprise?
* **Controls**: What restrictions apply to these features? For example, will you exclude certain files or block suggestions matching public code?

Generally, enterprise owners can either set each policy for the whole enterprise or "let organizations decide." With the latter option, users are subject to the policy of the organization where they receive their Copilot license or to the default defined in your "Policies for enterprise-assigned users" setting.

To manage policies, see [AUTOTITLE](https://funcoding.ai/agents/github-copilot/how-tos/administer-copilot/manage-for-enterprise/manage-enterprise-policies/).

## Configure networking

If your corporate network restricts users' traffic, add the required URLs to the allowlist for your firewall or proxy. See [AUTOTITLE](https://funcoding.ai/agents/github-copilot/reference/copilot-allowlist-reference/).

If you route traffic via a proxy server, you may need to ask users to configure proxy settings in their environment. You may also need to install custom certificates on your users' machines. For more information, see [AUTOTITLE](https://docs.github.com/copilot/concepts/network-settings).

If your enterprise is on GHE.com, users will also need to configure their environment to authenticate from their development environment. See [AUTOTITLE](https://funcoding.ai/agents/github-copilot/how-tos/copilot-in-your-ide/set-up-copilot/authenticate-to-ghecom/).

## Assign licenses

There are two main ways to grant access to Copilot in an enterprise:

* **Assign licenses directly to users or teams** in the enterprise. This approach simplifies license management at scale and provides the option of granting Copilot licenses to users who don't consume a GitHub Enterprise license. This approach is currently only available for **Copilot Business** licenses.
* **Enable Copilot for organizations**. This approach allows you to choose Copilot Business or Copilot Enterprise for individual organizations and give organization owners control to grant licenses to the users who need them most.

For instructions, see [AUTOTITLE](https://funcoding.ai/agents/github-copilot/how-tos/administer-copilot/manage-for-enterprise/manage-access/grant-access/).