4.9 KiB
title, intro, allowTitleToDifferFromFilename, redirect_from, versions, audience, contentType, topics, shortTitle
| title | intro | allowTitleToDifferFromFilename | redirect_from | versions | audience | contentType | topics | shortTitle | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Setting up a dedicated enterprise for GitHub Copilot Business | Learn how to configure an enterprise account for use with {% data variables.product.prodname_copilot %} only. | true |
|
|
|
how-tos |
|
Set up a dedicated enterprise |
You can create an enterprise account specifically for managing {% data variables.copilot.copilot_business_short %} licenses, without adopting {% data variables.product.prodname_enterprise %}. With this account, you will have access to enterprise-grade integrations with identity providers for authentication and provisioning, without needing to pay for {% data variables.product.prodname_enterprise %} licenses. See AUTOTITLE.
1. Create an enterprise account
Important
If you're purchasing {% data variables.copilot.copilot_business_short %} through {% data variables.product.company_short %}'s sales team, your enterprise account will be created for you. Skip to step 2.
You need to create an enterprise account, and the way to do that is to start a trial of {% data variables.product.prodname_ghe_cloud %}.
Don’t create any organizations during setup. Adding users to organizations assigns them {% data variables.product.prodname_enterprise %} licenses, while adding users directly to the enterprise keeps your setup limited to {% data variables.copilot.copilot_business_short %}.
2. Add users to your enterprise
Once you have an enterprise account, add the people who will receive {% data variables.copilot.copilot_business_short %} licenses. How you add users depends on your enterprise type.
Enterprise with personal accounts
Invite users directly to your enterprise. For detailed steps, see AUTOTITLE.
Enterprise with managed users
If your enterprise uses {% data variables.product.prodname_emus %}, you must provision user accounts from your identity provider (IdP) through SCIM. For setup and provisioning guidance, see AUTOTITLE.
Provisioned users will appear automatically in your enterprise’s People list. Later, you'll assign {% data variables.copilot.copilot_business_short %} licenses directly to these users or to enterprise teams synced with your IdP.
3. Create teams (optional)
You can group users to scale license assignment by creating and managing enterprise teams. If you plan to manage access in groups, create those groups now. See AUTOTITLE.
4. Enable {% data variables.product.prodname_copilot_short %} for the enterprise
{% data reusables.copilot-business-for-non-ghe.enable-copilot %}
5. Assign {% data variables.product.prodname_copilot_short %} licenses
Next, give people access to {% data variables.product.prodname_copilot_short %} by assigning {% data variables.copilot.copilot_business_short %} licenses to users or enterprise teams directly from the enterprise level.
For detailed steps, see AUTOTITLE.
6. Convert your trial to a paid enterprise account
To continue using {% data variables.copilot.copilot_business_short %} after your trial, convert your trial to a paid enterprise account. See AUTOTITLE.
Next steps
After setting up {% data variables.copilot.copilot_business_short %} for your enterprise, you can help your developers start using {% data variables.product.prodname_copilot_short %} and measure its impact across your organization. See AUTOTITLE.
If you ever want to access the full range of {% data variables.product.company_short %} features in the future, you can create organizations and add users to them.