Microsoft has announced that local currency pricing updates for Commercial Cloud services move to an annual cadence, applied every January, with the next update effective January 1, 2027. This replaces the previous pattern of multiple adjustments within a year as exchange rates moved.
For organizations buying in currencies other than USD, this is a meaningful improvement in predictability and a small loss of opportunity, and it is worth understanding both sides.
What gets better
Multi-currency budgeting for Microsoft services has been genuinely difficult. An organization operating across the EEA, the UK and the Nordics could see local price adjustments arrive at different times, on different SKUs, with limited notice, none of which aligned to its own financial year. Building a twelve-month forecast against that was an exercise in adding contingency.
A single annual date changes that. From January 2027, the local currency price you hold in January is the local currency price for the year, absent other structural changes such as the July 2026 global update. For finance teams, that converts a variable into a constant and removes a recurring source of forecast variance that was never anybody's fault.
It also simplifies the internal chargeback question. Organizations that recharge Microsoft costs to business units in local currency have had to decide whether to absorb intra-year adjustments centrally or push them through mid-year. That question largely disappears.
What gets harder
The intra-year adjustments occasionally created favourable moments. An organization with flexibility about when to place a large commitment could, in principle, time it against a currency position. That optionality is being removed, and with it a small amount of value that sophisticated buyers were able to capture.
More materially, an annual reset concentrates risk into a single date. Where previously a currency movement was absorbed in increments through the year, it will now arrive as one adjustment each January. For a currency that has moved significantly against USD over twelve months, that adjustment will be larger and more visible than the sum of the increments it replaces. Organizations should plan for January as a step change rather than assume the smoothing they experienced previously.
What to do about it
Three practical steps. First, move your Microsoft budget review cycle so it lands after the January adjustment is known rather than before it. A forecast built in November against December pricing will be wrong by January, and the error will be structural rather than random.
Second, for organizations with material non-USD exposure, model a plausible range for the January adjustment based on the trailing twelve-month currency movement and hold contingency against the upper end. This is basic treasury practice that Microsoft's previous cadence made awkward to apply and the new cadence makes straightforward.
Third, note the interaction with commitment timing. A multi-year commitment priced in local currency locks that currency position for the term. Under an annual adjustment cadence, the value of locking a rate before a January adjustment is more predictable than it was, which makes December a more interesting month for large commitments than it used to be — with the caveat that Microsoft's promotional calendar frequently runs on a different rhythm and may pull the optimal date elsewhere.
A related note for EEA customers
Separately from this change, minor pricing precision adjustments of a few cents were applied to selected Microsoft 365 and Office 365 SKUs in EUR, DKK, NOK, SEK and CHF on July 1, 2026, arising from an EU settlement compliance update. These are distinct from both the global increase and the currency cadence change, and they should be identified separately when reconciling invoices in those currencies.
How Lorexus engages
We build multi-currency Microsoft forecasts that account for the annual adjustment cadence, model commitment timing against both the pricing calendar and the promotional calendar, and structure chargeback so business units see stable numbers. Book a free 15-minute call with our senior engineers.