Skip to content
Back to Insights
IT Strategy3 February 20265 min

Microsoft July Licence Changes: Time for a Proper Review

From July, Microsoft is rolling out a new wave of licence updates including price adjustments and expanded feature sets across several Microsoft 365 plans. For many businesses, this will mean paying more per user but also receiving more capability than before. And that is where the opportunity lies.

While exact changes vary by licence type, July's updates generally fall into two categories. First, price increases -- some Microsoft 365 plans are increasing in cost, particularly where security tooling has been expanded, AI or automation features are bundled, or enterprise-grade controls are now standard. Second, feature expansion -- many licences now include tools that were previously add-ons, separate SKUs, or only available on higher-tier plans.

In reality, many organisations keep legacy licences they no longer need, pay for overlapping tools (third-party plus Microsoft), and underuse features already included in their subscription. So when prices rise, it feels like a straight cost increase -- even when it does not have to be.

This is the perfect moment to ask: Are we paying for third-party tools that Microsoft now includes? Are we on the right licence tier for how we actually work? Could we consolidate security, email, device management, or compliance tooling? Are all users licensed appropriately -- or is everyone on the max plan by default?

In many cases, we see businesses reduce overall spend by removing duplicate products, standardising licence types, and aligning licences to real-world usage.

Microsoft has quietly turned many licences into serious security platforms. Businesses still paying separately for endpoint protection, email security, identity controls, or basic compliance tooling often do not realise they already own capable alternatives inside Microsoft 365. That is money leaking out of the business every month.

If Microsoft is going to bundle more into your licences, you should use those features, replace what you no longer need, design a simpler, more secure stack, and reduce overall operational complexity. Done properly, July's changes can be a net positive, not a budget headache.

Microsoft has moved the goalposts -- but they have also widened them. Now is the time to review your licences, consolidate tooling, cut waste, and make sure you are paying for value, not inertia.