How this was actually announced
Microsoft disclosed this price increase not through a blog post, a pricing page update, or an Azure Updates announcement, the channels customers normally monitor for this kind of change, but through an Azure Service Health advisory tracked under ID JGW1-KG0, sent directly to affected customers starting around October 2, 2026. The first public traces of the notice surfaced on Microsoft Q&A forums on October 5, where customers and partners began piecing together the scope from the advisory text itself rather than from any official pricing communication.
As of the most recent reporting on November 11, more than five weeks after the initial notice went out, Microsoft had still not published a pricing page or Azure Updates entry confirming the specific new rates. That gap matters operationally: your finance team cannot model next year's Azure spend against an authoritative published number right now, only against a support advisory whose scope is still being interpreted by the community that received it.
What is actually increasing, and by how much
The increase applies to pay-as-you-go, Enterprise Agreement, and Microsoft Customer Agreement rates starting February 1, 2027, and it is not uniform across regions. North Europe, specifically the Dublin region, sees the steepest increase at 17 percent. France Central and France South follow at 11 percent. West Europe in Amsterdam, along with Norway East and Norway West, rise 9 percent. Southeast Asia, centered on Singapore, sees the smallest confirmed increase at 8 percent. Partners have separately reported a roughly 25 percent increase specifically for older v1 and v2 series VMs, though Microsoft has not confirmed that figure.
The advisory Microsoft sent, as quoted by customers on Microsoft Q&A, lists which VM series are excluded from the increase rather than confirming which ones are included, an unusual framing that pushes interpretation work onto the customer. Excluded series span older generations across v1 and v2, plus a handful of v7 series. Everything else, including v3 through v6 D and E series, B-series v2, and GPU families, falls outside the exclusion list and should be budgeted for accordingly. Managed Disks and Azure Files are also absent from the exclusion list.
Why the exclusion-list framing is the real problem
A pricing notice that tells you what is excluded, rather than what is included, inverts the normal burden of interpretation in Microsoft's favor and against yours as the customer footing the bill. It means every workload you run needs to be individually checked against a negative list rather than confirmed against a positive one, and any VM series or storage service Microsoft adds to its product catalog between now and February, without an explicit new exclusion, defaults to being in scope for the increase by omission alone.
This framing also makes the increase harder to communicate internally. Telling a budget owner their GPU-backed workload is affected because it is not on an exclusion list is a weaker, more hedged statement than confirming it against a published rate increase, and that ambiguity will cost you credibility in a CFO conversation if the actual February invoice does not match what you projected from the advisory alone.
What to do with the time you have left
You have roughly ten weeks before February 1, 2027, and the most concrete lever available in that window is your reserved instance and savings plan strategy. Commitments signed before the increase takes effect may lock in current rates for their full term length, which for a one or three year reservation could mean avoiding this specific increase entirely for the life of the commitment, a meaningfully different outcome than waiting and absorbing the new rate from day one.
Run your own workload inventory against the exclusion list now, region by region, rather than waiting for Microsoft's eventual official pricing page, since the advisory text is the only authoritative source currently available and it is not going to get easier to parse later. For any workload in North Europe specifically, where the 17 percent increase is steepest, this is worth an explicit line item in your Q1 2027 budget conversation rather than an assumption folded into general cloud cost inflation.
The broader signal for your vendor relationship
A major price increase disclosed through a support advisory rather than a public pricing announcement is itself a data point about how Microsoft is currently managing customer communication around Azure economics, at a moment when AI infrastructure demand is straining capacity across every hyperscaler. Whether this reflects rushed internal process or a deliberate choice to limit public scrutiny of the increase, the practical effect on you is the same: you are doing the interpretation work Microsoft would normally do in a published pricing change.
Treat this as a prompt to ask your account team directly for written confirmation of which of your specific workloads and regions are affected, rather than relying on community interpretation of the advisory text. A vendor that communicates a double-digit price increase this way is worth pushing for clarity from proactively, and getting that confirmation in writing now gives you a stronger position if the eventual invoice diverges from what the advisory implied.



