GitHub Copilot Premium Request Scenarios

This guide outlines two scenarios to help you set up GitHub Copilot in your GitHub Enterprise environment for optimal cost efficiency and usage control.

• Scenario 1: Selective onboarding to Copilot Enterprise for heavy users of Premium Requests.
• Scenario 2: Setting separate spending limits for specific Copilot users.

Note: Both scenarios require creating a new budget. By default, Copilot Premium Requests have a $0 budget applied, which must be removed for the options below to work properly.

Scenario 1: Selective Onboarding to Copilot Enterprise for Premium Request Power Users

Situation: You want to onboard a subset of users to Copilot Enterprise because it may be more cost-effective for heavy users of Premium Requests.

Note: Copilot Enterprise is only available for GitHub Enterprise (GHE) customers. It is not available for customers on non-GHE SKUs.

Background

• Copilot Business:

  • 300 Premium Requests/month
  • $19/user/month
  • Additional requests: $0.04 per request

• Copilot Enterprise:

  • 1,000 Premium Requests/month
  • $39/user/month
  • Additional requests: $0.04 per request

Cost Comparison

Tip: Any user making 800 or more Premium Requests per month will save money by being on Copilot Enterprise.

Directions

1. Download your GitHub Copilot Premium Request Usage Report following these instructions.
2. Aggregate the report to identify users who exceed 800 Premium Requests/month.
3. Create a new organization within your GitHub Enterprise.
4. Invite the power users to the new organization.
5. Assign Copilot Enterprise licenses to those users in the new organization.
6. Continue monitoring usage to ensure Copilot Enterprise remains the most cost-effective option for these users.

Scenario 2: Setting Separate Spending Limits for Specific Copilot Users

Situation: You want to set a separate budget for certain users to ensure they can continue using Premium Requests beyond their default entitlement.

Background

There are currently two supported methods to assign custom spending limits for specific users:

1. Create a separate Organization and set a budget specific to that Organization.
2. Create a Cost Center, assign users to it, and set a budget specific to that Cost Center.

Note: A user can belong to only one Cost Center at a time. If you already use Cost Centers for other purposes, only Option 1 may be viable.

Option 1: Use a Separate Organization Budget

1. Download your GitHub Copilot Premium Request Usage Report following these instructions.

2. Aggregate the report to identify users who may benefit from an increased budget.

3. Create a new organization within your GitHub Enterprise.

4. Invite the selected users to the new organization.

5. Assign Copilot licenses to those users.

6. Create a budget at the Enterprise level.

7. Configure the budget:

   • Budget Type: SKU-level budget
   • Product: Copilot
   • SKU: Copilot Premium Request
   • Budget Scope: The newly created organization
   • Budget Amount: Your desired limit
   • Alerts: Optional thresholds for budget notifications

8. Monitor usage to ensure the budget aligns with actual usage patterns.

Option 2: Use a Cost Center Budget

1. Download your GitHub Copilot Premium Request Usage Report following these instructions.

2. Aggregate the report to identify users who may benefit from an increased budget.

3. Create a new Cost Center.

4. Assign users to the Cost Center using the API.

5. Create a budget at the Enterprise level.

6. Configure the budget:

   • Budget Type: SKU-level budget
   • Product: Copilot
   • SKU: Copilot Premium Request
   • Budget Scope: The newly created Cost Center
   • Budget Amount: Your desired limit
   • Alerts: Optional thresholds for budget notifications

7. Continue monitoring Premium Request usage to validate the budget's effectiveness.

Tip: You can combine both scenarios if you'd like specific Copilot Enterprise users to have different spending limits than other Copilot Enterprise users.