The CMA Opened a Clock. Your Estate Still Needs a Number.

The CMA Opened a Clock. Your Estate Still Needs a Number.

On 31 March 2026 the UK Competition and Markets Authority said it would look at Microsoft’s business software. On 14 May it opened the file. The CMA Microsoft SMS inquiry will decide whether Microsoft should be designated as having strategic market status for that ecosystem. It is the fourth such investigation since the UK’s digital markets regime came into force in January 2025. The clock is nine months. The Investigation Notice sets the statutory deadline at 13 February 2027.

That’s the problem.

This is not a designation. It is a clock. The CMA has not found that Microsoft has strategic market status, and it has not written a remedy. A prior cloud investigation already put a number next to the same licensing pattern. If you cannot produce the Azure-versus-listed-provider delta on your own estate this week, you will spend those nine months reading headlines.

What the CMA actually opened

The 14 May press release is the scope. The CMA has “heard that UK customers may not always be able to effectively combine software from Microsoft with that of other providers, limiting their ability to get access to the best products at the most competitive prices.” The file covers productivity applications, operating systems, databases, and security software, and how AI competitors integrate with Microsoft’s business software. Sarah Cardell, the CMA’s chief executive, said: “Our aim is to understand how these markets are developing, Microsoft’s position within them and to consider what, if any, targeted action may be needed to ensure UK organizations can benefit from choice, innovation and competitive prices.” An SMS designation would allow the CMA to consider interventions. The notes to editors are explicit: designation does not assume wrongdoing. If designated, later processes could include conduct requirements or pro-competition interventions, subject to legal tests. That is not a list of orders, and it is not a change to your Enterprise Agreement. Do not brief a remedy the CMA has not written.

The licensing concern is older than this notice. The CMA’s cloud services market investigation closed on 31 July 2025. It found that Microsoft’s licensing practices were adversely impacting AWS and Google in cloud. The 14 May release says an SMS designation would also let the CMA consider intervening on that concern. The final decision illustrated the scale of the market: if UK IaaS and PaaS prices were on average 5 percent above a well-functioning market, customers would pay around £500 million more per year on £10.5 billion of 2024 revenue. That sentence is an illustration, not a Microsoft-only listed-provider invoice, and it is not a finding from this SMS inquiry.

The CMA Microsoft SMS inquiry is a clock, not a designation

Nine months. 13 February 2027. That is the decision date in the Investigation Notice.

Until then, nothing in the notice changes the price of a Windows Server core on AWS, Azure Hybrid Benefit on Azure, or the SQL Server quote in your last placement pack. The vendor will still walk in with an Azure conversation. Legal will still ask whether this is the CAT Windows Server listed-provider claim. It is not. That file is a class action. This is a designation investigation. You can be in both rooms. You cannot answer both with a headline.

Most SAM reports still collapse “Windows Server” and “compute.” The software did not change when the host moved. The license price did. Azure Hybrid Benefit is the Azure path. Listed-provider terms are the other. If your reports still collapse those cores into one unit cost, you are reading a reporting layer, not a license position.

This is not a criticism of the teams building those reports. The tools prove what is deployed. They do not recast the same estate two ways before a nine-month clock. The gap is interpretation work. An analysis that arrives after February 2027 is a document. One that arrives during the next cloud meeting is a decision input.

Picture the room. Your CIO has forwarded the CMA release. Finance wants to know what “£500 million” means for this organization. Procurement wants a stay-versus-move number on the next Windows Server estate. If SAM takes three weeks to split cores by cloud, the headline becomes the file.

If that feels familiar, the problem is not your team’s maturity. Do not let Microsoft frame the next meeting as “nothing has been designated, so nothing changes.” On the law, that sentence is fair. Yours is narrower: what are we running, on which cloud, what does Azure Hybrid Benefit do on Azure, and what do listed-provider terms do on AWS or Google Cloud. “We are multi-cloud” is not a number. A nine-month clock is not a discount.

What to have before February 2027

Do this in the next thirty days, as a decision pack rather than a project. The event is the next placement and the next executive ask, not the designation notice.

What you produceWhy it changes the next conversation
Windows Server and SQL Server cores by cloud, this weekDistinguishes a multi-cloud slide from cores already on a listed provider. A stale count is a document, not a position.
How those cores are licensed: Azure Hybrid Benefit or reallocation on Azure; listed-provider or license-included on AWS and Google CloudThat split is the commercial fact the prior investigation put a market number on. If you cannot say which quote applies, you do not have a position.
Azure-priced license cost versus listed-provider cost on the same estateThat delta is the number. Not a share of £500 million. Your cores, two clouds.
A one-page note for the CIO and legalThis is the SMS file, not the CAT class. What we take into the next placement. What we will not claim the CMA has already decided.

Can a non-specialist brief the CIO in fifteen minutes from the pack you have today? If the answer is no, you do not have a CMA Microsoft SMS position. You have a library and a deadline.

The decision layer, not another inventory

You already have discovery data and cloud bills. The gap is not another inventory. The gap is turning that estate into a decision before February 2027: which cores sit where, and what the same estate costs on Azure and on a listed provider. LICENSEWARE sits on the inventory and ITSM tools you already run. It is not a rip-and-replace SAM suite. It is a decision layer: what matters, why it matters now, what should happen next. Audit defense is the commercial question if listed-provider terms are how you keep a non-Azure cloud. Microsoft Deployment Manager is the pack that splits those cores; Microsoft integration is the Graph side if M365 sits on the same estate, and digital sovereignty is the European overlay if listed-provider terms are how you keep a non-Azure cloud.

If you are heading into a cloud placement or an EA conversation and your current tools still need three weeks to turn a host list into that number, book an Audit Readiness Review. You can also start on the free plan and run the analysis on your own data.

The question to walk in with

Do not let the next meeting open as “has the CMA designated Microsoft.” It has not. The right question is: what are we actually running, on which cloud, what does the same estate cost on Azure and on a listed provider, and can we defend that number before February 2027. That is a data question, not a sales question.

The CMA will take its nine months. You still have to place the next workload. The vendor will walk in with a number. The only question is whether you have yours first: current, defensible, and tied to the contract in front of you.

FAQ

Did the CMA designate Microsoft with strategic market status? No. On 14 May 2026 it opened the investigation. The statutory deadline is 13 February 2027. Opening a file is not a finding.

Is the £500 million my bill? No. That figure is a 5 percent illustration from the CMA’s earlier cloud investigation on £10.5 billion of UK IaaS/PaaS revenue. It is not your exposure and it is not a finding from this SMS inquiry.

Is this the same as the CAT Windows Server listed-provider claim? No. The CAT file is an opt-out class claim. This is an SMS designation investigation. Same licensing pattern. Different clock.

Alex Cojocaru

Alex has been active in the software world since he started his career as an Analyst in 2011. He had various roles in software asset management, data analytics, and software development. He walked in the shoes of an analyst, auditor, advisor, and software engineer, being involved in building SAM tools, amongst other data-focused projects. In 2020, Alex co-founded Licenseware and is currently leading the company as CEO.