UK Watchdog Widens Cloud Probe to Kubernetes and Identity Services
The CMA's new call for evidence puts Kubernetes and IAM under scrutiny for cloud lock-in. The consultation closes December 3, so UK teams have time to respond.

The UK's Competition and Markets Authority (CMA) has widened its digital sovereignty work beyond egress fees and into the technical layers where cloud workloads actually get locked in. A new questionnaire asks how cloud developers use Kubernetes and identity and access management (IAM) services, with the explicit aim of probing vendor lock-in among the hyperscalers. For anyone running multi-cloud estates or planning a move off a single provider, that's a meaningful shift in what the CMA considers the battleground.

What the CMA is asking
The call for evidence builds on work the CMA has already done with Amazon Web Services (AWS) and Microsoft. Those discussions focused on lowering egress fees and improving interoperability between the two platforms. Egress charges have long been the most visible friction point for customers who want to move data out of a cloud, but Kubernetes and IAM sit deeper in the stack. Container orchestration determines how workloads are packaged and scheduled, and identity determines who and what can reach them. If either is tightly coupled to one provider's services, moving the application becomes a rebuild rather than a migration.

The inclusion of IAM is the detail I'd flag first. Identity is the control plane for almost everything else in a cloud estate. Access policies, service principals, federation and conditional access rules all tend to accumulate around one directory. Once that happens, switching cloud providers means re-plumbing authentication for every workload, not just moving storage buckets. The CMA's questions are likely to probe how much of that coupling is a deliberate product decision and how much is an artefact of how the services were designed.

Where AWS and Microsoft stand
AWS has already been through this process. Earlier this year the CMA was largely satisfied that AWS was improving vendor interoperability and reducing lock-in for British cloud users. The clearest sign of that work is AWS Interconnect, which can connect with Azure, Oracle Cloud Infrastructure (OCI), and Google Cloud Platform (GCP). That gives AWS a credible story to tell, but the new consultation reopens the question for its identity offerings specifically. Expect AWS's identity services to face the same scrutiny that Microsoft's Entra ID is about to receive.

Microsoft is in a different position. It is currently under the CMA's microscope over whether it should be designated with strategic market status (SMS) for its business software ecosystem. A similar consultation on that question closed the week before this call for evidence was published. So Microsoft is facing two overlapping lines of inquiry: one on the breadth of its business software position, and another that now reaches into identity and container technology. Entra ID's role as the identity layer for Microsoft 365 and Azure makes it an obvious focus, and that's where the two threads are likely to meet.

Google and Oracle offer comparable identity and container services with their own cloud platforms, so the questionnaire will likely touch them too, even if the coverage so far centres on the two providers already in the CMA's sights.

Who else sits in the identity market
The IAM question also pulls in vendors outside the hyperscale group. Okta is the obvious independent name in workforce identity, and Palo Alto Networks is now a serious player through its Idira platform, which followed its CyberArk acquisition last year. That matters because a competition review of identity can't look only at the hyperscalers. Customers who buy identity from an independent vendor and run workloads on a hyperscaler are exactly the users who feel lock-in most when those two parts are tightly integrated.

The market numbers the CMA is citing
According to CMA data, Microsoft held up to 70% of the British security software market in 2025. AWS, Google and Palo Alto Networks each came in at 5% or less. Okta, CrowdStrike and Ping Identity were each put in the 5% to 10% range. Those are the figures the CMA has published, and they explain why the security software question keeps coming back into the frame. A single vendor with that share of a category gives customers little practical leverage when renegotiating or considering a switch.
What to do before December 3
The consultation is open to stakeholders both inside and outside the UK and closes on December 3. If your organisation runs significant workloads on Kubernetes or depends on a single cloud's identity service, now is the time to document where that dependency sits. Teams in this position typically find the same few pinch points: custom authentication flows tied to one directory, container platform features that don't have portable equivalents, and egress costs that only become visible when someone models a move. None of that requires a formal response to the CMA, but having your own inventory ready will make any future migration or renegotiation far less guesswork.
My read is that this investigation will be judged less on headline egress fees and more on whether identity and orchestration can be separated from the platform underneath them. Watch whether the CMA's follow-up focuses on interoperability standards, on contract terms, or on technical changes like the AWS Interconnect model. Each points to a different set of obligations for the vendors, and a different set of decisions for the teams running their infrastructure.