What the Microsoft Extended Service Term (EST) Really Means for Your Business
The short version: Starting May 4, 2026, Microsoft will remove the free grace period for expired CSP subscriptions. In its place is a paid Extended Service Term that bills monthly at your standard rate plus a 3% surcharge or 23% if no regular monthly term option exists for that SKU. It will be automatically, unless you explicitly cancel. This article explains what changed, who is affected, what it costs, and what most guides are leaving out.
The assumption that no longer holds
For years, Microsoft CSP subscriptions had a forgiving end-of-term behaviour. When a subscription expired without being renewed, services didn't cut off immediately. Instead, partners and customers entered a free grace period of 30 days of continued access and up to 90 days of continued access with no billing, no urgency. Time to chase approvals, renegotiate terms, or simply decide.
That buffer shaped how the industry built its renewal processes. Workflows were designed around it. Automations assumed it. Customer conversations were timed to it.
Now it's gone. Effective May 4, 2026, Microsoft will remove the free grace period entirely.
A subscription that reaches end-of-term without a renewal or explicit cancellation no longer has free access. It automatically converts into a paid Extended Service Term, billed monthly at your standard rate plus a 3% surcharge, or 23% for SKUs where no monthly plan is available.
The operational logic that underpins most renewal workflows today is built on a premise that will no longer exist.
How end-of-term used to work
Under the historic CSP model, partners had two choices when a subscription reached end-of-term.
- To renew: Service continued uninterrupted.
- To turn off auto-renew: which triggered a grace period of free service for a limited time.
That grace period absorbed:
- slow procurement cycles,
- delayed approvals, and
- gaps between conversations.
It cost nothing. It required no instruction. And as long as it existed, the consequences of inaction were minimal. That model ends on May 4, 2026.
What the Extended Service Term actually is
An Extended Service Term (EST) is a new end-of-term option for partners that need more time to decide between cancelling a subscription or renewing it.
Microsoft positions it as a paid bridge, service continuity while a partner and customer resolve their next step.
Under the new model, every eligible subscription reaches end-of-term with three possible outcomes:
| Option | What happens | Cost |
|---|---|---|
| Renew | Subscription continues on its current term type | Standard rate |
| Cancel at end of term | Access stops immediately. Data is retained but the subscription cannot be recovered or reactivated. | €0 — but access ends |
| Extended Service Term | Service continues month-to-month. Partners can renew, upgrade, or cancel at any point during the term. | Monthly rate + 3% uplift (or +23% if no monthly SKU exists for that product) |
EST functions as a monthly subscription with one meaningful difference. Unlike standard monthly terms, which enforce a 7-day cancellation window, EST can be cancelled at any point. That flexibility is the justification for the surcharge.
But that flexibility only works in your favour when EST is chosen deliberately. When it's inherited by default, from inaction, from a misconfigured API call, from an automation that wasn't updated, it is simply a cost that wasn't budgeted.
The six dates that define this change
Microsoft has been staging this rollout since late 2025. Several of these milestones have already passed.
NOV 3, 2025 (EST available in CSP Sandbox)
- Partners can experience the new end-of-term options for new subscriptions purchased after this date.
FEB 1, 2026 (EST price list preview published)
- Partners can review EST SKUs and pricing ahead of the enforcement date.
FEB 6–15, 2026 (Automatic backfill conversion)
- Microsoft converts all eligible subscriptions with autoRenewEnabled: false but no explicit cancel instruction — directly to EST.
FEB 16, 2026 (EST live in production)
- Partners can view and set end-of-term options via Partner Center UI and API.
FEB 27, 2026 (EST subscription export available)
- Partners can download a full list of subscriptions currently configured for EST.
MAY 4, 2026 (Enforcement date)
- Free grace period fully retired. All eligible subscriptions follow EST rules.
- New renewal parameters available in the CloudCockpit Self Service Portal.
Four of these milestones have already passed. The backfill has already run. EST is already live in production.
If you haven't reviewed your subscription portfolio since February 15, some of your subscriptions may already be configured to roll into EST. Without you having made that decision.
Who this affects
The scope of EST is broader than it initially appears.
In scope:
- Commercial, Education, and Non-profit license-based services
- All subscription durations: monthly, annual, and triennial
- All channels: CSP, MCA-E, and Buy-Online
- All markets globally
- Specialized offers and end-of-sale-with-conversion SKUs
Out of scope:
- Trial subscriptions
- End-of-sale SKUs without a conversion path
- Subscriptions with term end dates before May 4, 2026
If a subscription was purchased or renewed after April 1, 2025 and its term ends after May 4, 2026, it is eligible for EST.
What 3% actually costs
Three percent sounds like a rounding error. Applied across a real portfolio: multiple customers, multiple subscriptions, multiple months, it isn't.
The surcharge is calculated on the standard monthly term rate for each SKU. Every subscription that enters EST carries this cost for every month it remains there. That cost continues, month to month, until a partner explicitly cancels or converts back to a standard SKU.
For a subset of products where no monthly plan exists, the uplift isn't 3%. It's 23%.
The risk isn't in any single subscription. It's in the number of subscriptions that silently convert to EST because no explicit instruction was ever issued. The more subscriptions in a portfolio, the larger that number tends to be.
The risk most guides are missing: promotions don't transfer
IMPORTANT: Promotional pricing does not carry over to EST.
When a subscription moves to EST, it does not automatically carry over the promotional pricing that was applied to the original subscription. This is the most underreported consequence of the change.
A customer whose subscription was on a promotional rate enters EST at the standard monthly rate, plus the 3% uplift. The promotion doesn't follow. The customer may not expect the difference. The invoice reflects it anyway.
For partners, the implications are immediate. Margin calculations built on promotional rates become inaccurate the moment a subscription enters EST. Resale pricing built on those rates is now exposed. And customer trust takes a direct hit if the pricing change arrives without prior notice.
Current promotions should be taken into account when deciding whether to go to EST. That decision needs to happen before end-of-term, not after the first EST invoice arrives.
Any customer on promotional pricing with an EST-eligible subscription needs to be in your renewal workflow before May 4 — as an explicit conversation, not a footnote
The technical trap: autoRenewEnabled: false no longer means cancel
Under the old model, setting autoRenewEnabled: false was a clean, unambiguous instruction.
It meant: when this term ends, do not renew. Predictable. Reliable.
Now, under the EST model, that same call no longer produces that outcome.
Here is what happens today when you send that call:
- Your API call sets autoRenewEnabled: false
- Microsoft returns a response confirming autoRenewEnabled: false
- Within 24 hours, a background process detects that no explicit cancellation instruction was included
- The subscription is converted to EST with autoRenewEnabled: true
- A webhook fires: subscription-migrated-to-extended-service-term
If your system caches the initial response and doesn't monitor the webhook, you believe the subscription is set to cancel. It isn't.
The correct instruction requires an explicit scheduledActions block with actionType: Cancel
Not just setting autoRenewEnabled to false.
IMPORTANT: Any integration, PSA tool, or automation written before EST existed almost certainly doesn't include this. Find it. Fix it before May 4.
What changes once a subscription is in EST
| Action | Regular subscription | EST subscription |
|---|---|---|
| Change quantity | ✅ Yes | ❌ No |
| Change term duration | ✅ Yes | ❌ No |
| Change billing plan | ✅ Yes | ❌ No |
| Cancel | ✅ Within standard cancellation window | ✅ At any time |
| Upgrade to higher SKU | ✅ Yes | ✅ Yes (with restrictions) |
| Convert back to base SKU | N/A | ✅ Yes |
| Transfer to another CSP | ✅ Yes | ⚠️ Convert to base SKU first |
| Promotions applied | ✅ Yes | ❌ Not automatically |
Two primary restrictions apply:
Quantity Increases:
- These are blocked. Customers needing additional licenses must first revert to a standard SKU.
Transfers:
- Direct partner-to-partner transfers are not supported from EST. A conversion to the base SKU must be completed before the transfer.
When EST is the right choice
EST is not inherently a problem. Customers occasionally need time between the end-of-term and a final renewal decision. While the previous grace period met that need at no cost, EST serves the same purpose for a fee.
There are specific situations where EST is a sound commercial decision:
Pending Approvals: Renewal intent is clear, but the purchase order hasn't been signed. EST maintains continuity while the process concludes.
Evaluation of Upgrade Paths: The customer plans to move to a different SKU, but the transition plan isn't ready. EST keeps services running during migration planning.
Contract Renegotiations: New pricing or scope is under discussion. EST buys time without cutting off access mid-conversation.
The critical distinction: EST chosen deliberately, with the customer's awareness, as a short-term bridge is a legitimate commercial tool. EST inherited by default, through inaction, is pure cost leakage.
The difference between these two outcomes is a matter of process, not product.
Conclusion: Three things to do this week
The May 4 enforcement date is close. Three actions matter most right now.
1. Run the EST subscription audit in Partner Center.
Use the AI Assist export to generate a complete list of subscriptions currently configured to roll into EST.
In Partner Center, enter this prompt: "Please generate a list of all my subscriptions that are set to go to EST at the end of their term."
The export takes up to 6 hours to generate and can only be requested once per 24-hour period. Compare the results against actual customer intent. Make changes before the enforcement date.
The CloudCockpit Platform is designed to make this process easier. If you need help, send us a message, contact your account manager or the operations team.
2. Audit your automation logic.
Any integration, PSA tool, or custom script setting autoRenewEnabled: false without an explicit scheduledActions: Cancel instruction is producing the wrong outcome under EST rules. Find it. Fix it before May 4.
3. Identify every customer on promotional pricing.
Map which customers are on promotional rates and which of their subscriptions are EST-eligible. Each of those customers needs a renewal conversation before their term ends. The financial difference when promotions don't transfer to EST is material — and the customer won't know unless you tell them first.
Each of these represents a category of cost that materialises without a trigger. No alert, no invoice line that explains clearly what happened. The mechanism is silent and the cost is real.
The next article in this series is a step-by-step operational checklist. It covers exactly how to read the EST export, how to correct API calls, how to structure renewal conversations with customers on promotional pricing, and how to model the true cost exposure across your portfolio.
