GitHub Copilot is now one of the most commercially significant AI products in enterprise IT budgets — and one of the most poorly governed. Organisations are simultaneously paying for GitHub Copilot Business at the individual developer level, negotiating M365 Copilot at the EA level, and in some cases running both with incomplete understanding of the overlap. The licensing structure across Copilot products has become a genuine cost and compliance problem at scale.
This guide covers the GitHub Copilot licensing structure specifically — tier differences, buying options, governance requirements, and how GitHub Copilot interacts with (and sometimes duplicates) capabilities available through M365 Copilot. If you are managing a developer organisation of 50+ people, this analysis will likely identify immediate cost savings.
GitHub Copilot Tier Structure
GitHub Copilot is available in four tiers, each with distinct capabilities, pricing, and target populations. The tiers are not simply "more features for more money" — they reflect genuinely different deployment architectures and governance models.
| Tier | Price (per user/month) | Key Capabilities | Enterprise Relevance |
|---|---|---|---|
| GitHub Copilot Free | £0 | Limited completions (2,000/month), limited chat (50 messages/month), no policy controls | Not for enterprise — no admin controls, usage caps |
| GitHub Copilot Individual | £10 (billed annually) | Unlimited completions, unlimited chat, IDE integration, GitHub.com integration | Individual billing only — no enterprise policy, no tenant administration |
| GitHub Copilot Business | £19 (billed annually) | All Individual features + organisation-level policy controls, audit logs, IP indemnification, content exclusion, seat management via admin console | Minimum viable enterprise tier — provides basic governance and compliance controls |
| GitHub Copilot Enterprise | £39 (billed annually) | All Business features + GitHub.com knowledge base integration, pull request summaries, Copilot-in-GitHub.com, fine-tuned model support, enterprise-managed users (EMU) integration | Required for organisations that want Copilot connected to their internal repositories and custom knowledge |
What Actually Differentiates Business from Enterprise
The £20/user/month gap between Business and Enterprise is significant — for 200 developers, that is £48,000 annually. The Enterprise premium primarily buys:
- Knowledge bases: GitHub Copilot Enterprise can index your organisation's internal repositories and provide contextually relevant completions based on your own codebase, not just public GitHub training data. For organisations with substantial proprietary code libraries, this is genuinely valuable — completions become aligned to your coding standards, internal APIs, and architectural patterns.
- Pull request summaries: Automated PR summarisation using Copilot, reducing review overhead and improving documentation quality at merge.
- Copilot chat on GitHub.com: Chat interface integrated into the GitHub.com web experience, not just IDE plugins. Relevant for teams that do significant code review and issue triage in the browser.
- Enterprise Managed Users (EMU) integration: EMU allows organisations with strict identity governance requirements to manage GitHub user identities entirely through Entra ID — a compliance requirement for regulated industries that Business does not satisfy.
- Fine-tuned model support: The ability to connect custom-trained models for code completion, relevant for organisations with highly specialised languages or frameworks not well-represented in GitHub's training data.
The honest assessment for most organisations: if your developers work primarily with common languages and frameworks (Python, JavaScript, Java, C#, TypeScript), and you do not have strict identity governance requirements, GitHub Copilot Business delivers 80–85% of the Enterprise value at 49% of the price. The Enterprise tier is clearly justified when internal knowledge base integration or EMU compliance is a real requirement — not a theoretical nice-to-have.
Buying Options: EA, CSP, and Direct
GitHub Copilot can be purchased through three channels, and the commercial terms differ significantly:
GitHub.com Direct Billing
GitHub Copilot Business and Enterprise can be purchased directly through GitHub.com with a credit card or invoice billing arrangement. For organisations under 100 developers, this is the simplest option. The pricing is list price with no negotiation. Billing is monthly per active seat — the billing model is based on assigned seats, not active usage, so unassigned but provisioned seats do not bill.
Direct billing provides flexibility (cancel any seat with 30 days' notice) but no enterprise discount, no integration with EA financial reporting, and no MACC contribution. For developer tools at small scale, this is acceptable. At 200+ developers, the commercial case for moving to EA or CSP becomes compelling.
Microsoft Enterprise Agreement
GitHub Copilot Business and Enterprise can be included in a Microsoft Enterprise Agreement as part of the GitHub Enterprise enrolment — either standalone or bundled with GitHub Enterprise Cloud or Server. EA inclusion provides:
- Negotiated discount: Typically 10–20% below list for Copilot at meaningful developer populations (100+ seats), depending on overall EA spend level and negotiation quality
- Price lock: Three-year price stability versus the annual repricing risk of direct billing
- MACC contribution: GitHub Copilot Enterprise under EA can count toward Microsoft Azure Consumption Commitments in certain configurations — relevant for large Azure deployments seeking to maximise MACC leverage
- Consolidated billing and true-up: Annual true-up rather than monthly seat-by-seat management simplifies operations for IT finance teams
- Unified account team relationship: GitHub Copilot sits within the same commercial conversation as M365, Azure, and GitHub Enterprise — creating cross-product negotiation leverage
The tradeoff is EA's three-year commitment structure. For a developer population that is growing rapidly or whose Copilot adoption is still being validated, the flexibility cost of committing to a three-year EA for GitHub Copilot is real. The GitHub Enterprise licensing guide covers EA versus direct purchasing decisions in full.
CSP Channel
GitHub Copilot is available through Microsoft CSP partners, subject to NCE terms. Annual CSP subscriptions are available with the same 72-hour cancellation window that applies to other NCE products. For organisations already managing Microsoft 365 through CSP, adding GitHub Copilot to the same partner relationship simplifies billing. The discount structure through CSP is typically lower than EA for equivalent seat counts (0–8% versus 10–20% in EA).
GitHub Copilot vs M365 Copilot: The Overlap Problem
This is the area where enterprise organisations most frequently waste money. GitHub Copilot and Microsoft 365 Copilot are marketed as complementary products — and they are, at a product level. But at a feature level, there is meaningful overlap that creates double-payment risk for specific capabilities.
| Capability | GitHub Copilot Business/Enterprise | M365 Copilot | Overlap? |
|---|---|---|---|
| Code completion in IDE | Core feature | Not included | No overlap |
| Code review in GitHub.com | Enterprise tier | Not included | No overlap |
| General chat / Q&A (GPT-4 based) | Included | Included | Partial overlap — both provide GPT-4 chat; different context sources |
| Code generation in chat | Native capability | Limited via Copilot for Microsoft 365 in some apps | Partial overlap for simple scripts |
| Document and meeting summarisation | Not included | Core feature | No overlap |
| Azure DevOps integration | Limited (GitHub Actions, not ADO pipelines) | Not included | No overlap |
| GitHub Advanced Security | Separate add-on — not included in Copilot | Not included | No overlap (separate purchase) |
The practical implication: a developer who has both GitHub Copilot Business (£19/month) and M365 Copilot (£30/month) is paying £49/month for two AI assistants. The GitHub Copilot is better for code completion. The M365 Copilot is better for meetings, documents, and Outlook. There is partial overlap in the general chat capability — both users can ask general coding questions via chat in each product. This overlap does not justify discontinuing either product for developers who need both, but it should be understood before purchasing decisions are made.
Where the overlap becomes a real cost problem is when IT or procurement teams purchase M365 Copilot for all employees including developers under the assumption that it covers developer AI needs — and then separately approve GitHub Copilot purchases at the developer team level without the two decisions being commercially connected. At 300 developers with both products, the annual cost is £176,400 — a number that warrants a deliberate decision, not an accidental accumulation.
Seat Governance: The Largest Cost Leak
In organisations with 100+ GitHub Copilot seats, the most common source of ongoing overspend is not the tier selection or buying channel — it is seat proliferation without usage review. GitHub Copilot seats assigned but unused continue billing until actively deprovisioned. The nature of developer tooling makes this particularly common: seats are provisioned for a project, the project ends, the developer moves to other tools, and the seat continues billing indefinitely.
Effective GitHub Copilot seat governance requires three disciplines:
1. Assigned vs Active Usage Monitoring
GitHub's organisation admin console provides usage data showing which assigned Copilot seats generated completions or chat interactions in the last 30 days. "Active seat" is typically defined as a seat with at least one Copilot interaction in the measurement period. In most enterprise deployments, 15–25% of assigned seats are inactive in any given 30-day window — seats assigned to developers who are between projects, on leave, or who have stopped using Copilot without deprovisioning.
Monthly review of the active seat report and deprovisioning of persistently inactive seats (inactive for 60+ consecutive days is a reasonable threshold) typically recovers 10–20% of Copilot spend without affecting any developer who actually uses the tool.
2. Centralised Provisioning Policy
In organisations without a centralised provisioning policy, GitHub Copilot seats are frequently requested and approved at the team or manager level without finance oversight. The cumulative result is hundreds of seat assignments made without aggregate budget visibility. A centralised provisioning policy — requiring IT/procurement approval for Copilot seat assignments above team-level allocations — adds minimal operational overhead while providing the budget visibility needed to manage total cost.
3. Annual Tier Review
GitHub Copilot's tier structure and pricing have changed since launch and will continue to change. An annual review of whether Business or Enterprise is justified — based on actual utilisation of Enterprise-exclusive features (knowledge bases, EMU, PR summaries) — is worth the 2–3 hours it takes. Organisations that moved to Enterprise without validating the use of Enterprise-specific features frequently find that Business would have served equally well at half the per-seat premium.
Optimising Your GitHub Copilot and Developer AI Spend?
We help enterprise organisations structure their GitHub Copilot, M365 Copilot, and GitHub Enterprise licensing to eliminate overlap, reduce unnecessary tier upgrades, and negotiate EA inclusion at the right time. Developer AI is now a material line item — it deserves the same commercial rigour as your M365 or Azure agreements.
Developer Licensing Review
We analyse your GitHub Copilot, GitHub Enterprise, M365 Copilot, and Azure DevOps spend and identify consolidation and optimisation opportunities.
Request ReviewEA Negotiation for GitHub
Including GitHub Copilot in your EA? We help you negotiate the right tier, discount structure, and true-up terms before you sign.
EA Negotiation ServicesCopilot Governance Framework
Build the seat governance, usage monitoring, and provisioning controls that prevent Copilot spend from drifting upward without management awareness.
Get FrameworkGitHub Copilot Negotiation Strategy
For organisations purchasing GitHub Copilot through EA, there are several negotiation levers that are frequently underused:
Bundle Leverage with GitHub Enterprise
Microsoft's preferred commercial approach is to bundle GitHub Copilot with GitHub Enterprise Cloud or Server licences. The bundle can be commercially advantageous — the combined discount on the bundle is sometimes higher than the sum of individual product discounts. But the bundle can also force you to a tier you do not need. If you only need GitHub Copilot Business, negotiate it independently before accepting a bundled proposal that defaults you to Enterprise for features you have not validated needing.
Competitive Pressure
GitHub Copilot faces genuine competitive alternatives: Amazon Q Developer (formerly CodeWhisperer), JetBrains AI Assistant, Tabnine, and others. The quality gap between GitHub Copilot and its closest competitors has narrowed since Copilot's launch. Microsoft's account teams are aware that competitive alternatives exist, and referencing a competitor evaluation — credibly and with specific capability comparisons — creates price flexibility that does not exist when buying is perceived as inevitable.
Adoption-Based Step-Up
One of the most commercially rational structures for GitHub Copilot EA inclusion is a committed-seat-with-step-up arrangement: commit to a baseline of current active users at a negotiated discount, with a defined step-up mechanism to add seats at the same discount as adoption grows. This avoids both overpaying (committing to seats before you have the users) and underpaying (getting a low discount because your initial commitment is small). The developer licensing EA optimisation guide covers negotiation strategy for the full developer tooling stack.