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.
