Azure Reserved VM Instances Are Disappearing July 1: How Partners Can Protect Customer Savings Before It's Too Late
A step-by-step action guide for Microsoft CSP partners managing Azure cost optimization at scale
Your customers' Azure savings are about to evaporate — unless you act in the next 49 days.
Microsoft has announced that dozens of Azure Reserved Virtual Machine (VM) Instance SKUs will no longer be available for purchase or renewal starting July 1, 2026. This is not a minor SKU cleanup. It is a structural change that will force pay-as-you-go billing on workloads currently receiving up to 72% reservation discounts.
For partners managing tens or hundreds of customer Azure subscriptions, the financial exposure is significant. A single expired Dv3 reservation on a medium workload can increase monthly compute costs by 40-60% overnight. At distributor scale — 900 partners, 40,000 companies — the collective impact runs into millions.
This post tells you exactly which VM families are affected, what happens if you do nothing, and the concrete steps you must take before June 30.
What Changed? The Full List of Discontinued Reservations
Microsoft published Partner Center announcement #5 on May 4, 2026, confirming that select VM series will exit the reservation program. The discontinuation applies to:
One-Year RIs Ending (July 1, 2026)
| VM Family | Common Use Cases |
|---|---|
| Av2 / Amv2 | Entry-level workloads, dev/test, small web apps |
| Bv1 | Burst-capable workloads, intermittent compute |
| D / Ds / Dv2 / Dsv2 | General-purpose compute, business apps, mid-tier databases |
| F / Fs / Fsv2 | Compute-optimized, batch processing, gaming servers |
| G / Gs | Memory-optimized, large SAP HANA, high-performance databases |
| Ls / Lsv2 | Storage-optimized, NoSQL databases, big data |
One-Year AND Three-Year RIs Ending (July 1, 2026)
| VM Family | Impact Severity |
|---|---|
| Dv3 / Dsv3 | HIGH — One of the most commonly reserved families in SMB and mid-market |
| Ev3 / Esv3 | HIGH — Memory-optimized workhorses for ERP, databases, analytics |
China exception: This change does not currently apply to customers in China.
The Cost Impact: What "Pay-As-You-Go" Really Means
Here is the reality partners must communicate to customers:
An expired RI does not auto-migrate to anything. Even if auto-renew is enabled in Cost Management, the reservation simply ceases to exist, and the underlying VMs bill at on-demand rates.
| VM Size | PAYG Rate (West Europe, approx.) | RI Discount | Monthly Cost Increase |
|---|---|---|---|
| D4s v3 | ~$292/month | ~60% | +$175/month |
| E4s v3 | ~$292/month | ~60% | +$175/month |
| F4s v2 | ~$150/month | ~55% | +$83/month |
| D8s v3 | ~$583/month | ~60% | +$350/month |
Even with auto-renew enabled, impacted VM families will lapse to pay-as-you-go. Microsoft explicitly states: "If no action is taken before July 1, 2026, impacted VM workloads will be billed at pay-as-you-go rates once their corresponding RIs expire, even if auto-renew is enabled."
What Should Partners Do? A 5-Step Action Plan
The deadline is non-negotiable. Here is the exact workflow every partner should run now:
Step 1: Audit All Active Reservations (Do This Week)
Run the following Azure CLI command for every customer tenant with Azure Plan subscriptions:
bash
az consumption reservation summary list \
--reservation-order-id \
--query "[?contains(to_string(name),'Dv3') || contains(to_string(name),'Dsv3') || contains(to_string(name),'Ev3') || contains(to_string(name),'Esv3') || contains(to_string(name),'Dv2') || contains(to_string(name),'Dsv2') || contains(to_string(name),'Av2') || contains(to_string(name),'Bv1') || contains(to_string(name),'Fsv2') || contains(to_string(name),'Ls')]"
For broader discovery, use the Azure Retail Prices API or export reservation details from Cost Management + Billing in the Azure portal. Filter for VM families in the affected list and note the expiration date of each.
Deliverable: A spreadsheet per customer showing: VM family, RI term, expiration date, VM count, and estimated annual cost at PAYG if the RI lapses.
Step 2: Segment Customers by Risk Level
| Risk Tier | Criteria | Action |
|---|---|---|
| 🔴 Critical | RIs expiring between July 1 and December 31, 2026 | Immediate customer contact + migration planning |
| 🟡 High | RIs expiring in Q1-Q2 2027 | Schedule migration conversation within 30 days |
| 🟢 Planned | RIs with >12 months remaining | Add to quarterly business review agenda |
Step 3: Present the Three Migration Options
For every affected reservation, customers have three valid paths. Present all three with quantified recommendations:
Option A: Migrate to Newer-Generation VM Series (Recommended)
Microsoft provides dedicated migration guidance for D/Ds/Dv2/Dsv2 and Ls series. Newer families (Dv5, Dsv5, Ev5, Esv5, Lsv3) offer better performance-per-watt and maintain reservation eligibility.
- Pros: Continued RI savings, performance uplift, long-term support
- Cons: Requires VM redeployment or resize; application compatibility testing
- Partner revenue: Billable migration project, validation testing, performance benchmarking
Option B: Switch to Azure Savings Plan for Compute
If the customer's compute profile is variable or they run mixed VM families, a Savings Plan offers flexibility that RIs do not. Savings Plans apply discounts based on committed hourly spend, not specific VM families.
- Pros: Flexibility across VM families, regions, and sizes; no migration required
- Cons: Lower discount depth than RIs for stable workloads (~15-25% vs. 40-72%)
- Partner revenue: FinOps consulting, commitment sizing, ongoing optimization
Option C: Accept Pay-As-You-Go and Optimize Elsewhere
For declining workloads or short-term projects, absorbing the PAYG rate and rightsizing VMs (smaller SKUs, shutdown schedules, spot instances) may be the most rational choice.
- Pros: No migration effort; maximum flexibility
- Cons: Highest compute cost; no budget predictability
- Partner revenue: Rightsizing audit, scheduled automation, Spot VM implementation
Step 4: Execute Before June 30, 2026
For RIs expiring on or shortly after July 1, the migration or replacement must be completed before the deadline. There is no grace period. Microsoft will not extend reservation availability.
Critical dates:
- May 13, 2026 (today): T-49 to deadline
- May 31, 2026: Final reasonable date to initiate customer conversations
- June 15, 2026: Final reasonable date to begin technical migration work
- June 30, 2026: Hard cutoff — all decisions must be implemented
Step 5: Document and Invoice the Advisory Work
This is not a cost of doing business. This is billable advisory work with measurable customer value. Every hour you spend auditing reservations, sizing alternatives, and executing migrations should be tracked and invoiced.
Suggested service SKUs:
- Azure Cost Optimization Assessment (fixed fee)
- RI Migration Project (time & materials)
- Savings Plan Sizing & Commitment (fixed fee + percentage of first-year savings)
- Ongoing FinOps Management (monthly retainer)
Key Takeaways
- July 1, 2026 is a hard deadline. After this date, no new purchases or renewals of impacted RIs are possible.
- D/Ds/Dv2/Dsv3 and Ev3/Esv3 are the highest-impact families — these are widely used in general-purpose and memory-optimized workloads.
- Auto-renew does not protect customers. Lapsed RIs bill at pay-as-you-go rates automatically.
- Partners have three viable paths: migrate to newer VM series (recommended), switch to Savings Plans, or optimize on PAYG.
- This is billable work. Every partner should treat RI expiration audits as a professional service with clear deliverables and pricing.
- Distributor-scale math: If 10% of Cloud Factory's 40,000 customer companies each have $20,000/year in expiring RIs, the collective cost exposure is $80 million annually at PAYG rates.
Source: Microsoft Partner Center — Changes to Azure Reserved VM Instances
Ready to protect your customers' Azure savings? Explore Cloud Factory's Azure FinOps services →
Category: Azure Meta Description: Microsoft is discontinuing select Azure Reserved VM Instances on July 1, 2026. Learn which VM families are affected and the 5-step action plan every CSP partner must follow to protect customer savings. Meta Keywords: Azure Reserved VM Instances, Azure RI discontinuation, Azure savings plan, Azure cost optimization, Microsoft CSP partner, Azure VM migration, Dv3 RI, Ev3 RI, Azure FinOps, Cloud Factory Author: Cloud Factory Team