GitHub Copilot Licensing Has Changed: What Enterprise Buyers Need to Know

As of June 1, 2026, GitHub Copilot no longer operates on a straightforward per-user-per-month subscription license. Microsoft has shifted to a “hybrid model” that is based on a per-user-per-month subscription with a consumption-based component baked in. This consumption-based component ties spend directly to usage, and the implications for enterprise buyers are significant.

If you are already under a contract, considering adding GitHub Copilot, in active negotiations, or approaching a renewal, here is what you need to understand.

How the New GitHub Copilot Licensing Model Works

The new structure is still per-user-per-month, but each user subscription now comes with a pool of GitHub AI credits:

• Copilot Business tier customers pay $19 per-user-per-month and receive 1,900 AI Credits
• Copilot Enterprise tier customers pay $39 per-user-per-month and receive 3,900 AI Credits

Copilot Business and Enterprise customers will get 3,000 and 7,000 AI Credits respectively from 6/1 to 9/1. Organizations that build usage habits around these promotional numbers will face a material reduction when that period ends and need to ensure this is planned appropriately. The AI credits are pooled at the “entity level” and can be shared across users within your organization.

Draw down on the AI Credits is ultimately based on usage tied to the number of tokens consumed (input, output, and cached context) and the model. Each token is priced based on the API rate for the model used, and this total is converted into AI credits, with 1 AI Credit equaling $.01 USD. The API rates are found on Microsoft’s website.

What Happens When You Exceed Your GitHub Copilot Credit Limit

When the AI Credit pool runs out, you either stop or pay more. If you allow additional usage, which is set up by the customer, every AI Credit beyond the pool is billed at public per-credit rates. If you don’t allow additional usage, usage is blocked until the next month when the AI credits refresh.

You can also put usage “caps” in place that can be set at different “levels.”.

• User Level: A cap on the individual’s use of the shared AI credit pool along with a cap set on the additional usage.
• Cost Center Level: No cap on the use of the shared AI credit pool, only a cap on the additional usage.
• Enterprise Level: No cap on the use of the shared AI credit pool, only a cap on the additional usage for the entire enterprise or set of users.

Where Enterprise Buyers Have Leverage with GitHub Copilot

The consumption model creates real negotiating opportunities for buyers who come prepared. The key pressure points are:

• AI Credit Allocation Logic. The standard AI Credit allotments of 1,900 and 3,900 are not tailored to your organization. Ask Microsoft to forecast your specific consumption, project when you will eclipse your allocation, and justify the base numbers. If they cannot, that is leverage. If they can, you have data to negotiate allocations that actually reflect your needs.
• API Rates and Overage Discounts. Overage is billed at standard public API rates. There is no automatic volume discount. Negotiate a discount structure on overage before you sign or push for a higher base AI Credit pool to reduce the likelihood of hitting it.
• The Promotional Period Cliff. If you are signing or renewing now, negotiate to lock in the elevated promotional token levels as your permanent base. At minimum, secure a defined path for what happens when the promotion expires.

GitHub Copilot and the embedded consumption-based licensing model introduce variable cost exposure that grows with use, which benefits Microsoft and can be very problematic for customers that don’t set things up properly.

Enterprise buyers who understand the mechanics, challenge the assumptions baked into the pricing, obtain the right level of transparency, and negotiate the right protections before signing will be in a far better position than those who treat this as a routine renewal.

It is also important to ensure your larger Microsoft relationship (EA, Azure, Unified Support, LinkedIn) and the associated renewals are being accounted for appropriately as well.  When available and appropriate, it is always best to treat things holistically, when it comes to Microsoft negotiations.

However, enterprise buyers who don’t treat the purchase of GitHub Copilot appropriately will take on cost exposure they did not anticipate. If you are navigating a negotiation, about to enter into one or have a renewal coming up, learn more about how UpperEdge’s Microsoft Advisory Practice can help you negotiate from a position of leverage.