What the Microsoft price changes mean for next year's budget

Three things moved in Microsoft’s licensing on 1 July 2026. Two change a number. The third changes the structure of the budget, and it is the one most likely to be missed.

Base prices went up

The increase applies per seat, whether or not anyone in that seat uses AI. If your renewal falls after 1 July, it is already inside the figure your account manager is quoting, and comparing it against last year’s spend will understate the change.

The practical step is to model the new all-in seat cost across your actual tier mix before the renewal conversation rather than during it. Vendors negotiate better against a buyer who has already done the arithmetic.

Copilot Chat moved into the base packaging

Capabilities that used to require a separate conversation are now included in most tiers. That is genuine value, and it changes two things.

First, a proportion of your staff now have AI in front of them without anyone deciding they should. That is not a problem in itself, but it does mean the question “do we need an AI policy” has already been answered for you.

Second, it makes the premium tiers a sharper decision. The gap between what is included and what costs extra is narrower than it was, so the question becomes which specific roles justify the upgrade rather than how many licences to buy.

Agent usage is billed by consumption

This is the structural change. Every other line in a Microsoft bill is a seat count you can multiply and predict. Agent usage is credits — bought up front or paid as consumed — and it rises with adoption.

Three properties make it different from anything else in the budget:

• It grows when the rollout succeeds, so cost and success are correlated.
• It can be started by someone building an agent, without procurement involvement.
• Nobody is watching it in the first month, which is when the habits form.

A budget that treats agent usage as a fixed annual figure will be wrong. It needs a forecast built from expected volume, a ceiling, and an alert that reaches a person rather than a mailbox.

What to do before the next renewal

Count what you actually use. Most estates are paying for tiers that people do not use the features of, and for products duplicated by something else in the stack.

Decide the tier mix deliberately. Who genuinely needs the premium tier is a business question, not a default.

Put an owner on consumption. One person who holds the forecast, watches the number and can explain a movement. Day one, not after the first surprising invoice.

Reconcile to the ledger. Microsoft’s own reporting and your accounts payable record rarely agree at first. The difference is usually where the recoverable money is.

The vendor changed the shape of the bill. The response is to change the shape of the budget, which is ordinary work — it just has to happen before the invoice rather than after it.