Podcast Episode: Microsoft Cloud Pricing Shifts


Pip: Welcome to Cloudy with a Chance of Licensing โ€” where the forecast is partly cloudy with a strong chance of your Azure bill going up.

Mara: rich_gibbons has been tracking some significant changes across Azure pricing, reservation policy, and Copilot Studio this episode, alongside Microsoft's latest financial results. There's a lot that touches FinOps and ITAM teams directly.

Pip: Let's start with what February 2027 is quietly turning into: a deadline with teeth.

Azure Prices and Reservation Policy: February 2027

Mara: Two separate but converging changes land on the same date โ€” February 1st, 2027 โ€” and together they reshape how organizations should be thinking about their Azure commitments right now.

Pip: The price increases hit seven regions, and the spread is meaningful. Dublin leads at 17%, Singapore sits at the low end with 8%, and France, Amsterdam, and Norway fall in between.

Mara: The post is direct about the action item: "If you're heavily in these datacentres, particularly Dublin, modelling your bills next year โ€” and potential mitigations โ€” should be on the list for FinOps and ITAM teams."

Pip: Seventeen percent is not a rounding error. That's a real budget conversation waiting to happen, and the exclusion lists don't make it simpler โ€” there are long lists of VM series and storage services carved out, so teams need to check their specific footprint carefully.

Mara: And the reservation exchange policy post explains exactly why that footprint review matters even more now. From February 1st, 2027, Azure Reservations for Virtual Machines, App Service, SQL Database, and similar services will no longer be exchangeable if a Savings Plan exists for that service.

Pip: This change has been announced, postponed, and re-announced since October 2022 โ€” it's had more false starts than a budget approval cycle.

Mara: That history is worth noting. It was pushed from January 2024 to July 2024, then deferred indefinitely, with Microsoft promising six months' notice before re-implementing. That notice has now been given, and the post suggests another postponement seems unlikely.

Pip: So the flexibility organizations relied on โ€” swapping reservations when workloads shifted โ€” is going away for most compute services.

Mara: The post frames the strategic choice clearly: Savings Plans offer lower maximum discounts but much less administrative overhead and no need to manage exchanges. Reserved Instances still deliver higher discounts for stable, predictable workloads, but the safety valve of exchangeability is closing. Strategies need to be reviewed before that door shuts.

Pip: Two changes, one date โ€” the financial modeling homework is overdue.

Microsoft's Q1 FY27 Numbers

Mara: Microsoft's first quarter FY27 results are out, and the headline figures are substantial โ€” revenue of $92.3 billion, up 19%, with net income up 32% and Microsoft Cloud revenue reaching $63.9 billion.

Pip: Azure grew 48% year over year, which does make the price increases feel a little less like necessity and a little more like confidence.

Mara: Satya Nadella described Copilot's direction plainly: "We think of Copilot as the new OS for work." The results show consumption billing โ€” particularly through GitHub Copilot and M365 Copilot โ€” as a primary growth driver, with usage-based billing customers up over 75% in the quarter.

Pip: Speaking of usage-based billing โ€” that's exactly where the next story lives.

Copilot Studio's New Harness and Its Billing Catch

Mara: Copilot Studio now has a third option for building agents โ€” the GitHub Copilot harness โ€” which brings the same coding and reasoning capabilities as GitHub Copilot and Copilot Cowork to your in-house agents.

Pip: The capability sounds useful. The billing model is the part that deserves a careful read before anyone starts building.

Mara: The post quotes Microsoft directly: "Agents running on the GitHub Copilot harness use usage-based billing for all work, regardless of Microsoft 365 Copilot licensing." Unlike the existing harnesses, where Copilot Credits are covered by an M365 Copilot license, this one draws on pre-purchased credits or incurs pay-as-you-go costs.

Pip: No one is being forced onto this model โ€” it's an optional, additional capability. But "optional" and "inadvertent spend" have a way of meeting each other quietly.

Mara: The Copilot Studio Licensing Guide for August 2026 is worth reviewing alongside this, and the post is clear that strong internal governance and awareness programs are the practical response here.


Mara: February 2027 keeps appearing as the date when several assumptions about Azure cost management stop holding โ€” pricing, reservations, and consumption billing are all moving at once.

