Skip to main content

Chapter 4: Copilot Licensing & Plan Management

Part II: Licensing, Policies & Governance Prerequisites: Chapter 1: Enterprise Subscription & Environment Setup GH-100 Exam Mapping: Domain 3 (Describe how GitHub is deployed, distributed, and licensed — 9%) Verified: 2026-02-01 against official documentation

1. Introduction​

Learning Objectives​

After completing this chapter, you will be able to:

  • Compare Copilot plan tiers (Free, Individual, Business, Enterprise) and identify which is appropriate for enterprise use
  • Enable GitHub Copilot at the enterprise and organization levels
  • Assign and manage Copilot seats using the GitHub UI and CLI
  • Interpret usage reports and billing dashboards to optimize Copilot costs

Exam Domain Coverage​

DomainTopics in This Chapter
D3: Deployment, distribution, licensing (9%)Copilot plan tiers, seat assignment, billing, enterprise enablement

Chapter Overview​

GitHub Copilot is the AI-powered coding assistant at the heart of the enterprise developer experience. However, before any developer on your team can use Copilot, an administrator must choose the right plan, enable the feature at the correct organizational level, and assign seats to the right people.

This chapter walks through the Copilot licensing landscape — from plan tier selection to seat management to billing optimization. You will learn how Copilot licensing integrates with your GitHub Enterprise account, how to control access at the enterprise and organization levels, and how to use usage dashboards to make data-driven decisions about seat allocation.

By the end of this chapter, you will have Copilot enabled for your organization with seats assigned to your team — the prerequisite for every Copilot feature explored in later chapters.


2. Theory & Deep Dive​

Copilot Plan Tiers​

GitHub offers four Copilot plan tiers, each targeting a different audience and scale:

Copilot Free provides limited access to Copilot features for individual developers on personal GitHub accounts. It includes a monthly quota of code completions and chat interactions. Copilot Free is not managed by enterprise administrators and has no policy controls.

Copilot Individual (Pro) is a paid plan for individual developers. It removes the monthly quota and adds features like multi-file editing and Copilot in the CLI. Like Copilot Free, it is tied to personal accounts and cannot be centrally managed by an enterprise.

Copilot Business is the first enterprise-grade tier. It is managed at the organization level and provides:

  • Centralized seat assignment and management
  • Organization-level policy controls (code suggestions, chat, CLI)
  • Audit logging of Copilot usage events
  • Content exclusion rules to protect sensitive repositories
  • IP indemnity for code suggestions
  • No training on your organization's code

Copilot Enterprise includes everything in Copilot Business plus:

  • Knowledge bases built from your organization's repositories
  • Copilot pull request summaries
  • Copilot in GitHub.com search
  • Bing web search integration in Copilot chat
  • Enterprise-level policy management across multiple organizations
FeatureFreeIndividualBusinessEnterprise
Code completionsQuotaUnlimitedUnlimitedUnlimited
Copilot chatQuotaUnlimitedUnlimitedUnlimited
Multi-file editingNoYesYesYes
CLI accessNoYesYesYes
Coding agentNoNoYesYes
Centralized managementNoNoYesYes
Policy controlsNoNoOrganizationEnterprise
Audit loggingNoNoYesYes
Content exclusionsNoNoYesYes
Knowledge basesNoNoNoYes
PR summariesNoNoNoYes
IP indemnityNoNoYesYes

Enterprise Scenario: A 300-developer enterprise evaluates Copilot Business vs. Enterprise. They choose Copilot Enterprise because their organization has 50+ internal repositories they want Copilot to reference via knowledge bases, and their security team requires enterprise-level policy controls that span all three of their organizations.

Enabling Copilot at the Enterprise Level​

Copilot enablement follows the enterprise hierarchy (see Chapter 1: Enterprise Subscription & Environment Setup):

  1. Enterprise level: The enterprise owner enables Copilot and selects the plan tier. This creates a billing relationship and sets the maximum feature set available.
  2. Organization level: Organization owners decide whether their organization participates and which Copilot features are allowed (code completions, chat, CLI, coding agent).
  3. Seat assignment: Organization owners or enterprise owners assign Copilot seats to individual members or teams.

Enterprise owners can enforce a single policy across all organizations or allow each organization to set its own Copilot policies. The enterprise setting acts as a ceiling — organizations cannot enable features that the enterprise has disabled.

Seat Management Strategies​

Effective seat management balances developer productivity with cost control:

Assign to all members: The simplest approach. Every organization member gets a Copilot seat automatically. Best for organizations fully committed to AI-assisted development.

