Microsoft's Supreme Court Gambit on Software Exhaustion Could Redraw the Licensing Architecture for Every SaaS Vendor in Britain

Something quietly extraordinary happened in British software law last week. Microsoft secured an extended stay of proceedings in its long-running battle with ValueLicensing, having lost twice already, and is now petitioning the UK Supreme Court for one final appeal. The case, formally JJH Enterprises Ltd (t/a ValueLicensing) v Microsoft Corporation [2026] EWCA Civ 872, concerns a doctrine so fundamental to how software is bought and sold that it has a name borrowed from property law: exhaustion.

For engineers, product managers, and anyone building a licensing system in 2026, this is not a courtroom curiosity. It is a question about whether the perpetual-licence model, the one that shaped three decades of enterprise software, can be legally dismantled by contractual means and by herding customers onto subscriptions.

What the Doctrine of Exhaustion Actually Means

Software exhaustion is the principle that once a copyright owner sells a copy of its software, copyright cannot be used to control what happens to that copy next. Think of it as a kind of plumbing one-way valve: once the water flows through the meter, the supplier cannot demand it back. The EU's UsedSoft ruling established this principle for digital downloads in 2012, and UK courts have inherited and extended that reasoning post-Brexit.

ValueLicensing buys pre-owned perpetual licences for Microsoft products, including Windows and Office, from businesses that no longer need them, and resells them. Microsoft's position is that those licences were not exhausted and that reselling them constitutes copyright infringement, which would collapse ValueLicensing's underlying competition claim before it ever reached a substantive hearing.

The Competition Appeal Tribunal disagreed in late 2025. The Court of Appeal then dismissed both of Microsoft's appeals on 7 July 2026, ruling on two subsidiary points: whether the presence of bundled non-program works (icons, fonts, user-interface elements) prevented exhaustion, and whether volume licences could legally be subdivided. The Court found for ValueLicensing on both. On the first point, it applied the reasoning of UsedSoft, Nintendo, and Tom Kabinet to conclude that the bundled assets were incidental to the software program, and the Software Directive therefore governed the whole package. On the second, subdivision of volume licences was found to be lawful.

The Court noted, with a certain judicial dryness, that Microsoft's approach would produce an odd result: that a sprinkling of clip art could defeat the doctrine of exhaustion altogether. Courts, much like compilers, tend to reject logic that produces absurd outputs.

Microsoft has now indicated it will seek Supreme Court permission to appeal. Proceedings received an extended stay on 21 July 2026. If the Supreme Court declines to hear the case, it returns to the Competition Appeal Tribunal for a full substantive hearing, with a trial mooted for 2027.

What This Means Architecturally

So what does this mean for the engineering community, and why does it matter beyond one company's litigation budget?

The subscription-vs-perpetual question is not settled by business preference alone. If exhaustion doctrine holds at the Supreme Court level, it creates a legal floor beneath the secondary software market. Vendors cannot use copyright to foreclose resale; they can only try to foreclose it contractually, and that is exactly the competition-law question that proceeds to trial if Microsoft loses the appeal. ValueLicensing is seeking £270 million in damages, alleging Microsoft built restrictive clauses into contracts and offered customers better terms to abandon perpetual licences.

The Court of Appeal separately confirmed that the Competition Appeal Tribunal has full jurisdiction to decide copyright questions when they are necessary to resolve a competition claim. That procedural ruling alone is significant: it clears a path for other claimants who faced the same argument that copyright issues had to go elsewhere. A collective action brought by Alexander Wolfson, which could expose Microsoft to liability measured in billions, now stands to benefit directly from that jurisdictional clarity.

For SaaS vendors watching from the sidelines, the reading is nuanced. Pure SaaS products, delivered as a service rather than as a discrete copy transferred to the customer, are not obviously subject to the same exhaustion analysis. There is no "copy" in the traditional sense; the customer accesses a running instance, not a transferable artefact. That architectural choice, the one Salesforce made in 1999 and that every subsequent cloud-native vendor has inherited, insulates SaaS from the resale question almost by design. But any vendor still shipping perpetual on-premises licences alongside a subscription tier, and many enterprise vendors still do, now has to model their licensing terms against the possibility that those licences can be legally resold.

The UK Software Formation Context

The timing lands in an unusually active period for UK software company formation. Data from Your Company Formations shows that software and AI registrations under SIC 62.01 rose 86% in Q1 2026, more than doubling the full-year 2025 growth rate of 38.4% in a single quarter. Software publishing registrations grew 45.4% and web portal formations rose 27.4% in the same period. Britain is, by this measure, in the middle of a digital formation boom.

Those new companies are overwhelmingly choosing SaaS or cloud-native delivery, not least because it is cheaper to build. But they will inherit a licensing environment whose legal contours are still being drawn at the level of the Supreme Court.

The ONS published the Introductory Guidelines for SIC 2026 on 31 July 2026. For the first time, general-purpose AI software and AI model development are separated from broader software categories at the 5-digit level. Classification is not just bureaucracy; it determines how regulators, investors, and statistical agencies measure and monitor the sector. Once Companies House mandates adoption, founders choosing between an "AI model development" code and a "general-purpose software" code will be making a statement about how they intend to be counted.

The Trademark Signal

AIBD analysis of IPO Trade Mark Dashboard data shows a striking counter-signal: Class 9 UK trademark filings (covering software, computer programs, and electronic apparatus) reached 3,925 in 2026-Q3, a fall of 58.6% against the prior period. That is a dramatic contraction in brand-protection activity in the primary class for software goods, even as company formations surge. Two interpretations are plausible: either founders are deferring trademark spend until product-market fit, or the classification migration triggered by the Nice 13th Edition (which came into force in January 2026, moving several goods out of Class 9) is skewing the comparison. Either way, the gap between formation velocity and IP protection behaviour is worth monitoring.

The 6-12 Month Implications

If the UK Supreme Court grants permission to appeal, the substantive competition trial almost certainly slips to 2028. That gives every enterprise software vendor operating perpetual licence models in Britain a longer runway to restructure terms before a definitive ruling. Expect to see licence agreement updates that try, carefully, to distinguish between licence grants that are perpetual and those that are transferable, on the theory that the two concepts can be separated.

If the Supreme Court declines the appeal, the Competition Appeal Tribunal trial proceeds on the merits in 2027. That trial will determine whether Microsoft's conduct was anti-competitive, and the collective action exposure broadens. Vendors with similar subscription-migration strategies will read that trial transcript with attention.

For the engineering teams building licensing systems: the exhaustion doctrine is now a first-class architectural concern. The decision of whether to ship software as a transferable artefact or as a running service is no longer just a deployment preference. It is a legal one.