Microsoft has confirmed a change to how it manages local currency pricing across its commercial cloud services, moving from two adjustments a year to one, starting in January 2027. Microsoft will now revisit foreign currency prices once a year, on January 1st, rather than the twice-yearly cadence it had followed since at least 2024, with an option to make additional changes only in limited exceptional circumstances, and advance guidance to be issued each November ahead of the January adjustment.
What This Actually Covers
The change applies broadly across Microsoft’s commercial cloud portfolio, though not universally. These exchange rate fluctuations against the US dollar affect all Microsoft Online Services apart from Azure, and will now take place every January starting in 2027, with Microsoft providing advance notice of these changes each November.
That carve-out for Azure is worth noting specifically, since it means an organisation running a mixed Microsoft estate, Azure consumption alongside Microsoft 365, Dynamics 365, or other Online Services licensed in local currency, will see two different currency adjustment cadences applying across its own Microsoft relationship rather than one unified schedule.
Why Microsoft Is Framing This as Greater Predictability
Microsoft’s own justification for the change centres entirely on predictability, and it is worth examining that framing directly rather than accepting it at face value. Moving from two adjustment points a year to one does genuinely reduce the number of moments at which a customer’s local currency pricing can shift, which is a real form of predictability. It does not reduce how much any single adjustment might move pricing, and in fact may concentrate a full year’s currency movement into a single annual change rather than spreading it across two smaller ones.
That distinction matters because of how currency movements have actually played out recently. In early 2026, European Microsoft customers saw a seven point four percent price reduction as a direct result of a weakening US dollar, illustrating that these adjustments move in both directions and are not purely a mechanism for price increases. Reducing the adjustment frequency to once a year means an organisation now has only one opportunity a year for a currency movement to work in its favour, rather than two, which cuts both ways depending on which direction exchange rates happen to move in a given year.
Why Monthly Commitment Customers Feel This Differently
The practical effect of this change is not identical for every customer, and the distinction is worth understanding before assuming the shift is neutral across the board. For customers on a monthly commitment, pricing updates take effect on the first monthly renewal after January 1, 2027, and under the old semi-annual model, a customer on a monthly commitment could potentially be exposed to two currency-related adjustments in a single year, whereas under the new system there is generally only one scheduled adjustment.
That reduction from two potential adjustment points to one is a genuine, structural change for monthly commitment customers specifically, distinct from the broader predictability argument Microsoft is making. An organisation currently on monthly billing purely to retain flexibility around currency timing should factor this reduced adjustment frequency into whether that flexibility still delivers the value it once did.
What This Means Heading Into an EA Renewal
The timing of this shift is particularly relevant for organisations with an Enterprise Agreement renewal landing close to a January currency adjustment point, since price protection terms and renewal timing interact directly with when a currency adjustment actually applies. Existing products under agreements with price protection are generally not affected by a currency adjustment until renewal, though new products added to an agreement can be subject to whatever adjustment is in effect at the time they are ordered.
That distinction between existing, price-protected products and newly added ones is worth confirming explicitly for any organisation planning to expand its Microsoft estate around the same time as its EA renewal. Adding new products or services close to a January adjustment date means those specific additions could be priced under a different currency assumption than the rest of the agreement, even where the bulk of the existing agreement remains shielded by price protection until its own renewal point.
Why the Reduced Frequency Helps Budget Planning
Despite the trade-offs described above, there is a real, practical benefit to this change worth acknowledging directly. Twice-yearly currency adjustments have historically made annual budget planning for Microsoft licensing genuinely difficult, since a finance team building a twelve-month forecast had to account for the possibility of a mid-year adjustment landing on top of whatever renewal-driven changes were already expected. Reducing that to a single, predictable January date, with guidance issued the preceding November, gives finance and procurement teams a considerably clearer window to model the coming year’s Microsoft costs with one known adjustment point rather than two.
The confusion this change addresses is worth naming specifically, since it is a pattern we have seen recur across client conversations rather than a purely theoretical concern. Under the twice-yearly model, it was common for a customer to see a currency-driven change land close to, but not exactly aligned with, their own renewal date, and to assume the movement in their invoice was tied to the renewal itself rather than to a separate, semi-annual currency review running on its own schedule. That misattribution made it genuinely difficult for some finance teams to explain a price movement internally, since the actual cause, a scheduled currency adjustment rather than a negotiated renewal change, was not always obvious from the invoice alone. A single, well-publicised annual date removes much of that ambiguity, since there is now only one point in the year a currency-driven change can occur, and it is the same date for every customer rather than one of two dates that could each land at a different point relative to an individual renewal.
That clarity is worth building directly into an organisation’s own annual budgeting calendar. Treating the November guidance announcement as a fixed, recurring input to the following year’s Microsoft budget process, rather than reacting to it as an unplanned announcement each time, is the practical way to capture the predictability benefit Microsoft is describing without being caught off guard by whatever direction the January adjustment ultimately takes.
Conclusion
Microsoft’s shift to a single annual local currency pricing adjustment, taking effect from January 2027, genuinely simplifies the calendar of when currency-driven price changes can occur, but it does not reduce how much those changes can move pricing in either direction, and it removes the second adjustment point that previously gave some customers, particularly those on monthly commitments, an additional chance for exchange rates to move in their favour.
Organisations should build the November guidance announcement into their standing annual budget process, confirm directly how price protection terms interact with the new January date for any EA renewal or new product addition landing near that period, and treat this as a genuine planning simplification rather than assuming it removes currency risk from Microsoft licensing altogether.