Assign to selected teams: Target Copilot seats to specific teams (e.g., engineering teams) while excluding teams that do not write code (e.g., marketing, sales). This is managed via team-based assignment.

Assign to selected individuals: The most granular approach. Administrators manually assign seats to specific users. Best for pilot programs or organizations with strict budget constraints.

Dynamic seat management: GitHub automatically reclaims seats from users who have not used Copilot in the past 30 days (if the organization enables this setting). Reclaimed seats can be reassigned to new users.

Enterprise Scenario: A 200-developer organization starts a Copilot pilot with 50 seats assigned to their platform engineering team. After 60 days, usage data shows 48 of 50 seats are actively used. They expand to 150 seats for all engineering teams, using the dynamic reclamation feature to automatically free seats from inactive users.

Billing and Cost Optimization​

Copilot billing follows a per-seat-per-month model:

  • Seats are billed on the first day of each billing cycle
  • Mid-cycle additions are prorated
  • Removed seats are not refunded for the current cycle
  • Enterprise billing consolidates all organizations into a single invoice

Key cost optimization strategies:

  • Enable dynamic seat reclamation to avoid paying for unused seats
  • Review the Copilot usage dashboard monthly to identify underutilized seats
  • Start with team-based assignment rather than organization-wide to control initial costs
  • Use the billing API to build custom cost reports and forecasts

Usage Reporting​

GitHub provides several reporting tools for Copilot usage:

Organization-level dashboard: Shows total seats, active users, acceptance rates for code completions, and chat usage metrics. Accessible at Settings > Copilot > Usage.

Enterprise-level dashboard: Aggregates usage across all organizations. Shows trends over time, top-usage organizations, and feature adoption metrics.

REST API (Application Programming Interface): The Copilot usage API provides programmatic access to usage data, enabling custom dashboards and integration with business intelligence tools.

Audit log: Every Copilot event (seat assignment, policy change, feature usage) is logged in the enterprise audit log and can be streamed to a Security Information and Event Management (SIEM) system (see Chapter 6: Security, Audit & Compliance).


3. Diagrams​

Copilot Licensing Hierarchy​

graph TD
ENT[Enterprise Account<br/>Copilot Enterprise Enabled] --> POL{Enterprise Policy<br/>Allowed Features}
POL --> ORG1[Organization A<br/>Copilot: All Features]
POL --> ORG2[Organization B<br/>Copilot: Code + Chat Only]
POL --> ORG3[Organization C<br/>Copilot: Disabled]

ORG1 --> TEAM1[Team: Platform<br/>50 seats assigned]
ORG1 --> TEAM2[Team: Mobile<br/>30 seats assigned]
ORG2 --> TEAM3[Team: Data Eng<br/>20 seats assigned]

TEAM1 --> U1[Developer 1<br/>Active]
TEAM1 --> U2[Developer 2<br/>Active]
TEAM1 --> U3[Developer 3<br/>Inactive 35d → Reclaimed]

style ENT fill:#2d333b,stroke:#539bf5,color:#adbac7
style ORG1 fill:#2d333b,stroke:#57ab5a,color:#adbac7
style ORG2 fill:#2d333b,stroke:#e5c07b,color:#adbac7
style ORG3 fill:#2d333b,stroke:#e06c75,color:#adbac7
style U3 fill:#2d333b,stroke:#e06c75,color:#adbac7

Figure 4.1: Copilot licensing flows from the enterprise account down through organizations to individual seats. Organization C has Copilot disabled by the org owner despite the enterprise allowing it. Developer 3's seat was reclaimed after 35 days of inactivity.

Seat Assignment Decision Flow​

flowchart TD
START[New Copilot Deployment] --> Q1{Budget<br/>Constraint?}
Q1 -->|Unlimited| ALL[Assign to All Members]
Q1 -->|Limited| Q2{Pilot or<br/>Full Rollout?}
Q2 -->|Pilot| IND[Assign to Selected<br/>Individuals]
Q2 -->|Full Rollout| TEAM[Assign to Selected<br/>Teams]
ALL --> RECLAIM[Enable Dynamic<br/>Seat Reclamation]
TEAM --> RECLAIM
IND --> REVIEW[Review Usage<br/>After 30 Days]
RECLAIM --> MONITOR[Monitor Usage<br/>Dashboard Monthly]
REVIEW --> EXPAND{Expand<br/>Seats?}
EXPAND -->|Yes| TEAM
EXPAND -->|No| REVIEW

Figure 4.2: Decision flow for choosing a Copilot seat assignment strategy based on budget and rollout phase.


4. Summary​