Pip: Next time, hopefully the forecast includes at least one change that makes the bill smaller. We'll be watching.

Microsoft Financial Results: FY27 Q1


Microsoft’s results for FY27 Q1 are out and, once again, the numbers are bigger than last time. It’s always difficult to reconcile such huge results with layoff announcements and that has happened again with news that Microsoft have made a voluntary exit offer to approx. 60,000 staff – almost a quarter of the workforce.

Talking about the recent Copilot “super app” that combines Chat, Cowork, Autopilot, and Code, Satya Nadella said “We think of Copilot as the new OS for work” – make of that what you will!

It’s clear that AI, Copilot, and consumption billing are the big drivers of Microsoft’s revenue and future direction.

  • Revenue = $92.3 billion, up 19%
  • Net Income = $36.6 billion, up 32%
  • Microsoft Cloud revenue = $63.9 billion, up 30%

For several years, revenue has been split into different categories:

  • Productivity and Business Processes
  • Intelligent Cloud
  • More Personal Computing

but it now seems to be:

  • Agents and Infra
  • Devices and Consumer

so the Agents & Infra segment includes Azure and M365. I assume it will include Dynamics 365 too but, for the first time in a long time, that isn’t mentioned specifically…does that mean D365 hasn’t grown in Q1 FY27?

Nadella did say that they’re “bringing the business logic and capabilities of Dynamics 365 directly into Copilot and helping every organization stand up their own infinite SaaS Factory” – perhaps there’s a shift in focus happening?

Amy Hood, CFO, stated that:

“Capital expenditures were $45.2 billion,. Roughly three quarters of…capex was for short-lived assets, primarily CPUs and GPUs, including higher memory and storage costs.”

That’s over $33 billion on CPUs and GPUs in a single quarter!

Agents & Infra numbers

  • Revenue increased 25% to $76.8 billion
  • Azure revenue grew 48%
  • M365 Commercial increased 17%

M365 Copilot, E5, and E7 helped drive higher average revenue per user as well as more consumption billing, particularly of GitHub Copilot.

Earnings Call highlights

  • The number of Copilot customers actively consuming credits through usage-based billing grew over 75 percent over the quarter.
  • Credit consumption from agentic features on GitHub has more than doubled since usage-based billing went into effect.
  • Over 44,000 paid Fabric customers, up more than 50 percent year over year.
  • Microsoft added 24 new data centers across five continents this quarter.

See the Microsoft page here – FY27 Q1 – Press Releases – Investor Relations – Microsoft

Microsoft increase Azure prices from February 2027


From 1 February 2027, Microsoft will raise prices for specific Azure Virtual Machine series and Azure Storage services in seven regions, by between 8% and 17%.

Regions and increases

Dublin takes the largest rise at 17%, and Singapore the smallest at 8%:

EU North (Dublin)

17%

France Central

11%

France South

11%

EU West (Amsterdam)

9%

Norway East

9%

Norway West

9%

Southeast Asia (Singapore)

8%

Microsoft has published an exclusion list as follows:

Excluded Virtual Machine series:

  • v1: Bv1, D, Ds, F, Fs, G, Gs, L, NP, HCS
  • v2: Av2, Amv2, Dv2, Dsv2, Fsv2, Lsv2
  • v7: Dsv7, Ddsv7, Dlsv7, Dldsv7, Esv7, Edsv7

Excluded Azure Storage services: Container Storage, Managed Lustre, NetApp Files Cross Region Replication SKU, Blob Features, Change Feed, General Block Blob, Import/Export, Queues, Queues v2, Standard Page Blob, Storage Actions, Storage Bandwidth, Storage Discovery, Tables and the Transaction Optimized SKU.

If you’re heavily in these datacentres, particularly Dublin, modelling your bills next year – and potential mitigations – should be on the list for FinOps and ITAM teams.

Remember, this is the same date (Feb 1, 2027) that the reservation changes kick in too.

Azure Future Capacity Reservations


A robed figure faces a glowing cloud gateway labeled CLOUD FUTURE CAPACITY
A robed traveler confronts a luminous cloud gateway surrounded by digital data streams and futuristic servers.

