Content reviewed: 12 October 2026
User assignment, purchased quantity, commitment term and billing frequency are four separate facts. Record them before planning a change.
This guide covers ordinary NCE licence-based subscriptions in CSP. Software subscriptions, Marketplace offers and other products can have different rules.
Monthly billing and commitment
An annual commitment can be billed monthly. Billing frequency determines when payments fall due; it does not provide the right to reduce quantity whenever a user leaves.
Ask for the exact term, billing plan, quantity, start date and renewal date. Compare proposals for the same period.
Plan seasonal staffing before ordering. Confirm a more flexible term for the specific product rather than assuming every offer supports it.
The seven-day window
For ordinary NCE licence-based subscriptions, Microsoft permits cancellation within seven days, or 168 hours, of the applicable term, with proration. Quantity reductions concern licences added at purchase, renewal or midterm within their own seven-day window. Adding a few seats does not reopen cancellation of the original order.
Check the NCE cancellation policy and subscription management guidance for the actual product and operation.
Use the exact timestamp and available operation, not a local calendar-day estimate. Confirm the applicable deadline with the partner.
Overview of changes
| Request | What changes | What to verify |
|---|---|---|
| Remove a leaver’s licence | User assignment | Data and service access |
| Reduce purchased seats | Subscription quantity | Allowed quantity and deadline |
| Add an employee | Assignment or purchased quantity | Available seats and order |
| Set term-end choice | Renewal, cancellation or EST | Explicit instruction and effective date |
| Suspend subscription | Service state | User impact and continued billing |
| Change CSP partner | Commercial relationship | Supported transfer and continuity |
| Change product | Services and order | Supported conversion and data |
One operation does not automatically perform the others. Confirm each commercial change against the correct subscription ID.
Unassigned seats and billed quantity
An unassigned seat can remain within the paid commitment. It may be available for another permitted use, but being unassigned does not itself reduce the invoice.
Report unassigned capacity, a planned renewal reduction and a completed commercial reduction separately. They are not interchangeable savings.
Check the reassignment rights of the product too. An available seat does not necessarily permit unlimited changes of licence holder.
Reduction windows for added seats
The partner can check Customers → customer → subscription → View licenses to reduce, or Get a Subscription by ID. Microsoft documents the reducible quantities and deadlines. For example, an original 100 seats outside their window plus 20 added later should not be treated as a fresh order of all 120 seats. Confirm the actual permitted reduction.
After every change, retain the subscription ID, resulting quantity, timestamp and confirmation. These distinguish original capacity from later additions.
Check bulk onboarding orders promptly. Licences can be assigned quickly, while correcting a wrong purchase has a limited commercial window.
Plan renewal before the deadline
Set internal deadlines for inventory, approval and partner confirmation. Choose the lead time according to the actual renewal and contract.
Combine current assignments with confirmed hires, departures and exceptions. Approval establishes the target products and quantity; partner confirmation must establish the actual scheduled renewal.
At term end, confirm renewal, cancellation at expiry or paid EST. An auto-renew-off label alone no longer describes every eligible subscription’s outcome.
EST: auto-renew off may still lead to charges
Since 4 May 2026, eligible subscriptions no longer receive the former free continuation after non-renewal. They need renewal, cancellation at expiration or paid Extended Service Term. Check eligibility and exceptions in the current EST documentation.
For an eligible subscription, auto-renew false without explicit cancellation is insufficient. Microsoft describes a background change of the term-end instruction to EST with auto-renew true, usually within hours and within 24 hours after a false-only API update. Ask for the actual term-end instruction and a later verification, not just the first API response or an old screenshot.
EST is billed monthly at the corresponding monthly-term SKU rate plus 3%; the documentation states 23% when no monthly plan exists. This is not 3% above any historical annual invoice. Confirm the market, currency and actual partner EST quote. EST cancellation is prorated for the days it was active.
Cancel at expiration stops service at term end, and that subscription cannot be recovered or reactivated. Data retention is separate and does not provide continued working access. Prepare replacement entitlements, exports or migration for the affected services before confirming cancellation.
Three possible term-end outcomes
| Outcome | What the partner should confirm | Result |
|---|---|---|
| Normal renewal | Renew and any target quantity | A new ordinary licence term begins. |
| Cancellation at expiry | Explicit Cancel for TermEnd | Services end; the same subscription cannot be reactivated. |
| EST continuation | RenewToExtendedServiceTerm and effective date | Paid monthly EST continues until cancellation or conversion. |
The scheduledActions field matters to a partner using the API. A customer should request a clear outcome, subscription ID, effective date and quantity. autoRenewEnabled alone does not establish explicit cancellation. The documentation distinguishes eligible offers and exceptions; not every subscription necessarily has all three options.
EST does not allow direct seat-count changes
During EST, quantity, term and billing plan cannot be changed directly. Conversion to a supported ordinary SKU can allow a quantity reduction and a new cancellation window. Microsoft says that subscription ID is retained. Do not infer whether a new window exists solely from a changed identifier.
EST cannot use a direct partner-to-partner CSP transfer. Microsoft recommends conversion to an ordinary SKU first, followed by transfer. A parallel replacement purchase can encounter a product’s 300-seat limit. Plan a partner change before automatic entry into EST.
Recheck renewal plans after midterm changes
For ordinary scheduled changes, Microsoft lists quantity changes, upgrades, cancellation or disabling auto-renew as actions that can delete the saved plan. The EST documentation also says midterm changes do not themselves remove the chosen EST term-end outcome. These are separate records: after a change, verify both future quantity/product and the renew/cancel/EST choice.
Partial upgrades and cancellation windows
A subscription produced by a partial upgrade inherits the original cancellation window under the cancellation policy. A new ID alone does not establish a new right to cancel. Verify the particular supported operation rather than using “upgrade and cancel” as a general rule.