Key Takeaways:

  • Copilot Business and Enterprise are the only plans suitable for enterprise use — they provide centralized management, policy controls, audit logging, and IP indemnity
  • Copilot Enterprise adds knowledge bases, PR summaries, and enterprise-level policy management over Business
  • Seat assignment can be organization-wide, team-based, or individual — start with team-based for controlled rollouts
  • Dynamic seat reclamation automatically frees seats from users inactive for 30+ days, optimizing costs
  • Usage dashboards and the Copilot API provide the data needed for cost optimization and adoption tracking

What's Next: See Chapter 5: Copilot Policies & Content Controls for configuring what Copilot can and cannot do within your organization.


5. Hands-On Assignment​

Prerequisites Check: Before starting this lab, ensure you have completed:

  • A working GitHub Enterprise Cloud environment (Chapter 1: Enterprise Subscription & Environment Setup)
  • At least one organization with 2+ members
  • GitHub CLI (gh) installed and authenticated
  • Enterprise owner or organization owner role

Lab: Enable Copilot for Your Organization​

Objective: Enable GitHub Copilot at the enterprise level, configure organization-level settings, and assign seats to team members.

Prerequisites:

  • A GitHub Enterprise Cloud trial (from Chapter 1: Enterprise Subscription & Environment Setup)
  • At least one organization with 2+ members
  • GitHub CLI (gh) installed and authenticated
  • Enterprise owner or organization owner role

Assignment:

  1. Enable Copilot at the enterprise level and select a plan tier
  2. Configure Copilot access for your organization (enable code completions, chat, and CLI)
  3. Assign Copilot seats to at least two organization members
  4. Verify seat assignment via the usage dashboard
  5. Review the billing summary to understand per-seat costs

Expected Outcome: Copilot is enabled and seats are assigned. Members can activate Copilot in their IDE (see Chapter 11: IDE Integration & Developer Experience).

Validation: Navigate to Organization Settings > Copilot > Access and confirm that assigned members show as "Active" or "Pending activation."


6. Step-by-Step Walkthrough​

This section provides a guided solution for the hands-on assignment above. If you completed the assignment independently, you can skip this section or use it to verify your approach.

Step 1: Enable Copilot at the Enterprise Level​

Navigate to your enterprise settings in the browser:

  1. Go to https://github.com/enterprises/YOUR-ENTERPRISE
  2. Click Settings in the sidebar
  3. Click Copilot under the "Policies" section
  4. Select the plan tier (Business or Enterprise)
  5. Set the enterprise-wide policy for Copilot features

Alternatively, use the GitHub CLI:

# View current enterprise Copilot settings
gh api /enterprises/YOUR-ENTERPRISE/copilot/billing \
--jq '{plan: .plan_type, seats: .seats}'

Expected output:

{
"plan": "enterprise",
"seats": {
"total": 0,
"assigned": 0
}
}

Step 2: Configure Organization-Level Copilot Access​

# View current organization Copilot settings
gh api /orgs/YOUR-ORG/copilot/billing \
--jq '{plan: .plan_type, seat_management: .seat_management_setting}'

In the browser:

  1. Go to https://github.com/organizations/YOUR-ORG/settings/copilot
  2. Under "Policies", enable the features you want: code completions, Copilot Chat, Copilot in the CLI
  3. Under "Access", choose your seat assignment strategy: "All members", "Selected teams", or "Selected members"

Step 3: Assign Copilot Seats​

# Assign a Copilot seat to a specific user
gh api --method POST /orgs/YOUR-ORG/copilot/billing/selected_users \
-f selected_usernames[]="developer-1" \
-f selected_usernames[]="developer-2"

Expected output:

{
"seats_created": 2
}

For team-based assignment:

# Assign Copilot seats to all members of a team
gh api --method POST /orgs/YOUR-ORG/copilot/billing/selected_teams \
-f selected_teams[]="platform-engineering"

Step 4: Verify Seat Assignment​

# List all assigned Copilot seats
gh api /orgs/YOUR-ORG/copilot/billing/seats \
--jq '.seats[] | {user: .assignee.login, created: .created_at, last_activity: .last_activity_at}'

Expected output:

{
"user": "developer-1",
"created": "2026-02-01T10:00:00Z",
"last_activity": null
}
{
"user": "developer-2",
"created": "2026-02-01T10:00:00Z",
"last_activity": null
}

The last_activity field will be null until the user activates Copilot in their IDE.

Step 5: Review Billing Summary​

# View Copilot billing summary for the organization
gh api /orgs/YOUR-ORG/copilot/billing \
--jq '{plan: .plan_type, total_seats: .seats, used_seats: .seats_billed}'

