GitHub Copilot is a for fee add on to GitHub. GitHub Copilot comes in two flavors, GitHub Copilot Business and GitHub Copilot Enterprise. Each Organization must choose one or the other to assign to users. GitHub documentation describing the differences.

Part 1: Request access to GitHub Copilot

1. If your GitHub Organization is not part of the University of Washington GitHub Enterprise, fill out the Request for Access form to get started.
2. All billing is done through Azure Subscriptions. If you do not have an Azure Subscription, fill out the Azure Subscription form to have one created for you. 
3. To enable GitHub Copilot, you must grant the u_devtools_github_admins group Reader access to your Azure Subscription. This requires entering your Azure Subscription, navigating to Access Control (IAM), and adding u_devtools_github_admins as a Reader role assignment.
4. Be sure to change the "Assignment Type" from time-bound to PERMANENT

 

 

1. Fill out the GitHub Copilot Request Form
2. We will review your information and enable GitHub CoPilot for your Organization.

Part 2: Assigning GitHub Copilot to users

Only the Organization Owner may distribute GitHub Copilot licenses

1. Login to your Organization dashboard.

2. Click Settings in the top navigation.

3. Click Copilot and then Access in the left navigation.

4. Click Start Adding Seats.

5. Choose whether you want to assign a Guthub Copilot seat for all users of your organization or only selected users.

6. If you choose Purchase for selected members, you are presented with this screen to choose the users you would like to assign GitHub Copilot seats to.

7. Click Continue to Purchase to confirm your selections.

 

The GitHub Documentation site has more detailed information about assigning GitHub Copilot seats.

Your budget (work tag) will be billed through Azure each month for the seats you use.