The Microsoft 365 and Office 365 commercial pricing update took effect on July 1, 2026. For most organizations the first invoice reflecting it will arrive in the coming weeks, and for a meaningful number of them the figures will not match expectations — usually because of how renewal dates, term boundaries and packaging rollout interact rather than because anything is wrong.
Here is how to read it.
Rule one: your renewal date governs, not July 1
Existing subscriptions remain at their prior price until the subscription renews. A tenant with an annual term running to November 2026 continues paying the old rate through November regardless of the July 1 date. If your July invoice shows an increase on a subscription that has not reached its anniversary, that is worth querying with your partner.
The corollary is that increases will arrive at different times across a mixed estate. Organizations with subscriptions purchased at different points in the year will see the change phase in across several months, which makes a single before-and-after comparison misleading. Reconcile per subscription against its own term dates.
Rule two: mid-term upgrades pull your start date forward
Microsoft's FAQ is explicit on one point that catches people out: customers who perform a mid-term upgrade to the Microsoft 365 E3 or E5 three-year SKUs pull their subscription start date forward. In other words, an upgrade is not a neutral act — it resets the term, and it resets it onto whichever price table is in effect at that moment. An upgrade executed before July 1 locked the old pricing for the new term. One executed after does not.
Microsoft's published FAQ does not address how additional seats added to an existing subscription mid-term are priced. If your estate has grown since its last renewal, confirm the treatment of those seats with your partner directly rather than assuming they inherit the original term's rate — the answer varies by agreement type and it is worth having in writing.
Rule three: packaging and pricing are not synchronised
The packaging changes — Defender for Office 365 P1 into Microsoft 365 E3, Security Copilot and Cloud PKI into E5, Intune Plan 2 into E3 and EMS, additional mailbox storage into Business Basic and Standard — roll out progressively between June and August 1, 2026, with a minimum of thirty days notice through the Message Center. Your price may move before the capability arrives, or the capability may arrive before your renewal moves the price. Both are expected.
This matters commercially. Cancelling a standalone Defender for Office 365 P1 subscription because you believe it is now bundled, before the packaging has actually reached your tenant, creates a coverage gap. Confirm the capability is present in your tenant before releasing the add-on, and time the cancellation to the add-on's own term boundary.
Rule four: EEA currencies have a separate small adjustment
Selected Microsoft 365 and Office 365 SKUs in EUR, DKK, NOK, SEK and CHF received minor pricing precision adjustments — cents, not percentages — effective July 1, arising from an EU settlement compliance update. This is separate from the global increase. Reconciling in those currencies without accounting for it produces small unexplained variances.
The three actions worth taking now
First, build a per-subscription reconciliation showing term dates, old rate, new rate and the month the change lands. This is the artefact finance needs and almost nobody has. It converts "Microsoft put prices up" into a forecast.
Second, list every add-on subscription that the repackaging makes redundant, with its term end date. Each of those is a cancellation to schedule, and the aggregate frequently offsets a large share of the increase. The most common candidates are Defender for Office 365 P1, Intune Plan 2, Intune Remote Help, and for E5 customers, separately provisioned Security Copilot capacity.
Third, complete the right-sizing you deferred. Inactive assignments, tier misfits and duplicated subscriptions all cost more than they did last quarter. The recoverable amount in a typical mid-market estate exceeds the increase; the reason it is rarely recovered is that nobody owns the review.
What is coming next
Microsoft has confirmed that local currency pricing moves to a single annual update every January for commercial cloud services, with the next one effective January 1, 2027. That replaces the previous pattern of multiple intra-year adjustments and makes January the date to plan around going forward.
How Lorexus engages
We build the per-subscription reconciliation, identify and schedule the redundant add-on cancellations against their term boundaries, and run the right-sizing audit. In the estates we have reviewed this quarter, recovered spend has consistently exceeded the increase. Book a free 15-minute call with our senior engineers.