Navigate to Enterprise Settings > Billing > Copilot in the browser for a visual dashboard showing:

  • Total seats purchased
  • Seats in use
  • Monthly cost projection
  • Seat activity trends

Verification​

Confirm setup is complete:

# Final verification: list all Copilot-enabled users
gh api /orgs/YOUR-ORG/copilot/billing/seats \
--jq '.total_seats'

You should see at least 2 seats assigned. Ask your team members to open VS Code and verify they see the Copilot icon in the status bar.


7. Q&A — Chapter Review​

Instructions: Select the best answer for each question. Answers and explanations follow after all questions.

Question 1​

Which Copilot plan tier is the minimum required for centralized seat management by an organization administrator?

  • A) Copilot Free
  • B) Copilot Individual
  • C) Copilot Business
  • D) Copilot Enterprise

Question 2​

An enterprise owner enables Copilot Enterprise and allows all features. An organization owner within that enterprise disables Copilot Chat for their organization. What happens when a developer in that organization tries to use Copilot Chat?

  • A) Copilot Chat works because the enterprise allows it
  • B) Copilot Chat is blocked because the organization disabled it
  • C) The developer receives a prompt to upgrade their plan
  • D) Copilot Chat works but is not audited

Question 3​

What is the default inactivity period after which GitHub can automatically reclaim a Copilot seat?

  • A) 7 days
  • B) 14 days
  • C) 30 days
  • D) 90 days

Question 4​

Which feature is available in Copilot Enterprise but NOT in Copilot Business?

  • A) Code completions in the IDE
  • B) Copilot Chat
  • C) Knowledge bases from organization repositories
  • D) Audit logging

Question 5​

A company wants to start a Copilot pilot with 25 engineers before expanding to the full 200-person engineering department. Which seat assignment strategy is most appropriate?

  • A) Assign to all organization members
  • B) Assign to selected individuals
  • C) Assign to selected teams
  • D) Enable dynamic reclamation only

Question 6​

Where can an enterprise owner view aggregated Copilot usage data across all organizations?

  • A) Organization Settings > Copilot > Usage
  • B) Enterprise Settings > Copilot > Usage
  • C) GitHub.com dashboard homepage
  • D) The Copilot IDE extension settings

Question 7​

How are mid-cycle Copilot seat additions billed?

  • A) Full month charge regardless of when added
  • B) Prorated for the remaining days in the billing cycle
  • C) Free until the next billing cycle
  • D) Charged at double rate for the first month

Question 8​

Which API endpoint provides programmatic access to Copilot usage metrics?

  • A) /orgs/{org}/actions/usage
  • B) /orgs/{org}/copilot/billing
  • C) /orgs/{org}/settings/copilot
  • D) /enterprises/{enterprise}/audit-log

Question 9​

An organization has 100 Copilot seats assigned. After enabling dynamic seat reclamation, 15 users have been inactive for over 30 days. What happens to their seats?

  • A) Nothing — seats remain assigned until manually removed
  • B) Users receive a warning email but keep their seats
  • C) Seats are automatically reclaimed and become available for reassignment
  • D) The organization is charged a reduced rate for inactive seats

Question 10​

Which of the following is NOT included with Copilot Business?

  • A) IP indemnity for code suggestions
  • B) Content exclusion rules
  • C) Pull request summaries generated by Copilot
  • D) Organization-level policy controls

Answer Key​

QAnswerExplanation
1CCopilot Business is the first tier that provides centralized seat management. Free and Individual are personal-account plans without management capabilities.
2BOrganization policies can be more restrictive than enterprise policies. The enterprise setting is a ceiling — organizations can disable features the enterprise allows, but cannot enable features the enterprise disables.
3CGitHub's dynamic seat reclamation uses a 30-day inactivity threshold. After 30 days without Copilot usage, the seat can be automatically reclaimed.
4CKnowledge bases, which allow Copilot to reference your organization's internal repositories, are exclusive to Copilot Enterprise.
5BFor a pilot with specific individuals before a broader rollout, assigning to selected individuals gives the most control. Team-based assignment is better for the expansion phase.
6BEnterprise-level Copilot usage dashboards are found under Enterprise Settings > Copilot > Usage, which aggregates data across all organizations.
7BMid-cycle seat additions are prorated — you only pay for the remaining days in the current billing cycle.
8BThe /orgs/{org}/copilot/billing endpoint and its sub-endpoints provide programmatic access to Copilot usage and seat data.
9CWith dynamic seat reclamation enabled, seats are automatically reclaimed from users inactive for 30+ days and become available for reassignment to other users.
10CPull request summaries generated by Copilot are a Copilot Enterprise exclusive feature. Business includes IP indemnity, content exclusions, and policy controls.