Example: 100 purchased, eight unassigned
A hypothetical company has 100 purchased seats and 92 assigned. Four unassigned seats cover confirmed hires, two form an operational reserve and two currently have no planned use.
The audit identifies two seats as candidates for a commercial reduction. Check the date, permitted operation and future staffing before including a confirmed reduction in the budget.
Assigning one of those seats to a new employee uses existing purchased capacity. It does not reduce the invoice.
Suspension does not end the commitment
Suspending an ordinary NCE subscription interrupts customer access while the partner continues to be billed. It does not replace cancellation or a quantity reduction. After reactivation, recheck the term-end choice: the EST documentation describes suspend/reactivate setting it to EST, which must be adjusted to the intended outcome.
Confirm the consequences for users before suspension. Service interruption and billing are separate results.
For a disputed order, give the partner the subscription ID, timestamps and operation history. Distinguish a commercial request from a documented system fault. Another customer’s reported exception does not establish eligibility for your subscription.
Verify the completed renewal
- Compare the confirmed order and the actual quantity.
- Verify product, commitment length and billing.
- Check the continuity of user services.
- Check the invoice and change period.
- Save the confirmation and schedule the next internal review.
A partner’s “configured” message is not the final check. Confirm the actual subscription state and billing outcome.
Frequently asked questions
Does removing a user’s licence reduce the invoice?
Not automatically. It changes assignment rather than purchased quantity. Commercial reductions need their own eligible operation and confirmation.
Is auto-renew false enough to end service?
Not for an eligible EST subscription. Confirm explicit Cancel at term end; a false-only setting can be converted to EST.
Can quantity be reduced directly during EST?
No. Assess a supported conversion to an ordinary SKU, for which Microsoft permits a quantity reduction.
Does suspension have the same effect as cancellation?
No. It interrupts access while ordinary NCE billing continues for the partner. Recheck the term-end choice after reactivation too.
Does a partial upgrade reopen cancellation?
Not automatically: it inherits the original window. Conversion out of EST is a different documented operation that can open a new window while retaining the ID.
Keep an order record
Keep the product, subscription ID, purchased quantity, commitment, billing frequency and renewal timestamp. These records distinguish user administration from changes to the commercial subscription.








