[EDI - Drivers] Align "About billing for GitHub Copilot" in your orga…

…nization/enterprise (#56711) Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Isaac Brown <101839405+isaacmbrown@users.noreply.github.com> Co-authored-by: Siara <108543037+SiaraMist@users.noreply.github.com> Co-authored-by: SiaraMist <siaramist@github.com>
github · docs-bot · Jul 25, 2025 · Jul 25, 2025 · Jul 25, 2025 · Jul 25, 2025
commit 6c48627268b69a902fc52c7dd7085d840a904824
diff --git a/content/copilot/reference/copilot-billing/azure-billing.md b/content/copilot/reference/copilot-billing/azure-billing.md
@@ -0,0 +1,27 @@
+---
+title: Copilot billing through Azure
+shortTitle: Azure billing
+intro: 'Learn how metered billing for {% data variables.product.prodname_copilot %} works when you are connected to an Azure subscription, including billing cycles, invoicing, and usage tracking.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+allowTitleToDifferFromFilename: true
+contentType: reference
+---
+
+This article provides information about how {% data variables.product.prodname_copilot_short %} metered billing works when you connect an Azure subscription to your organization or enterprise account.
+
+## Metered billing activation
+
+* When you connect your Azure subscription and enable metered billing, usage data begins flowing from {% data variables.product.github %} to Azure.
+* Any {% data variables.product.prodname_copilot_short %} usage from the start of your current {% data variables.product.github %} billing cycle up to the point when you enable metered billing via Azure will be billed through {% data variables.product.prodname_dotcom %} on your next billing date.
+* Usage from the date Azure metered billing is enabled through to the end of that calendar month will be charged via Azure, and appears on your Azure invoice at the start of the next month.
+
+For more information, see [AUTOTITLE](/billing/managing-the-plan-for-your-github-account/connecting-an-azure-subscription).
+
+## Usage tracking and invoicing
+
+* Usage data is transmitted from {% data variables.product.github %} to Azure **daily**.
+* You can **track daily usage (number of seats) in Azure**.
+* Actual billing and payments are processed **monthly**, based on the number of seats used during that calendar month.
diff --git a/content/copilot/reference/copilot-billing/billing-cycle.md b/content/copilot/reference/copilot-billing/billing-cycle.md
@@ -0,0 +1,26 @@
+---
+title: Copilot billing cycle
+intro: 'Learn about the billing cycle for {% data variables.product.prodname_copilot %} in organizations and enterprises.'
+shortTitle: Billing cycle
+versions:
+  feature: copilot
+topics:
+  - Copilot
+allowTitleToDifferFromFilename: true
+contentType: reference
+---
+
+## Billing cycle basics
+
+* The billing cycle for {% data variables.product.prodname_copilot_short %} in organizations and enterprises is **monthly**.
+* Charges are calculated based on the **number of {% data variables.product.prodname_copilot_short %} seats (licenses) assigned during the billing cycle**.
+
+## When does billing occur?
+
+Billed users are calculated once per month, at the end of each billing cycle, based on the number of {% data variables.product.prodname_copilot_short %} seats that are assigned. You can add or remove seats at any time during the billing cycle.
+
+For reference information about seat assignment, see [AUTOTITLE](/copilot/reference/copilot-billing/seat-assignment).
+
+{% data reusables.billing.authorization-charge %}
+
+{% data reusables.copilot.billing-timezone %}
diff --git a/content/copilot/reference/copilot-billing/index.md b/content/copilot/reference/copilot-billing/index.md
@@ -0,0 +1,14 @@
+---
+title: Copilot billing
+shortTitle: Copilot billing
+intro: 'Find billing information about {% data variables.product.prodname_copilot %}.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+children:
+  - /billing-cycle
+  - /seat-assignment
+  - /license-changes
+  - /azure-billing
+---
diff --git a/content/copilot/reference/copilot-billing/license-changes.md b/content/copilot/reference/copilot-billing/license-changes.md
@@ -0,0 +1,83 @@
+---
+title: Making changes to your Copilot license
+shortTitle: License changes
+intro: 'Learn how changes to {% data variables.product.prodname_copilot %} licenses affect billing and user access for organizations, enterprises, and personal accounts.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+allowTitleToDifferFromFilename: true
+contentType: reference
+---
+
+This article provides details about what happens when you add or remove {% data variables.product.prodname_copilot_short %} licenses, for organizations, enterprises, and personal accounts. Use it to check:
+* **What** happens to billing and access
+* **When** those changes take effect
+* **How** proration or refunds are handled
+
+## Personal accounts
+
+What you need to know about the following actions:
+
+* **Upgrading:** If you move from a monthly to a yearly plan, the change is **immediate**. You are charged a prorated amount for the new plan.
+* **Downgrading/canceling:**
+  * **Monthly plan:** Access remains until the end of the current cycle. **No refund for unused time**.
+  * **Yearly plan:** Access remains until the end of the annual term already paid for.
+* **Switching plans:** Proration applies when switching between monthly and yearly, and the new plan starts **right away**.
+
+## Organizations
+
+What you need to know about the following actions:
+
+### Adding seats
+
+* **Billing:** Additional {% data variables.product.prodname_copilot_short %} seats are billed for the remainder of the current billing cycle. Charges are prorated based on the date seats are added.
+* **Access:** Users assigned to new seats get access **immediately** after assignment.
+
+### Removing seats
+
+* **Billing:**
+  * Billing for that user stops at the end of the cycle.
+  * Reduced seat count takes effect at the start of the **next billing cycle**.
+  * **No refunds are issued for unused time in the current cycle.**
+* **Access:** If a seat is unassigned during a billing cycle, the affected user can still access {% data variables.product.prodname_copilot_short %} until the end of the cycle.
+
+Additionally:
+
+* If **{% data variables.product.prodname_copilot_short %} is disabled at the organization level or licensed users are removed from the organization**: Affected users lose access to {% data variables.product.prodname_copilot_short %} immediately. Billing for affected users stops at the end of the cycle. If a user is restored to the organization or {% data variables.product.prodname_copilot_short %} is reenabled during the billing cycle, the users regain access to {% data variables.product.prodname_copilot_short %} **immediately**.
+
+## Enterprises
+
+What you need to know about the following actions:
+
+### Adding seats
+
+* **Billing:** Additional seats are billed on a prorated basis for the remainder of the current billing cycle.
+* **Access:** Assigned users gain **immediate access** to {% data variables.product.prodname_copilot_short %}.
+
+### Removing seats
+
+* **Billing:**
+  * The reduced seat count is effective in the **next billing cycle**.
+  * **There are no refunds for the current cycle.**
+* **Access:** Users lose access **immediately** if their seat is removed, but seats can be reassigned within the current cycle until the new count applies.
+
+Additionally:
+
+* **If an organization with {% data variables.product.prodname_copilot_short %} seats is removed from an enterprise**: Billing for those seats will stop at the end of the billing cycle. The users who had seats assigned by the removed organization will lose access to {% data variables.product.prodname_copilot_short %} unless they receive a seat through another organization.
+
+* **If {% data variables.product.prodname_copilot_short %} is disabled at the enterprise level**: Any user with a {% data variables.product.prodname_copilot_short %} license will lose access to {% data variables.product.prodname_copilot_short %} immediately. Billing for that user stops at the end of the cycle. If {% data variables.product.prodname_copilot_short %} is reenabled, users regain access to {% data variables.product.prodname_copilot_short %} immediately.
+
+## In summary
+
+* **Proration:** Applies when adding seats/licenses or upgrading plans. You pay only for the portion of the billing cycle remaining.
+* **Access:** Assignments and plan changes are effective immediately for affected users.
+* **Removing or canceling:** No refunds are issued for unused time; access continues until the end of the cycle paid for, unless a seat/license is unassigned.
+* **Reassignment:** In {% data variables.copilot.copilot_for_business %} and {% data variables.copilot.copilot_enterprise %} plans, unassigned seats/licenses can be immediately reassigned to another user during the current billing cycle.
+
+| Scenario                        | Plan                | When is billing affected? | Is proration applied? | When does access change? | Refund for unused time? |
+|----------------------------------|---------------------|--------------------------|----------------------|--------------------------|-------------------------|
+| Add seat/license                 | {% data variables.copilot.copilot_business_short %}, {% data variables.copilot.copilot_enterprise_short %}| Next bill             | Yes                  | Immediately              | N/A                     |
+| Remove seat/license              | {% data variables.copilot.copilot_business_short %}, {% data variables.copilot.copilot_enterprise_short %}e| Next bill             | N/A                  | Immediately              | No                      |
+| Cancel subscription              | All plans           | End of cycle            | N/A                  | End of cycle            | No                      |
+| Upgrade/downgrade/switch plan    | All plans           | Immediate                | Yes                  | Immediately              | N/A (proration instead) |
diff --git a/content/copilot/reference/copilot-billing/seat-assignment.md b/content/copilot/reference/copilot-billing/seat-assignment.md
@@ -0,0 +1,27 @@
+---
+title: Copilot seat assignment
+shortTitle: Seat assignment
+intro: 'Learn how seat assignment for {% data variables.product.prodname_copilot %} works in organizations and enterprises, including billing, user eligibility, and assignment management.'
+versions:
+  feature: copilot
+topics:
+  - Copilot
+contentType: reference
+---
+
+This article explains how seat assignment for {% data variables.product.prodname_copilot_short %} works in organizations and enterprises.
+
+## What is a {% data variables.product.prodname_copilot_short %} seat?
+
+A **{% data variables.product.prodname_copilot_short %} seat** is a license to use {% data variables.product.prodname_copilot_short %}, assigned to a unique user account through a {% data variables.copilot.copilot_business_short %} or a {% data variables.copilot.copilot_enterprise_short %} plan.
+
+Users must be assigned a seat to access {% data variables.product.prodname_copilot_short %} features under an organization or enterprise plan
+
+## Seat assignment management
+
+* **Who assigns seats:** Organization owners. Seats are assigned to specific user accounts. See [AUTOTITLE](/copilot/how-tos/administer/organizations/managing-access-to-github-copilot-in-your-organization/granting-access-to-copilot-for-members-of-your-organization).
+* **Where:** Seat assignment can be managed in the {% data variables.product.github %} organization settings or via the REST API.
+* **If all assigned seats are removed, the organization's {% data variables.product.prodname_copilot_short %} plan is canceled.**
+* **If a user with an active {% data variables.copilot.copilot_pro_short %} or {% data variables.copilot.copilot_pro_plus_short %} plan is assigned a seat in a {% data variables.copilot.copilot_business_short %} or {% data variables.copilot.copilot_enterprise_short %} plan**, their personal plan is automatically canceled, and a prorated refund for any remaining portion of their personal billing cycle is issued. The user will now use {% data variables.product.prodname_copilot_short %} under the organization's policies.
+* **If a single user receives a seat from multiple organizations within the same enterprise**, the enterprise is only billed once per billing cycle for that unique user. One organization that assigned {% data variables.product.prodname_copilot_short %} to the user is chosen at random each month to be billed for the seat.
+* **If a user is assigned both a  {% data variables.copilot.copilot_business_short %} and a {% data variables.copilot.copilot_enterprise_short %} seat from different organizations within the same enterprise**, only the {% data variables.copilot.copilot_enterprise_short %} seat is billed. The charge is at the {% data variables.copilot.copilot_enterprise_short %} rate from the time the {% data variables.copilot.copilot_enterprise_short %} seat is assigned. The user will have access to the all the features and capabilities available under the {% data variables.copilot.copilot_enterprise_short %} plan.
diff --git a/content/copilot/reference/index.md b/content/copilot/reference/index.md
@@ -7,6 +7,7 @@ versions:
 topics:
   - Copilot
 children:
+  - /copilot-billing
   - /cheat-sheet
   - /keyboard-shortcuts
   - /policy-conflicts

diff --git a/data/reusables/copilot/billing-timezone.md b/data/reusables/copilot/billing-timezone.md
@@ -0,0 +1 @@
+{% data variables.product.prodname_copilot %} uses UTC but aligns charges with your billing cycle’s timezone. For example, if your cycle ends at 11:59 PM EST, canceling a seat at 7:00 PM EST will show as 12:00 AM UTC, but you won’t be charged for that seat in the next cycle.
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		{% data variables.product.prodname_copilot %} uses UTC but aligns charges with your billing cycle’s timezone. For example, if your cycle ends at 11:59 PM EST, canceling a seat at 7:00 PM EST will show as 12:00 AM UTC, but you won’t be charged for that seat in the next cycle.