Skip to content

Instantly share code, notes, and snippets.

@bthomas2622

bthomas2622/copilot-for-business-resources.md Secret

Last active April 30, 2024 22:19
Show Gist options
  • Save bthomas2622/fbf87a742a33cb5bb9a2826b112689c8 to your computer and use it in GitHub Desktop.
Save bthomas2622/fbf87a742a33cb5bb9a2826b112689c8 to your computer and use it in GitHub Desktop.
Download ZIP
Copilot for Business Resources
Raw
copilot-for-business-resources.md

Copilot for Business (CfB) Resources

Table of Contents

Official Resources

Copilot Enablement

Pricing and Terms

Copilot for Business (CfB) FAQ

How do I enable/purchase Copilot for Business (GitHub Enterprise Cloud)?

  1. Set up Copilot for Business subscription for your enterprise.
  2. GitHub Enterprise Account Administrator can then enable Organizations Copilot access in the Enterprise Account Policy Settings. (Video Guide)
  3. GitHub Organization Administrator can then enable usage, set policy, and purchase for members in the Organization settings. (Video Guide)

How is Copilot for Business billed?

The GitHub Copilot for Business subscription is available on a monthly cycle, and is billed at $19 per user per month. Billing for GitHub Copilot for Business is processed at the end of each billing cycle. Billed users are calculated based on the number of assigned GitHub Copilot seats.

How do I manage users and licenses for Copilot for Business?

Currently Copilot for Business licenses are purchased and assigned at the Organization level via the UI (Org Settings -> Copilot -> Access) or the API.

The 3 different options for user assignment within an organization are:

  1. Purchase for all members
  2. Purchase for selected users
  3. Purchase for selected GitHub Teams

User Assignment Best Practices (4 Options):

  1. Purchase for all members within an existing organization.

  2. Create a dedicated company-copilot organization with no code where Copilot is purchased for all members. Members of the organization can then be synchronized with an Identity Provider group via SCIM for automated Copilot access. This is a good option for enteprises that want to enable for a group of users across multiple organizations.

  3. Purchase Copilot for a copilot-team within an organization. And utilize Team Synchronization to synchronized that team with an Identity Provider team for automated Copilot access.

  4. Automate access within an organization via the Copilot for Business API.

CfB REST API Capabilities

  • Get organization settings for Copilot for Business
  • Get organization seat information including active/inactive users
  • List all Copilot for Business seat assignments for an organization
  • Add/Remove users and teams to the Copilot for Business subscription for an organization
  • Get Copilot for Business seat assignment details for a user

How do I leverage Copilot for Business with GitHub Enterprise Server?

Currently GitHub Copilot for Business can only be authenticated in the IDE through a GitHub.com account. GitHub Enterprise offers a unified licensing model that provides GHE users with a GHE Cloud license for each GHE Server license. Check with your GitHub Account Manager if you are unsure if you are on the unified license model today. Companies using GHES today with unified license plan can create an associated GitHub Cloud Enterprise (optionally linked to their GHES via GitHub Connect).

With an associated GitHub.com Enterprise, GHES developers can be onboarded into a GHEC organization that is purely for membership purposes (no code). Copilot for Business can be enabled for those developers following the instructions above, then these developers will be able to authenticate with GitHub.com in the Copilot IDE extension, allowing these developers for leverage the tool while working on code stored in their GHES environment.

What is Copilot Chat?

Copilot Chat is a chat interface in the editor that's focused on developer scenarios and natively integrates with VS Code, Visual Studio, and JetBrains IDEs. GitHub Copilot chat is not just a chat window. It understands what code a developer has typed, what error messages are shown, and it's deeply integrated into the IDE. A developer can get in-depth analysis and explanations of what code blocks are intended to do, generate unit tests, and even get proposed fixes to bugs.

GitHub Blog

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment