Listed-Provider Pricing Is Now a UK Class File
The UK Competition Appeal Tribunal granted an opt-out Collective Proceedings Order on a Windows Server listed-provider claim. Judgment [2026] CAT 34 was handed down on 21 April 2026. The allegation is that Microsoft charged more for Windows Server on rival clouds (AWS, Google Cloud, and Alibaba) than on Azure. The proposed class is about 59,000 UK organizations. Aggregate damages are estimated at more than £1.7 billion. The Tribunal said the claim “comfortably passes” the reasonable-prospect threshold.
That’s the problem.
This is not a courtroom story. It is a license-position story. Listed-provider pricing is no longer a 2024 CISPE settlement or a regulator probe in another country. It is a live UK class claim. If you ran Windows Server on a cloud that is not Azure, you need that number this week (for the opt-out window, and for the next placement).
What the CAT actually decided
The claim was filed on 3 December 2024. Lead claimant is Dr Maria Luisa Stasi. Microsoft objected on blueprint-to-trial, funding, and opt-out versus opt-in. The Tribunal certified anyway. That is a certification. It is not a finding that Microsoft overcharged anyone, and it is not a damages award.
Microsoft applied for permission to appeal the CPO. The Tribunal refused. The application has been renewed before the Court of Appeal. Believe the last sentence of any vendor statement that “today’s decision makes no final determination.” A CPO is a green light to trial, not a check.
The class, as the PCR defined it and the Tribunal certified, is organizations that obtained a licence to use Windows Server from a Listed Provider during the claim period. A sub-class covers holders of on-premises licences with Software Assurance who are alleged to have suffered additional loss. The CPO is opt-out: UK-domiciled organizations in the class are in unless they leave. The order sets a domicile date three months after the CPO is drawn, and an opt-out window after the Rule 81 notice is published.
The same licensing has been in more than one room. In 2024 Microsoft settled with CISPE, the EU cloud-vendor group, with a payout and commitments to change its practices. On 31 July 2025 the CMA’s cloud market investigation found that Microsoft’s licensing practices were adversely impacting AWS and Google in cloud. None of that is a UK class file. This is.
Listed-provider pricing is now a live UK class claim
Look at your own cloud file. Most SAM reports still have a row that says “Windows Server” and a FinOps view that says “compute.” Those two words hide the claim.
The Tribunal’s judgment sets out two alleged licensing practices. SPLA pricing: wholesale Windows Server prices to rival clouds higher than equivalent licences on Azure. Re-licensing: Azure Hybrid Benefit lets an on-premises licence run on Azure, but the same licence on a listed provider needs a re-licensing fee. The software did not change. The cloud did. The license price followed the cloud. That delta is what the class is about. It is also what your next placement is about.
If your reports still collapse “Windows Server” 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 price the same core two ways before legal asks whether you sit in a class of 59,000. The gap is interpretation work.
Picture the room. Legal has forwarded the CAT judgment. Your CIO wants to know if you are in the 59,000. Procurement wants to know whether the next AWS Windows Server quote is still the right buy. FinOps wants the Azure-versus-listed-provider delta in the TCO. If SAM takes three weeks to recast cores by cloud, legal answers with a headline and the placement happens on the vendor’s number.
If that feels familiar, the problem is not your team’s maturity. A class-claim question is being answered with a single-cloud entitlement report. The vendor will walk in with an Azure conversation (and, separately, with a statement that nothing has been decided). Both can be true. Neither is your number.
Do not let Microsoft frame the next meeting as “the tribunal has not found anything, so nothing changes.” On the law, that sentence is fair. Yours is narrower: what Windows Server did we run on a listed provider, what did the same estate cost on Azure, and are we in the class the CAT described. “We are multi-cloud” is not an answer. A 2024 European settlement is not a UK opt-out decision.
The number behind a Windows Server listed-provider claim
Do this in the next thirty days, as a decision pack rather than a project. The event is the opt-out window and the next Windows Server placement (not the trial).
| What you produce | Why it changes the next conversation |
|---|---|
| Windows Server instances and cores by cloud, this week: Azure, AWS, Google Cloud, Alibaba, anyone else | Distinguishes a multi-cloud slide from cores already on a listed provider. A stale count is a document, not a position. |
| How those cores were licensed: Azure Hybrid Benefit or reallocation on Azure; listed-provider or license-included on AWS and Google Cloud | That split is the claim. If you cannot say which quote applied, you cannot say whether you look like a class member. |
| Azure-priced license cost versus listed-provider cost on the same estate | That delta is the number. Not a share of £1.7 billion. Your cores, your entitlements, two clouds. |
| A one-page note for legal and the CIO | Are we likely in the class as the CAT defined it. Do we wait for the opt-out date. What do we take into the next placement either way. |
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 Windows Server listed-provider claim position. You have a library and a judgment PDF.
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: which Windows Server cores sit on Azure, which sit on a listed provider, what the license delta is, and what legal and procurement should do before the opt-out date lands. 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. Microsoft Deployment Manager is how Windows Server cores by cloud become a pack; Microsoft integration is the Graph side if M365 sits on the same estate, and listed-provider pricing is also a digital sovereignty issue for European estates that cannot treat Azure as the only legal cloud.
If you are heading into the opt-out window or a cloud placement and your current tools still need three weeks to turn a host list into an Azure-versus-listed-provider 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 Microsoft been found to have overcharged us.” The CAT has not decided that. The right question is: what Windows Server did we run on AWS, Google Cloud, or Alibaba, what did the same estate cost on Azure, and are we in this class. That is a data question, not a sales question.
Microsoft will appeal. CISPE already settled in 2024. The CMA already found an adverse effect on competition. You still have to answer legal this month, and 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.