Azure Future Capacity Reservations have been added to the Product Terms – these “allow Customers to request capacity for specified Microsoft Azure resources in a specified region, with a scheduled start date and reservation term“.

This seems a way of alleviating concerns over lack of capacity in certain regions and giving Microsoft more information with which to make resource and capacity increase decisions.

How do they work?

  • You request: A specific amount of Azure capacity, in a region, starting on a future date, for a set term.
  • Microsoft decides: They can accept, reject, or modify the request, normally within 7 days.
  • Availability: Microsoft tries to provide the capacity on the agreed start date. If they can’t provide all of it, they have 30 days to fulfil the remainder.
  • You can’t change it: Once accepted, you can’t modify it during the 12 weeks before the start date or the 30-day fulfilment period.
  • You pay for what they provide: Whether you actually use the capacity or not. Equally – you don’t pay for what they don’t provide.
  • If Microsoft can’t provide it: You can cancel the unfulfilled portion after the 30-day fulfilment period.
  • No compensation: Generally, Microsoft doesn’t owe you service credits for failing to provide the capacity.
  • No discount: This is capacity assurance, not a price discount, and doesn’t give you dedicated hardware.
  • You still have to do the admin: Subscription, quota, deployment and configuration requirements remain your responsibility.
  • End of term: The reservation expires and subsequent usage is charged at the then-current consumption rates.

These sit in the portfolio alongside the still somewhat mysterious Azure Capacity Blocks – Microsoft Azure Capacity Blocks โ€“ Cloudy with a chance of Licensing

Microsoft remove Azure Reservation exchange policy


Customer and store employee discussing a receipt at customer service counter
A customer discusses a return with a store employee near a return policy sign.

From February 1st, 2027 – Azure Reservations will no longer be eligible* to be exchanged if the service also has a Savings Plan available. This applies to:

  • Azure Virtual Machines
  • Azure App Service
  • Azure SQL Database
  • and “similar services”.

*Reservations purchased before February 1, 2027, keep the right to one final exchange.

Equally, from that date any additional compute or database services that also become available for a Savings Plan will be subject to this change. Instance Size Flexibility isn’t impacted by this change.

The following are excluded from the change:

  • Reservations for products or services that are deprecated and approaching end of life.
  • Reservations for products and services that aren’t covered by savings plans, such as Azure VMware Solution. If you have a reservation for Azure VMware Solution, this policy change doesn’t affect it.
  • Cloud environments that don’t currently support savings plans.

Microsoft initially announced this change in October 2022 with a date of Jan 1, 2024. That was then pushed back to July 1, 2024 and then postponed indefinitely – with a promise of 6 months notice before it would be implemented again…and that’s what Microsoft have given. Could we see another postponement? Perhaps, but it seems unlikley tbh.

It’s clear that Microsoft want Savings Plans to be the primary option for organisations so here’s a quick overview if you’re not familiar:

FeatureAzure Reserved InstancesAzure Savings Plans
CommitmentCommit to a specific Azure resource (e.g. VM family, SQL Database, App Service)Commit to an hourly spend amount on eligible compute & database services
Term1 or 3 years1 or 3 years
DiscountTypically offers the highest discount when usage is stableLower maximum discount, but greater flexibility
FlexibilityLow โ€“ tied to the purchased resourceHigh โ€“ discounts automatically apply across eligible compute resources
Changing VM SizeAllowed within instance size flexibility rules for some servicesNo action required
Changing VM FamilyPreviously possible through Reservation exchanges (being phased out)No action required
Changing RegionMay require a Reservation exchange (being phased out)No action required
Workload ChangesBest suited to stable, predictable workloadsDesigned for dynamic, changing cloud environments
AdministrationRequires ongoing monitoring and optimisation to ensure Reservations still match usageMuch lower administrative overhead once purchased
Best ForLong-running production workloads with predictable resource requirementsOrganisations with frequently changing compute usage, autoscaling or modern cloud architectures
RiskHigher risk of underutilisation if workloads changeLower risk, as discounts follow eligible usage automatically

FinOps impact

