.png)
Key takeaways
1
Azure announced that purchases and renewals for Reserved VM Instances covering specific legacy VM series would end on July 1, 2026.
2
Durable Task Scheduler Consumption became generally available, creating a usage-based cost model worth incorporating into Azure Functions and agent-workflow forecasts.
3
Microsoft expanded its AI and developer tooling, while Azure Files introduced GA support for Entra-only identities for SMB.
May’s Azure updates span commitment pricing, serverless orchestration, AI models, networking, storage, identity, and security.
For FinOps teams, the most important announcement was Microsoft’s planned change to Reserved VM Instance availability. The July 1 deadline was announced in May, giving teams time to review affected reservations, utilization, workload roadmaps, and alternative commitment options.
Other May releases matter less because they directly reduce cloud spend and more because they change the underlying cost model, architecture, or operational choices teams need to forecast.
For FinOps teams, the most important announcement was Microsoft’s planned change to Reserved VM Instance availability. The July 1 deadline was announced in May, giving teams time to review affected reservations, utilization, workload roadmaps, and alternative commitment options.
Other May releases matter less because they directly reduce cloud spend and more because they change the underlying cost model, architecture, or operational choices teams need to forecast.
Azure RIs: July 1 deadline for legacy VM series
Microsoft announced that starting July 1, 2026, purchases and renewals would no longer be available for one-year RIs covering Av2, Amv2, Bv1, D, Ds, Dv2, Dsv2, F, Fs, Fsv2, G, Gs, Ls, and Lsv2 VM series.
For Dv3, Dsv3, Ev3, and Esv3, both one-year and three-year RI purchases and renewals were affected. Existing reservations continue to provide their applicable discounts through the end of their terms. See Microsoft’s legacy RI transition guide.
For Dv3, Dsv3, Ev3, and Esv3, both one-year and three-year RI purchases and renewals were affected. Existing reservations continue to provide their applicable discounts through the end of their terms. See Microsoft’s legacy RI transition guide.
What should FinOps teams review?
For each affected reservation, record:
Do not assume every legacy VM family belongs to this July 1 change. HBv2 and NP-series, for example, had separate RI changes on April 2, 2026.
- VM family and region
- Reservation expiration date
- Recent utilization
- Matching active usage
- Planned workload migration or modernization date
- Expected spend after RI coverage ends
Do not assume every legacy VM family belongs to this July 1 change. HBv2 and NP-series, for example, had separate RI changes on April 2, 2026.
How much can Azure RIs save?
Microsoft advertises up to 72% savings versus pay-as-you-go for Azure Reserved VM Instances.
That is a maximum provider-published figure for a specific configuration and term, not an expected saving for every workload. Actual savings vary by VM type, region, operating system, term, and usage. See Azure Reserved VM Instance pricing.
That is a maximum provider-published figure for a specific configuration and term, not an expected saving for every workload. Actual savings vary by VM type, region, operating system, term, and usage. See Azure Reserved VM Instance pricing.
Azure Savings Plan vs. Reserved VM Instances
The July 1 announcement makes commitment planning more important for teams operating affected VM families.
A Reserved VM Instance is tied more closely to a particular VM configuration and region. An Azure Savings Plan for Compute uses an hourly spend commitment and provides broader flexibility across eligible compute usage.
A Reserved VM Instance is tied more closely to a particular VM configuration and region. An Azure Savings Plan for Compute uses an hourly spend commitment and provides broader flexibility across eligible compute usage.
| Consideration | Reserved VM Instance | Savings Plan for Compute |
|---|---|---|
| Commitment basis | Resource/configuration | Eligible hourly spend |
| Best fit | Stable workloads | Workloads expected to change |
| Flexibility | More constrained | Broader |
| Key risk | Configuration changes can reduce fit | Commitment can exceed eligible usage |
| FinOps focus | Utilization and configuration | Eligible spend and commitment coverage |
The right choice depends on expected future usage rather than the headline discount alone. See Microsoft’s Savings Plan and reservation comparison.
Azure Functions: Durable Task Scheduler Consumption reaches GA
Azure Durable Task Scheduler’s Consumption SKU reached general availability in May. It provides a usage-based option for durable orchestration workloads, including workflows used for AI agent scenarios.
The important FinOps point is that scheduler costs should not be confused with the compute cost of the application executing the workflow.
Microsoft documents scheduler billing separately from application compute. See Microsoft Durable Task Scheduler billing documentation.
For forecasting, track orchestration activity and application compute separately. Teams with bursty workflows should compare actual scheduler activity against their current cost model rather than assuming that changing SKUs automatically lowers total application spend.
Related read: AWS in May 2026 Updates
The important FinOps point is that scheduler costs should not be confused with the compute cost of the application executing the workflow.
Microsoft documents scheduler billing separately from application compute. See Microsoft Durable Task Scheduler billing documentation.
For forecasting, track orchestration activity and application compute separately. Teams with bursty workflows should compare actual scheduler activity against their current cost model rather than assuming that changing SKUs automatically lowers total application spend.
Related read: AWS in May 2026 Updates
Microsoft Foundry expands its model choices
Microsoft Foundry’s model catalog now includes DeepSeek-V4-Pro and DeepSeek-V4-Flash. Availability varies by deployment and region, so teams should verify the current catalog before designing a production workload around a particular model. See Microsoft Foundry model catalog.
From a FinOps perspective, model selection should be based on cost per useful outcome, not token price alone. Benchmark input and output tokens, latency, retries, quality, and regional pricing against representative workloads before changing a production model.
Microsoft’s current DeepSeek pricing page provides model-specific pricing and notes that actual prices can vary by agreement, date, and currency.
From a FinOps perspective, model selection should be based on cost per useful outcome, not token price alone. Benchmark input and output tokens, latency, retries, quality, and regional pricing against representative workloads before changing a production model.
Microsoft’s current DeepSeek pricing page provides model-specific pricing and notes that actual prices can vary by agreement, date, and currency.
Storage and identity updates
Azure Files Entra-only identities reach GA
Microsoft announced general availability of Entra-only identities for Azure Files SMB in May. The capability allows organizations to authenticate Azure Files SMB access using Microsoft Entra ID without requiring Active Directory, hybrid synchronization, or managed domain controllers for that identity model. Read the Microsoft Azure Files Entra-only identities announcement.
This is primarily an architecture and identity update, not an automatic storage-cost reduction. However, organizations planning to retire unnecessary identity infrastructure can include the operational cost implications in their modernization business case.
This is primarily an architecture and identity update, not an automatic storage-cost reduction. However, organizations planning to retire unnecessary identity infrastructure can include the operational cost implications in their modernization business case.
Azure Storage Mover adds Blob-to-Blob migration
Azure Storage Mover now supports Azure-to-Azure migration between Blob containers, including transfers between storage accounts and regions. Microsoft documents a limit of 500 million objects per migration job and up to 10 concurrent jobs per subscription.
For FinOps teams, model storage transaction, transfer, and destination-storage costs before moving large datasets. Scheduling a migration may improve operational control, but it does not by itself remove applicable transfer charges.
For FinOps teams, model storage transaction, transfer, and destination-storage costs before moving large datasets. Scheduling a migration may improve operational control, but it does not by itself remove applicable transfer charges.
Networking and operational updates
May also brought networking and platform improvements, including changes affecting NSG and UDR scale and additional Network Watcher capabilities.
The important FinOps distinction is that better operational tooling does not automatically create savings. For features such as Rule Impact Analyzer, teams should first confirm eligibility and preview status before building the capability into a production operating process.
Use these updates primarily to improve operational control, reduce configuration risk, and support better infrastructure decisions rather than assigning them an assumed percentage cost saving.
Related read: GCP in May 2026 Updates
The important FinOps distinction is that better operational tooling does not automatically create savings. For features such as Rule Impact Analyzer, teams should first confirm eligibility and preview status before building the capability into a production operating process.
Use these updates primarily to improve operational control, reduce configuration risk, and support better infrastructure decisions rather than assigning them an assumed percentage cost saving.
Related read: GCP in May 2026 Updates
Security and compliance notices
May also included security and compliance changes that should remain on infrastructure teams’ review lists.
Secure Boot certificate updates require affected organizations to verify whether certificate deployment is handled automatically or through managed update processes. This is primarily a security and platform-maintenance issue rather than a FinOps optimization.
Likewise, France’s upcoming e-invoicing requirements matter to organizations affected by the local regulatory requirements. These changes should be handled by the appropriate finance, tax, and compliance owners rather than treated as cloud-cost optimization measures.
Secure Boot certificate updates require affected organizations to verify whether certificate deployment is handled automatically or through managed update processes. This is primarily a security and platform-maintenance issue rather than a FinOps optimization.
Likewise, France’s upcoming e-invoicing requirements matter to organizations affected by the local regulatory requirements. These changes should be handled by the appropriate finance, tax, and compliance owners rather than treated as cloud-cost optimization measures.
May 2026 Azure FinOps Checklist
Before closing the May review cycle, FinOps teams should:
Inventory Azure RIs using the VM families affected by Microsoft's July 1, 2026 change.
Record each reservation's expiration date and utilization.
Compare supported RI options, Azure Savings Plan for Compute, and modernization plans.
Complete any desired affected-RI renewal or replacement transaction before July 1, 2026, where applicable.
Forecast Durable Task Scheduler Consumption costs from actual action volume.
Separate scheduler costs from Azure Functions or other application compute.
Benchmark DeepSeek models using Azure's current model pricing and representative workloads.
Review networking rule changes through Rule Impact Analyzer where applicable.
Check Azure Files identity architecture for opportunities to reduce unnecessary AD dependencies.
Review ANF Cache Volume use cases for WAN or bandwidth optimization rather than assuming capacity savings.
Validate Secure Boot certificate status for affected environments.
Treat Event Grid Subscription Identifiers as an application messaging feature, not a native cost-allocation mechanism.
How Usage.ai fits
Cloud optimization starts with understanding the workload before choosing a commitment.
We help teams evaluate Azure usage, identify eligible commitment opportunities, and manage approved commitments. Our Flex Commitment Program can deliver up to 57% savings on cloud spend, while cashback protection helps reduce the financial exposure associated with eligible commitments that become underutilized.
Microsoft’s native Azure commitment discounts vary by service, configuration, region, term, and usage. For Azure Reserved VM Instances, Microsoft advertises savings of up to 72% versus pay-as-you-go for eligible configurations.
We help teams evaluate Azure usage, identify eligible commitment opportunities, and manage approved commitments. Our Flex Commitment Program can deliver up to 57% savings on cloud spend, while cashback protection helps reduce the financial exposure associated with eligible commitments that become underutilized.
Microsoft’s native Azure commitment discounts vary by service, configuration, region, term, and usage. For Azure Reserved VM Instances, Microsoft advertises savings of up to 72% versus pay-as-you-go for eligible configurations.
Frequently asked questions
What Azure RI change was announced in May 2026?
Microsoft announced that purchases and renewals for specified legacy VM RI series would no longer be available starting July 1, 2026. Existing reservations continue through their terms.
Which Azure VM RIs are affected?
The July 1 change covers one-year RIs for Av2, Amv2, Bv1, D, Ds, Dv2, Dsv2, F, Fs, Fsv2, G, Gs, Ls, and Lsv2, plus one- and three-year RIs for Dv3, Dsv3, Ev3, and Esv3.
Is the 72% Azure RI saving available to every workload?
No. Microsoft presents up to 72% as a specific maximum pricing example. Actual savings depend on factors including VM type, region, operating system, term, and usage.
Does Durable Task Scheduler Consumption eliminate Azure Functions compute costs?
No. Scheduler billing and application compute are separate cost components. Teams should model both when forecasting durable workflow costs.
Is Azure Files Entra-only identity a cost optimization?
It is primarily an identity and architecture capability. It can reduce operational dependencies where organizations can eliminate unnecessary Active Directory or hybrid identity infrastructure, but it should not be treated as an automatic Azure storage-cost reduction.
Share
Facebook
X
LinkedIn
Reddit
