The argument in brief
McCluggage's case starts with a trade-off. Renewing Microsoft is the easy option in the short term. Integration is simple, the estate is already in place, and switching looks expensive. His claim is that thousands of individually sensible renewals add up to something else. In his words, they leave one supplier deep inside public-sector data, identity and security architecture.
He says the consequence matters most for AI. If every new AI rollout has to sit on infrastructure that one vendor controls, competing AI suppliers are priced and engineered out before they can bid. He points to Windows Server and SQL Server as the "foundational grip". His reasoning is that penalising those workloads on rival clouds pulls data gravity into Microsoft's ecosystem for good.
This is advocacy, and it is a plausible reading rather than a proven outcome. No evidence in front of me shows that any specific public contract is irreversibly locked in.
What the CMA has actually put on the record
On 16 October 2026 the CMA began consulting on its proposed decision to designate Microsoft as having strategic market status in respect of its business software ecosystem. The investigation itself was launched on 14 May 2026.
Key points for IT teams:
- The status is provisional. The CMA's proposed decision is a provisional assessment that Microsoft meets the statutory conditions for designation. It is not a final ruling.
- The deadlines are close. Comments are invited by 13 November 2026, and the CMA will take a final decision by 13 February 2027. The consultation is still open as of today.
- Five areas are in scope. They are PC operating systems, productivity suites, security software, server operating systems and relational database management systems.
- A roadmap came with the proposal. The CMA published an indicative roadmap setting out where it would gather more evidence and consider possible interventions if Microsoft is designated. Proposed areas include how security products are bundled, and whether organisations have real choice over which cloud runs their software licences.
- Designation is not intervention. Any action would be a separate step from the decision now under consultation.
- Microsoft disagrees. Microsoft said it does not share the CMA's views in its proposed decision, as reported by Bloomberg and The Business Times.
This is a useful correction to the opinion piece's framing. McCluggage asks the CMA to publish an interim roadmap. The CMA has already published an indicative one tied to the SMS proposal. What he is really asking for is something narrower and procurement-specific: guidance for buyers, plus tests that show whether voluntary commitments are working.
The procurement context
The CMA's own procurement work supplies the backdrop. Sarah Cardell spoke at the House of Commons on 8 September 2026 and introduced two CMA reports. Her speech put annual UK government spending on goods, services and infrastructure at around £400 billion.
Her central warning applies directly to the lock-in debate. Minimising cost today may come at the expense of long-term value through greater competition and market dynamism. The CMA's wider procurement paper uses cloud as a case study. It describes UK cloud supply as highly concentrated, with no UK hyperscaler competitor today.
The CMA does not say that buying Microsoft is bad value, or that departments should leave. Its message is that objectives and trade-offs should be explicit, and that competition effects should count in procurement decisions. The second report, on bid rigging, covers collusion in tenders. It is unrelated to Microsoft and should not be read as evidence of anything about Microsoft.
What the author wants a roadmap to cover
McCluggage lists four proposals. None is CMA policy:
- Non-discriminatory licensing for Microsoft products on rival clouds.
- Interoperability that extends to identity, permissions and AI-agent portability.
- Public-sector contracts with built-in exit plans.
- Independently verifiable evidence, not just documentation, that voluntary commitments are producing real switching and multi-cloud adoption.
Claims to treat carefully
Several figures in the opinion piece could not be matched to primary sources in the evidence I reviewed:
- Microsoft and AWS each holding 30–40% of the UK cloud market.
- Fewer than 1% of customers switching cloud provider each year.
- The 31 March 2026 voluntary commitments, including a longer free egress window moving from 60 to 180 days.
- The claim that over 15 million UK users are in scope.
The CMA's own consultation material describes Microsoft's business software as used by more than one million UK businesses and public-sector organisations, with around 20 million monthly users. That differs from the author's 15 million. One report also says the CMA noted material progress with Microsoft and AWS on data egress fees and interoperability in a separate cloud engagement. That fits the general direction of the author's account of voluntary commitments, but not his specific terms. Treat the specifics as the author's claims until you check the CMA's cloud decision documents.
Practical takeaways for IT and procurement teams
Without waiting for the CMA, public bodies can do several things:
- Map dependencies before renewal. List what sits on Entra identity, Windows Server and SQL Server licences, Microsoft security tooling and Copilot data connections.
- Cost the exit. Estimate egress, retraining, licence re-use and migration effort. The CMA has described switching barriers as the source of Microsoft's strength, so this is where they are likely to show up.
- Ask about AI portability up front. Ask whether agents, prompts, grounding data and permission models can move to another platform.
- Write exit terms into contracts. Use data export formats, assistance periods and licence portability clauses.
- Respond to the consultation. Customers and competitors have until 13 November 2026 to comment, and the CMA has said Microsoft will not use confidentiality provisions to stop parties responding.
Analysis: two clocks
The clearest point in the opinion piece is that two clocks are running. Procurement and AI rollouts move on contract cycles and budget years. The CMA's formal process runs on statutory deadlines through February 2027. The CMA's own roadmap would only start to examine specific interventions after any designation, so remedies are likely to follow later still.
Whether that gap is a risk or just how regulation works is the real disagreement. Microsoft can argue that its commitments were made in good faith and that customers are free to choose. Critics will say that free choice means little once the data and identity layers are tied together. The evidence so far leaves both views open. What it does support is a modest conclusion: buyers who plan for portability now lose little if regulators move slowly, and gain a lot if they don't.