The ability to exchange Reserved Instances has been part of mature Azure commitment strategies for quite some time but this is bringing much of that to an end. Strategies will need to be reviewed and a decision made on whether Savings Plans are now a better option, even with the potential loss of discount.

Make sure you communicate this change internally and work to update your governance and strategy asap.

You can see the Microsoft Learn page, with examples, here – Changes to the Azure reservation exchange policy – Microsoft Cost Management | Microsoft Learn

Microsoft Azure Capacity Blocks


Pixel art style cloud above data center buildings with digital data streams connecting them
Digital cloud linking to a modern data center in a pixel art style.

A new addition, Azure Capacity Blocks (ACB):

“allow Customers to purchase a fixed duration block of capacity for a specific Microsoft Azure resource in a specified region, with a scheduled start date in the future.”

They can range from 1 day to 6 months, they are fully paid for upfront, and cannot be cancelled or refunded. Unused portions of ACBs will not be refunded either. Once the term ends, customers “will be evicted from the applicable capacity, and Microsoft will stop Customerโ€™s use of the applicable Microsoft Azure Services.”

When I initially looked, there was a Learn site for this new release but I cannot find it now. Not sure if it’s been removed or I (and ChatGPT) just aren’t looking in the right place all of a sudden ๐Ÿค”

This new offering must be related to the capacity issues that Microsoft have been having in their Azure datacentres – will it help prevent that from reoccuring?

Microsoft Financial Results FY26 Q2


Microsoft Financial Results for Q2 FY26

Revenue = $81.3 billion (up 17%)

Net Income =ย $38.5 billion (up 60%)

Microsoft Cloud = $51.5 billion

As it has been every quarter for many years now, more big increases across the board as Microsoft continues to grow. They have RPO (Remaining Performance Obligation) of $625 billion, an increase of 110%, which indicates a lot of multi-year agreements have been signed. This huge backlog of guaranteed revenue likely means that Microsoft aren’t as bothered about your order/renewal as you might like them to be…making discounts harder to come by for many customers.

Is AI still a hot topic?

Yes!

Satya Nadella, Microsoft CEO said:

โ€œWe are only at the beginning phases of AI diffusion and already Microsoft has built an AI business that is larger than some of our biggest franchises”

โ€œWe are pushing the frontier across our entire AI stack to drive new value for our customers and partners.โ€

And devoted the majority of his time on the earnings call to discussing AI, both software and hardware.

Additionally, Q2 saw commercial booking increase 230%, โ€œdriven by Azure commitments from OpenAI and Anthropicโ€. Further more, Perplexity have also signed a $750 million deal with Azure – https://www.msn.com/en-us/money/other/perplexity-inks-microsoft-ai-cloud-deal-amid-dispute-with-amazon/

Productivity & Business Processes

Revenue = $51.5 billion, an increase of 26%

Dynamics 365 revenue increased 19%

Microsoft 365 Commercial cloud revenue increased 17% with ARPU (Average Revenue Per User) driven by E5 and M365 Copilot.

Microsoft 365 Copilot seats added increased 160% year on year in FY26 Q2 (Oct โ€“ Dec 2025) taking them to 15 million paid seats. Of course, how many of those are being used โ€“ and being used well โ€“ is a different question entirely. 

Tracking and understanding ROI of AI investments isnโ€™t as high a priority for most organisations as it should be. This really is an areas where ITAM & FinOps professionals can help organisations take a deeper, more data driven approach to AI procurement and value. I wrote this over 2.5 years ago – https://cloudywithachanceoflicensing.com/2023/07/21/microsoft-365-copilot-pricing-and-licensing-strategy/ – and I don’t think much has changed tbh.

Intelligent Cloud

Revenue = $32.9 billion, an increase of 29%

Azure increased by 39% (down from 40% in the previous quarter) but gross margin on cloud declined slightly. Market analysts were hoping for higher Azure growth so this perceived miss was partially responsible for a drop in Microsoft’s stock after the announcement.

They are also concerned that the huge amount of money Microsoft are spending on CAPEX related to AI datacentres etc. isn’t generating ROI fast enough.

Conclusion

Microsoftโ€™s results underscore that licence management, cloud cost control, and financial governance are now inseparable, particularly as AI accelerates both consumption and complexity. 

