How does Github Copilot/ Enterprise EMU billing works

[sumitmalik51]

🏷️ Discussion Type

Question

Hi everyone,

I'm looking for clarification on how GitHub Copilot Enterprise billing works in an Enterprise Managed Users (EMU) environment.

Let's say we have the following scenario:

An EMU user is provisioned and assigned a Copilot Enterprise seat on the 1st of the month.
The user accesses GitHub.
Later the same day, the user is removed from the organization (or deprovisioned through SCIM/IdP), causing the Copilot seat to be unassigned.

My questions are:

Is the Copilot Enterprise seat billed only for the period it was assigned, or is a full month's charge incurred?
Does billing differ if the user is simply removed from the organization versus fully deprovisioned as an EMU account?
Are there any minimum billing periods for Copilot Enterprise seats?
Is there documentation that specifically covers short-lived or temporary EMU users in training/lab environments?

We're evaluating usage patterns for temporary lab users and want to better understand the billing implications of assigning and removing Copilot Enterprise seats within a very short timeframe.

Thanks in advance for any guidance!

[SwapnilSadhu007]

Copilot Enterprise seats are billed monthly per seat. If a user is assigned a seat at any point in the month, the organization is charged for that full month — even if the user is removed or deprovisioned the same day.

Key points:

1. Billing is monthly, not prorated daily or hourly.
2. Removing a user from the org or fully deprovisioning them as an EMU account both end the seat assignment, but the charge for that month remains.
3. Minimum billing period is one month per seat.
4. For temporary or lab users, avoid assigning Copilot Enterprise seats unless you plan for them to stay active for the month.

GitHub’s documentation confirms that Copilot Enterprise billing is seat‑based and monthly, with no special handling for short‑lived EMU accounts.