.png)
Executive Summary
April 2026 was a significant month for Azure across AI partnerships, storage pricing, and platform retirements. Three things need attention now:
- Microsoft amended its OpenAI partnership on April 27, 2026, confirming OpenAI products ship first on Azure. GPT-5.5 and GPT-image-2 are now available on Azure OpenAI Service, alongside Claude Opus 4.7. Each carries different pricing and governance requirements.
- Azure Blob Storage introduced a minimum billable object size for cooler storage tiers. Any team storing small objects in Cool, Cold, or Archive tiers is now paying more per object than before, regardless of actual data size.
- AKS Ubuntu 22.04 node pool retirement and Azure Functions v3 Linux consumption deprecation both moved to active status this month. Both require migration planning with firm deadlines.
For FinOps teams, two additional changes matter: License Mobility for Windows Server and SQL Server under the Microsoft Customer Agreement took effect April 1, and Premium SSD v2 reached general availability for Azure database services, changing the cost model for high-IOPS database workloads.
All pricing figures in this document require verification at azure.microsoft.com/pricing before acting on them.
Microsoft-OpenAI Amended Partnership: What Azure Customers Need to Know
On April 27, 2026, Microsoft and OpenAI announced an amended partnership agreement. The key terms for Azure customers:
- Microsoft remains OpenAI’s primary cloud partner.
- OpenAI products will ship first on Azure, unless Microsoft cannot or chooses not to support the necessary capabilities.
- The amended agreement is designed for “greater predictability” and “flexibility for both companies to pursue new opportunities.”
Practically, this means Azure remains the best-supported platform for OpenAI model deployment. Teams evaluating whether to run OpenAI models on Azure versus other clouds should factor the priority access arrangement into their infrastructure planning.
New Models Now Available on Azure OpenAI Service: GPT-5.5, GPT-image-2, and Claude Opus 4.7
Three significant model additions reached Azure this month:
| Model | Type | Key Use Case | Cost Consideration | Status |
|---|---|---|---|---|
| GPT-5.5 | Large language model | Complex reasoning, long-context tasks | Higher per-token cost than GPT-4o; verify pricing before switching | Available on Azure OpenAI Service |
| GPT-image-2 | Multimodal / image generation | Image creation and editing from text prompts | Per-image pricing; model richer outputs require governance review | Available on Azure OpenAI Service |
| Claude Opus 4.7 | Large language model | Agentic coding, long-horizon task execution | 64.3% on SWE-bench Pro; 87.6% on SWE-bench Verified; higher cost tier | Available on Azure OpenAI Service |
Model choice on Azure OpenAI Service now demands both technical evaluation and cost governance. Teams routing all AI traffic to GPT-5.5 without benchmarking against GPT-4o or Claude Haiku for simpler tasks may see 2x to 3x inference cost increases with no corresponding quality improvement for those workloads.
Storage: Minimum Billable Object Size, Blob Tier Changes, and Premium SSD v2 GA
Minimum Billable Object Size for Cooler Storage Tiers – Action Required
Microsoft announced a minimum billable object size for cooler storage tiers in Blob Storage accounts and Azure Data Lake Storage (ADLS) Gen2. This update introduces a minimum billable size threshold for objects stored in the Cool, Cold, and Archive tiers.
The practical impact: if your application stores many small objects in cooler tiers, such as log files, metadata records, thumbnails, or configuration blobs, each object now bills at a minimum size regardless of its actual size. Teams optimizing for the low per-GB rate on Archive tier while storing millions of small files should re-model their total storage cost with this minimum size applied.
Recommended action: pull your object count by size distribution from Azure Storage Explorer or Azure Monitor metrics. If the average object size in your cooler-tier buckets is significantly below the minimum billable size, consider batching or archiving small objects into larger files before the change fully takes effect.
Azure Elastic SAN: Capacity Autoscaling Now Available
Azure Elastic SAN now supports automatic capacity scaling to match workload demand. Teams running Elastic SAN no longer need to manually provision ahead of demand spikes. The autoscaling feature improves uptime during unplanned growth, but it also introduces the risk of unpredictable cost increases if scale-out limits are not configured.
Set maximum capacity limits before enabling autoscaling. Without limits, storage spend can scale unconstrained during peak events.
Premium SSD v2 Now Generally Available for Azure Database Services
Premium SSD v2 reached general availability for Azure Database this month, including Azure Database for PostgreSQL Flexible Server. Key improvements:
- Higher IOPS and throughput for high-transaction database workloads compared to Premium SSD v1.
- New flexible provisioning model decouples capacity, IOPS, and throughput with GiB granularity and lower IOPS minimums.
- In sample scenarios, the decoupled model delivers up to 50% cost reductions for small disks and up to 25% for large disks.
- Cross-tenant customer-managed key (CMK) support is now generally available for Premium SSD v2 and Ultra Disks.
The decoupling of capacity, IOPS, and throughput is the significant change for FinOps teams. Previously, purchasing higher IOPS meant provisioning more capacity than required. With Premium SSD v2, right-sizing IOPS separately from capacity avoids paying for unused storage to reach the IOPS floor. Model your current Premium SSD v1 costs against the v2 pricing before migrating.
For a framework on Azure commitment strategy across VMs and databases, the Usage.ai guide on Azure Cost Optimization covers Reserved VM Instances, Azure Savings Plans, and Hybrid Benefit in detail.
Databases and Containers: PostgreSQL Improvements, AKS Retirements, and Arc SQL Migration
Azure Database for PostgreSQL Flexible Server: Logical Replication Monitoring and New Regions
Two database updates this month for PostgreSQL teams:
- Logical replication slot monitoring is now available in Azure Database for PostgreSQL Flexible Server. Teams can track replication health, detect lag, and maintain data consistency during migrations without external tooling.
- Broader regional availability, including Denmark East, reduces latency for workloads served from Northern Europe.
The logical replication monitoring is specifically valuable for teams mid-migration. Replication lag that goes undetected can cause silent data divergence between source and target. Monitoring replication slot health is now a first-party capability, removing the need for custom pg_replication_slots queries or external Datadog monitors for this specific signal.
AKS Ubuntu 22.04 Node Pool Retirement – Migration Planning Required
AKS will retire Ubuntu 22.04 worker node images. Teams running AKS node pools on Ubuntu 22.04 must migrate to Ubuntu 24.04 before the retirement date. Key actions:
- Audit all AKS node pools for Ubuntu 22.04 images using Azure CLI or Azure Portal.
- Test workloads on Ubuntu 24.04 in a non-production cluster before migrating production pools.
- Use CLI backup options to snapshot existing configurations before the upgrade.
Failing to migrate before the retirement date will cause node pool provisioning failures. AKS clusters do not automatically upgrade node OS images.
Azure Functions v3 Linux Consumption: Deprecation Active
Microsoft deprecated Linux consumption for Azure Functions v3 this month. Teams running Functions v3 on Linux in the consumption plan must migrate to Functions v4.
Cost implication: Functions v4 consumption pricing is structurally the same as v3 – per execution and per GB-second of memory. The migration does not change your cost model. The risk is a disruption timeline: if you miss the deprecation date, v3 functions on Linux consumption stop working.
Azure Arc Now Supports SQL Server on Azure VMs as Migration Target
Azure Arc now supports SQL Server on Azure Virtual Machines as a migration target, easing hybrid-to-cloud migration paths while keeping familiar management tools. Teams migrating SQL Server workloads from on-premises or other clouds to Azure can now use Arc as the management and migration layer without switching toolsets mid-migration.
This is relevant for teams evaluating SQL Server Extended Security Update pricing changes. SQL Server 2016 reaches end of Extended Support on July 14, 2026. Microsoft introduced a simplified pricing model for SQL Server 2016 Extended Security Updates in Azure, aligning pricing with on-premises rates. Teams running SQL Server 2014 in Azure Virtual Machines currently receive Extended Security Updates at no extra cost – this will change.
Security and Identity: Defender for SQL, External MFA GA, and Entra PAM Updates
Defender for SQL Servers on Machines: Enhanced Agent Architecture in Government Cloud
As of April 27, 2026, Microsoft rolled out an enhanced agent-based solution for Microsoft Defender for SQL Servers on Machines in government (Fairfax) cloud environments. The update replaces legacy Azure Monitor-based agents with a modern extension-based architecture, simplifying onboarding and improving SQL detection coverage. Migration of currently protected SQL instances is automatic. Teams should enable automatic registration with the SQL IaaS Agent extension to ensure new SQL instances are detected and registered.
External MFA Now Generally Available in Microsoft Entra ID
External Multifactor Authentication (External MFA) is now generally available in Microsoft Entra ID. This allows organizations to meet MFA requirements while continuing to use their preferred MFA provider. Microsoft Entra ID remains the identity control plane, performing full policy evaluation and Conditional Access enforcement on every sign-in. Organizations with existing MFA investments in Okta, Duo, or other providers can now integrate them formally without workarounds.
Privileged Access Manager: Soft Delete for Conditional Access Policies
Microsoft Entra now supports soft delete and restore for Conditional Access policies and Named Locations, currently in public preview. Teams that accidentally delete a Conditional Access policy can now restore it without rebuilding from scratch. This reduces the operational risk of Conditional Access management and removes the need for manual policy export-before-delete procedures.
Licensing: License Mobility for MCA, Windows Server, and SQL Server 2016 ESU
License Mobility Under Microsoft Customer Agreement: Effective April 1, 2026
License Mobility for Windows Server and SQL Server purchased under the Microsoft Customer Agreement (MCA) took effect April 1, 2026. Teams on MCA agreements can now apply their existing Windows Server and SQL Server licenses to Azure deployments, easing the path to Azure Hybrid Benefit without requiring a separate Software Assurance agreement.
Combined with Azure Hybrid Benefit, Windows Server and SQL Server workloads can save up to 85% compared to pay-as-you-go pricing. If your team is on MCA and has not yet reviewed Azure Hybrid Benefit eligibility, April 2026 is the first month this full combination is available.
For a breakdown of how Azure Reserved VM Instances, Savings Plans, and Hybrid Benefit stack together, the Usage.ai guide on commitment-based discounts across Azure explains each mechanism and when each delivers the best return.
SQL Server 2016 Extended Security Updates: New Pricing Model
Microsoft introduced a simplified, consistent pricing model for SQL Server 2016 Extended Security Updates in Azure, aligning with on-premises and other public cloud pricing. SQL Server 2016 reaches end of Extended Support on July 14, 2026. Teams running SQL Server 2016 in Azure VMs need to either migrate to a supported version or budget for Extended Security Update charges.
Teams running SQL Server 2014 in Azure VMs currently receive Extended Security Updates at no extra cost – check whether this benefit continues beyond the SQL Server 2016 extended support end date.
FinOps and Cost Management: What April 2026 Means for Azure Spend
Azure OpenAI Model Costs: Governance Before Scale
GPT-5.5, GPT-image-2, and Claude Opus 4.7 on Azure OpenAI Service are the most direct new cost risks from April 2026. The pattern seen with every model generation upgrade holds: newer models cost more per token and deliver higher quality, but many production use cases do not require the highest-quality model for every call.
Recommended action: before migrating workloads to GPT-5.5 or Claude Opus 4.7, benchmark each use case against the cheapest model that meets quality requirements. A classification pipeline that worked on GPT-3.5-turbo does not need GPT-5.5. Set per-deployment spending limits in Azure OpenAI Service before enabling the new models in production.
Blob Storage Minimum Billable Object Size: Model Before the Change Lands
The minimum billable object size change for cooler storage tiers is the most underestimated cost change from April 2026. Many engineering teams store small files in Cool or Archive tier because the per-GB rate is low and never audit whether the actual objects are small enough to be affected by a minimum size floor.
Pull your Azure Storage metrics for object count versus total storage by tier. Divide total storage by object count to get the average object size per tier. If average object size in Cool, Cold, or Archive is below the minimum billable threshold, calculate the effective per-GB cost increase and update your storage budget.
Database Savings Plans and Premium SSD v2: Two Separate Optimization Opportunities
Premium SSD v2 general availability for Azure Database creates a right-sizing opportunity: if you are currently over-provisioned on Premium SSD v1 to reach a required IOPS floor, the decoupled v2 model may let you reduce storage while maintaining the same IOPS and throughput. Run a cost comparison between your current v1 configuration and an equivalent v2 configuration before renewing any storage reservations.
For teams running multiple Azure database services and evaluating whether Database Savings Plans or Reserved Instances deliver better coverage, the Usage.ai guide on Azure Database Savings Plans covers the commitment comparison, qualifying services, and when each approach makes sense.
Azure Hybrid Benefit Review: April Is the First Month the Full MCA Combination Is Active
License Mobility for MCA took effect April 1, making April 2026 the first full month where teams on MCA agreements can combine License Mobility, Azure Hybrid Benefit, and Reserved VM Instances. The maximum savings combination – 3-year Reserved VM Instance plus Azure Hybrid Benefit for Windows Server plus SQL Server license portability – can reduce effective VM cost by up to 85% versus pay-as-you-go.
If your team has not reviewed Azure Hybrid Benefit eligibility since the MCA License Mobility change, do so before the next RI renewal cycle. Teams that purchased Reserved Instances without Hybrid Benefit are overpaying for the licensing component.
