Since Microsoft acquired GitHub, the platform has steadily aligned with the broader Microsoft ecosystem — and that includes how Enterprise licensing and billing are managed. For organisations using GitHub Enterprise Cloud, the shift is clear: licensing is now sourced and governed through the Microsoft Partner channel, bringing GitHub into the same procurement and billing framework you already use for Azure, Microsoft 365, and other Microsoft services.
How GitHub Enterprise Billing Works Today
GitHub uses a unique‑user licensing model, meaning each individual consumes only one licence regardless of how many organisations or deployments they access. The enterprise account serves as the central billing hub across GitHub Enterprise Cloud.
With GitHub now more closely integrated into Microsoft’s commercial frameworks, Enterprise licences follow the same procurement patterns as other Microsoft services. For invoiced customers, usage and any paid add‑ons, such as Secret Protection, appear on a single consolidated bill.
Billing Models You’ll Encounter
GitHub currently operates under two primary billing models:
- Usage‑based billing – now the default for trials started on or after August 1, 2024.
- Volume/subscription agreements – existing customers remain on these until renewal, when they have the option to switch to metered billing.
For most organisations, these models feel familiar – they mirror Microsoft’s broader approach to cloud consumption and subscription‑based licensing.
Why Licensing Now Runs Through the Microsoft Partner Channel
Microsoft’s ownership means GitHub Enterprise is now treated like any other Microsoft cloud product. Licensing is managed through the official Partner channel to ensure:
- procurement aligns with existing CSP or EA workflows
- governance and compliance controls are consistent
- billing becomes simpler and more predictable
- organisations gain consolidated visibility into licence usage and cost attribution
GitHub is no longer “just a developer tool.” It’s part of the modern Microsoft cloud stack, and the commercial model finally reflects that.
Better Visibility, Better Control
GitHub’s enterprise billing platform gives organisations visibility into licence usage, metered features, cost centres, budgets, and spending patterns. Teams can set alerts, control usage, and use GitHub’s REST API to pull detailed usage reports when needed.
This level of insight goes a long way in helping finance and IT teams stay aligned, forecast more accurately, and avoid surprises. The ability to attribute costs to specific groups or cost centres also helps organisations maintain clarity around how engineering resources are consumed.
Need help getting started with GitHub?
Whether you’re exploring GitHub Enterprise for the first time or trying to make sense of the new licensing model through the Microsoft Partner channel, Codify can help.
If you’d like guidance on the right licensing approach, support setting up your environment, or simply want to understand how GitHub fits into your broader Microsoft cloud strategy – get in touch with us. Our team can walk you through your options and help you get started with confidence.
👉 Get in touch for help with GitHub licensing or implementation
Related Blogs
Microsoft 365 E3 and E5 Licensing Changes: What the New Intune Suite Inclusions Mean