For ITAM and FinOps leaders, Q2 FY26 is less about Microsoftโ€™s growth and more about the operational response it demands: proactive review of AI and cloud commitments, tighter contract scrutiny, and implementation of usage intelligence. 

Organisations that align ITAM and FinOps processes to anticipate consumption variability and optimise spend can mitigate financial risk while maximising value from licences, cloud services, and emerging AI capabilities. Success will increasingly depend on granular monitoring, AI-informed analytics, and governance tools that bridge licensing, cloud, and financial metrics.

See more here – FY26 Q2 – Press Releases – Investor Relations – Microsoft

Microsoft Azure Storage Discovery


Microsoft have a new (currently in preview) service to give more visibility into your Azure Blob storage.

Azure Storage Discovery will:

  • Measure how much data is stored across all storage accounts
  • Identify regions experiencing the highest growth
  • Find opportunities to reduce costs by locating infrequently used data
  • Assess whether storage configurations align with security and compliance best practices
https://learn.microsoft.com/en-us/azure/storage-discovery/overview

Storage is often a source of hidden spend (and waste) in the cloud, so this may well be a useful weapon in your arsenal.

How is it priced?

There is a Free tier and also a paid-for Standard tier.

https://learn.microsoft.com/en-us/azure/storage-discovery/pricing

1 The backfill feature automatically adds historic data into a Storage Discovery workspace from before the workspace is created.
2 Every workspace retains insights for some time to allow for historical analysis.

The total cost will be comprised of:

  • Pricing plan
  • Workspace configuration
  • Number of storage resources & data objects analysed

Note that a storage resource can be included in multiple workspaces and will be charged in each one.

How much will all this cost? As the service is in Preview, and you’re able to use it for free, Microsoft haven’t released pricing details. These will become available on Azure.com before October 1, 2025, when billing kicks in.

To find out more about what it does and how it works, head here.

Microsoft Purview gets more PAYG SKUs for AI


Microsoft Purview is a suite of products focused on data security, governance, and compliance across the Microsoft portfolio.

Microsoft first introduced Pay As You Go (PAYG) aka Consumption SKUs for Purview in January 2025 and now, from May 1, 2025 there are a new set. These new SKUs are aimed at protecting “your data as it moves across networks and through GenAI applications“.

The * is to note that Audit Standard is included within “Microsoft first party applications such as Microsoft 365 applications, Fabric, and Microsoft first party AI apps like Microsoft 365 Copilot, Security Copilot or AI applications custom-built using Copilot Studio“.

New metric/acronym alert! The 10,000 events for Insider Risk Management are known as a “Data Security Processing Unit (DPSU)”.

I notice that, for “Data Security Investigations”, Microsoft say:

“Data Security Investigations is billed through two meters: 1) the Data Security Investigations non-AI processing and storage meter and 2) Security Compute Units.

The Data Security Investigations non-AI processing and storage meter allows customers to store data related to an investigation. Security Compute Units are used to measure the computational capacity needed to run the AI analysis within DSI.”

Security Compute Units (SCUs) were introduced with Microsoft Security Copilot. It seems now that certain Purview PAYG usage may also consume your SCUs – needing further planning and budget insights.

You can see more from Microsoft here.

Microsoft on-premises hotpatching comes to Windows Server 2025 – at a cost


Hotpatching – the ability to install patch updates without needing to restart the server – has been available in Microsoft Azure for a while. It is now coming to on-premises Windows Server 2025 machines…for a fee.

This new capability requires connection to Azure Arc and is currently free in preview but, from July 1 2025, it will cost $1.50 per core per month. That’s over $100,000 per year for 100 x 64 core servers…

*Update May 2026*

As of May 15th, 2026 – Hotpatch enabled by Azure Arc is available at no additional cost for Windows Server 2025. See more here:

Simplified access to Hotpatching enabled by Azure Arc for Windows Server 2025 | Microsoft Community Hub

If you’ve enrolled into the Preview, make sure you unenroll by June 30th to avoid being charged!

Interestingly, it doesn’t remove reboots completely but reduces the number from 12 per year to 4.

See more details from Microsoft here.