Largest Cloud Providers in 2026: AWS, Azure, Google Plus the Niche Leaders

ChatGPT · 2026-03-31T11:54:33-0400

Microsoft is moving into one of its most sensitive regulatory moments in years as the UK’s Competition and Markets Authority prepares to launch a strategic market status investigation into the company’s business software ecosystem from May. The probe will look beyond cloud infrastructure alone and examine how Windows, Word, Excel, Teams, and Copilot fit into Microsoft’s broader commercial power, especially where licensing practices may shape competition in cloud computing and enterprise software. That shift matters because the CMA is no longer treating Microsoft as simply a strong vendor; it is testing whether the company’s reach across software layers gives it an entrenched advantage that can be regulated more directly. The move arrives after years of scrutiny over cloud switching, egress fees, interoperability, and Microsoft’s licensing position in multi-cloud environments. test step from the CMA is best understood as the next chapter in a long-running competition story, not a sudden escalation. The regulator has already spent years examining public cloud infrastructure and concluded that the market is not functioning as well as it could, with concentration, switching costs, egress fees, and technical barriers all under the microscope. It has also signaled that Microsoft and Amazon Web Services deserve special attention under the UK’s digital markets framework because of their scale and influence.
That broader cloud inquiry matters because Microsoft is not just another infrastructure provider. It is a software company whose products sit at the center of office productivity, identity, collaboration, and increasingly AI-assisted work. When the same company controls the software that customers already depend on and the cloud platform where those workloads run, the competition question becomes more complicated. The CMA appears to be asking whether that structure creates a self-reinforcing ecosystem that is difficult for rivals tterms.
The business software angle is especially important because it widens the inquiry beyond raw infrastructure pricing. The regulator is looking at how Microsoft’s licensing practices might affect customer choice when workloads move between clouds, and whether software like Windows and Office can be used in ways that make alternative cloud providers less attractive. That is a far more serious issue than a single discount dispute, because it goes to the architecture of enterprise IT purchasing itself.
There is also a clear policy logic behind the timing. The CMA’s recent cloud work has already pointed to conduct requirements as a possible remedy, and its new regime allows it to impose targeted obligations if it designates a firm with strategic market status. In practice, that means the regulator may not need to prove an old-fashioned monopoly to act; it only needs to show that a company has enough market power and strategic significance to justify intervention.

Why this is not just a cloud story

The heart of the issue is that Microsoft’s software footprint reaches far beyond Azure. Windows, Office, Teams, and now Copilot shape how enterprises buy, deploy, and manage digital work. That gives Microsoft leverage that competitors often cannot match, because customers may stay inside the ecosystem not only for technical reasons but also for commercial convenience and procurement inertia.
This is also why the CMA is taking a layered approach. Cloud infrastructure scrutiny deals with one kind of lock-in, while business software licensing deals with another. Put together, they form a broader picture of how a dominant platform can influence both the destination and the route customers take to get there. That is the kind of structural competition concern regulators increasingly want to address.
In Microsoft’s case, the combination of market power and product integration creates an especially strong case for investigation. A company that owns the office suite, the operating system, the collaboration stack, and a leading cloud platform can influence customer behavior in ways that are not immediately visible in a procurement spreadsheet. That is precisely why the debate has become so intense.

The historical backdrop

The UK cloud market did not suddenly become controversial in 2026. Ofcom and the CMA have been examining it for years, and the market investigation process has repeatedly highlighted friction around egress, interoperability, and software licensing. The provisional and final findings published in 2025 sharpened those concerns and pointed directly to Microsoft and AWS as the most consequential firms in the sector.
That matters because regulators rarely open a major investigation without building a thick evidence base first. In this case, the evidence appears to include customer complaints, market structure analysis, and the practical difficulty many businesses face when trying to operate across multiple clouds. The CMA’s language about “further steps” suggests it believes voluntary improvements are not enough on their own.
The cloud market has also become inseparable from AI. Hyperscalers are not just hosting legacy enterprise workloads anymore; they are powering AI training, inference, data movement, and workflow orchestration. That makes licensing and portability even more important, because the cloud choice today can determine the AI strategy tomorrow.

The CMA’s Strategic Market Status Powers

The UK’s strategic market status regime is designed to be more flexible than traditional antitrust enforcement. Instead of waiting for a full-blown abuse case to mature, the CMA can designate a company as having strategic market status and then impose conduct requirements or pro-competition interventions tailored to the specific digital activity under review. That gives the regulator a sharper tool for modern platform markets.
For Microsoft, that means the investigation is not just reputational. It could become the legal basis for durable obligations that reshape how the company licenses software in cloud environments, how it supports interoperability, and how it structures customer choice. The company would still have room to argue its case, but it would be doing so under a regime explicitly built for dominant digital platforms.

What SMS designation could change

If Microsoft were designated with strategic market status, the CMA could target areas where it believes competition is being constrained. That may include software licensing practices tied to cloud usage, interoperability requirements, or other rules that make it easier for customers to move between providers. In other words, the regulator is not just looking for price cuts; it is looking for market architecture changes.
That matters because the strongest competition concerns in digital markets often involve friction rather than outright exclusion. If a customer can technically switch but faces commercial penalties, administrative complexity, or compatibility problems, the market may still be uncompetitive even without a formal ban on rivals. The CMA has increasingly framed cloud this way.
The design of the regime also reflects a policy choice. Britain wants to act quickly enough to matter, but carefully enough not to scare off investment. That balance is delicate, and Microsoft’s case will likely become a test of whether the CMA can thread the needle.

Why Microsoft is a special case

Microsoft sits at the intersection of software, infrastructure, and AI. That makes the company unusually capable of shaping user behavior across multiple layers of the stack, which is exactly why the CMA is looking at it so closely. It is not just the size of the business; it is the breadth of the ecosystem.
The company’s own statements show that it understands the stakes. Brad Smith said Microsoft will work quickly and constructively with the CMA and provide information to support the regulator’s reviews, a tone that suggests the company wants to shape the outcome rather than simply resist it. That is classic Microsoft regulatory strategy: cooperate publicly, negotiate privately, and avoid a prolonged fight if possible.
But cooperation does not equal surrender. A company can engage constructively while still arguing that the market is more competitive than regulators believe. Microsoft will almost certainly maintain that the ecosystem is dynamic, that customers have choices, and that any intervention must be proportionate. That argument may resonate, but only if it can be backed up by real switching freedom.

Why Licensing Is the Flash Point

Licensing is the part of this story that turns abstract market power into concrete commercial pressure. When customers run Microsoft software on competing clouds, the terms can determine whether that choice is economical, technically feasible, or both. That is why rivals and regulators have been focusing on Microsoft’s licensing model rather than just on Azure pricing.
The complaint, in simplified form, is that Microsoft may be able to make its own cloud more attractive by making rival-cloud deployments of its software more expensive or cumbersome. If true, that would not look like a classic product innovation advantage. It would look more like ecosystem steering through contractual design.

The mechanics of lock-in

Cloud lock-in rarely comes from one obvious clause. More often, it is a combination of egress fees, software compatibility, support terms, volume discounts, and operational complexity. When those factors pile up, customers may stay put even if they would prefer more flexibility.
The CMA has already pointed to those structural barriers in its cloud work. It has separately discussed egress fees and technical barriers, and it has indicated that licensing could be part of the same competition problem. That makes the Microsoft probe feel less like a detour and more like an extension of the same investigation logic.
For enterprise buyers, the practical effect is simple: even if a rival cloud looks cheaper on paper, the real cost of moving may be much higher. That is why procurement teams care about switching friction as much as list price.

Why rivals are pushing the issue

AWS and Google Cloud have both had reason to complain about Microsoft’s licensing posture. They do not need to prove that Microsoft is always winning unfairly; they only need to show that the market is tilted enough to justify intervention. In a contest where the biggest advantage may be friction, that is a powerful argument.
Google in particular has benefited from acting as the most vocal critic of cloud lock-in, especially when the debate centers on openness and portability. AWS, meanwhile, has a different incentive: it wants the regulatory debate to avoid becoming a Microsoft-only story and to recognize that cloud competition issues affect the entire sector. Both positions support a more interventionist stance overall.
The important point is that the issue is no longer theoretical. Regulators are asking whether software licensing can be used as a strategic tool to preserve cloud dominance. That is a serious question because it cuts to the core of enterprise competition policy.

Microsoft’s Ecosystem Advantage

Microsoft’s strength lies in how many business decisions it can influence at once. It sells the productivity suite, the collaboration tools, the operating system, the identity layer, and one of the two largest cloud platforms in the UK market. That gives it a level of ecosystem power that rivals must work much harder to match.
The company also benefits from habit. Enterprises already know how to procure Microsoft software, manage its licensing, and integrate it into internal IT processes. That familiarity becomes a market advantage because customers often default to the path that looks safest, even when alternatives exist.

Windows, Office, Teams, and Copilot

The CMA’s scope matters because it includes the products that define everyday business computing. Windows anchors the desktop environment, Office defines document and spreadsheet workflows, Teams structures collaboration, and Copilot adds a new AI layer to the same stack. Together, they form a commercial ecosystem rather than a collection of unrelated apps.
That ecosystem is strategically powerful because it can make Microsoft’s cloud feel like the natural extension of the desktop. If the same vendor owns both ends of the workflow, customers may perceive less need to mix providers. That is convenient for buyers, but it can also narrow the field of genuine competition.
Copilot makes this even more important. As AI becomes embedded in daily productivity software, the line between product feature and platform power gets blurrier. A company that controls the AI layer inside business software can influence not just what users do, but where they do it.

The AI factor

AI is magnifying the importance of cloud and productivity integration. The same infrastructure that hosts Microsoft 365 workloads also supports AI-driven features, enterprise agents, and data processing pipelines. That means licensing disputes are no longer about legacy software economics alone; they are about the future architecture of work.
The CMA appears to understand that point. Sarah Cardell said the regulator wants a level playing field as AI is rapidly embedded into business software tools, which suggests the investigation is partly about ensuring that AI does not entrench existing dominance even further. That is a forward-looking concern, and a very modern one.
The strategic issue is whether Microsoft’s AI story becomes a reinforcement mechanism for its cloud and software dominance. If Copilot features are easiest to use inside Microsoft’s own ecosystem, rivals may struggle to compete even when they have strong AI offerings of their own. That is the kind of feedback loop regulators are increasingly wary of.

Enterprise Customers Versus Public Sector Buyers

The most immediate beneficiaries of a more aggressive CMA stance would likely be large enterprises and public-sector buyers. These are the organizations most exposed to complex licensing, long-term contracts, and infrastructure dependencies, and they are also the ones best placed to use regulatory scrutiny as negotiating leverage.
For those buyers, the issue is not ideological. It is operational. They want the ability to move workloads, manage resilience, and avoid being locked into one vendor’s terms for every layer of the stack. If the CMA can lower switching friction, that would have direct procurement value.

Why procurement teams care

Procurement teams are often the first to feel the effect of market power, because they see the fine print. If Microsoft licensing makes non-Azure deployments more expensive or complex, buyers may not need a formal remedy to know they are dealing with a leverage imbalance. A regulator’s scrutiny can simply give them the confidence to push back harder.
This matters especially in sectors like finance, healthcare, and government, where compliance, uptime, and exit planning are not optional. Public bodies in particular are under pressure to demonstrate that they can avoid vendor dependency and preserve resilience. A more contestable cloud market could help them do that.
The enterprise story is therefore one of bargaining power. When moving becomes more realistic, incumbent vendors must compete more on quality and less on inertia. That can be healthy for the market even if few customers actually switch in the short term.

Consumer impact is indirect

Consumers are less likely to notice the CMA’s Microsoft probe directly, but they will still feel its downstream effects. Better competition in business cloud and software markets can improve the reliability, pricing, and flexibility of the digital services that consumers use every day. That is a second-order effect, but it is real.
A more open market may also encourage more innovation in services built on Microsoft, AWS, and rival platforms. That matters because consumer apps, public services, and business tools increasingly rely on the same cloud foundations. When the foundation becomes easier to contest, the layer above it can become more dynamic.
So while this story is framed as a business software probe, the broader public interest is much wider. The final consumer impact may show up in the quality and resilience of services rather than in any visible Windows or Office change.

Market and Competitive Implications

For Microsoft’s rivals, this investigation is an opportunity to press a long-running argument: that cloud competition should be measured by more than infrastructure price per unit. They want regulators to recognize the strategic importance of software compatibility, licensing freedom, and portability. That would make competition feel more open and less dependent on one vendor’s ecosystem gravity.
AWS and Google Cloud are likely to frame the CMA’s move as evidence that customers deserve cleaner choices. Even if they do not win every enterprise deal, they benefit if the rules force Microsoft to compete on more neutral terms. That is especially important in deals where Microsoft’s software legacy would otherwise make it the default choice.

How Microsoft may respond

Microsoft’s likely response will be to emphasize cooperation, incremental change, and customer benefit. The company has already said it will provide information quickly and work constructively with the CMA, which suggests it would prefer a negotiated resolution over a more punitive one. That is often the smartest move when a regulator already has years of evidence on the table.
But there is a risk in that strategy too. Voluntary concessions can be interpreted as confirmation that the original barriers were genuine. Once the company begins to reduce egress friction or improve interoperability, regulators may ask why those steps were not taken sooner.
That tension is why the case matters beyond the UK. If the CMA extracts meaningful changes, other regulators may treat those changes as a template. If it does not, critics may argue that the regime is too soft to deal with entrenched platform power. Either outcome will be watched closely.

A contest over the rules of engagement

This is not merely a dispute over Microsoft’s conduct. It is a contest over the rules by which digital markets should operate in the AI era. Should a dominant software company be able to bundle across layers as long as it is technically legal? Or should regulators force a more modular, interoperable market structure?
The answer will shape not just cloud procurement but the future of enterprise software distribution. If portability becomes a regulatory norm, vendors will have to earn customer loyalty more explicitly. If not, the market may continue to reward integrated ecosystems even when they are hard to leave.

Strengths and Opportunities

The CMA’s move could produce real benefits if it succeeds in lowering lock-in and making cloud competition more transparent. It also gives Microsoft a chance to simplify parts of its licensing story and rebuild trust with enterprise buyers. In that sense, this probe is both a threat and a pressure-release valve.

More transparent licensing could reduce hidden switching costs.
Lower egress friction would strengthen customer bargaining power.
Better interoperability could support multi-cloud resilience.
Enterprise procurement would become easier to justify internally.
Smaller rivals would get a fairer shot at workload migration.
Microsoft could use the moment to clean up confusing terms.
The CMA could prove that its digital regime can work pragmatically.

Risks and Concerns

The main risk is that regulators may target the symptoms rather than the underlying structure of cloud dependency. If remedies are too narrow, they could improve the optics without meaningfully changing customer behavior. There is also a danger of overcorrection that makes enterprise licensing less flexible without actually increasing competition.

Overly broad remedies could reduce legitimate commercial flexibility.
Narrow remedies may fail to address technical switching barriers.
Compliance burden could rise without tangible customer gains.
Fragmented rules across jurisdictions may complicate procurement.
Voluntary changes may be too limited to alter market power.
The wrong remedy could discourage future infrastructure investment.
AI bundling could create new forms of lock-in if left unchecked.

Looking Ahead

The most important question now is how quickly the CMA turns scrutiny into formal action and whether it treats Microsoft’s ecosystem as a single market power problem or as a set of connected issues. The answer will determine whether the investigation becomes a landmark case or just another chapter in the long argument over cloud fairness. Either way, the focus on business software makes the stakes larger than before.
What happens next will also depend on how Microsoft responds in practice, not just in public statements. If it makes credible changes on licensing, interoperability, and switching, it may help narrow the case for harsher intervention. If those changes are seen as cosmetic, the CMA is likely to push further.
The broader market should expect three things to remain front and center: licensing neutrality, multi-cloud portability, and the competitive consequences of AI being embedded in everyday business software. Those are no longer niche regulatory concerns. They are now central questions about how the modern enterprise technology stack should work.

The CMA’s SMS process could become the main legal lever.
Microsoft’s licensing terms will stay under intense scrutiny.
AWS and Google will keep pressing the portability argument.
Enterprise customers may use the probe as negotiating leverage.
AI integration will make ecosystem power harder to separate from software power.

Microsoft has weathered regulatory pressure before, but this case is different because it targets the company’s core enterprise architecture rather than a single product line. If the CMA succeeds, it may redefine how business software giants can shape cloud competition in the UK and beyond. If it fails, the result will still tell us something important: that the next generation of competition policy may struggle to keep pace with the companies building the digital workplace itself.

Source: Exmouth Journal Microsoft to face competition watchdog probe over business software

Navigation section

Largest Cloud Providers in 2026: AWS, Azure, Google Plus the Niche Leaders

The Cloud Market Leaders​

AWS: The default reference point​

Azure: Enterprise gravity at work​

Google Cloud: Data and AI credibility​

The Strong Second Tier​

Alibaba Cloud’s regional strength​

Oracle Cloud Infrastructure and the database play​

IBM Cloud for regulated workloads​

DigitalOcean and OVHcloud in the specialist lane​

Why Market Share Still Matters​

The economics of scale​

The AI acceleration effect​

Multi-Cloud Is Now a Default Strategy​

Enterprise pragmatism​

Technical trade-offs​

Competitive Implications for Rivals​

The race for platform stickiness​

Regulatory and antitrust pressure​

How the Ranking Changes by Use Case​

Enterprise buyers​

Developers and startups​

Regional and sovereignty-driven buyers​

Strengths and Opportunities​

Risks and Concerns​

Looking Ahead​

ChatGPT

AI

Why this is not just a cloud story​

The historical backdrop​

The CMA’s Strategic Market Status Powers​

What SMS designation could change​

Why Microsoft is a special case​

Why Licensing Is the Flash Point​

The mechanics of lock-in​

Why rivals are pushing the issue​

Microsoft’s Ecosystem Advantage​

Windows, Office, Teams, and Copilot​

The AI factor​

Enterprise Customers Versus Public Sector Buyers​

Why procurement teams care​

Consumer impact is indirect​

Market and Competitive Implications​

How Microsoft may respond​

A contest over the rules of engagement​

Strengths and Opportunities​

Risks and Concerns​

Looking Ahead​

Similar threads

The Cloud Market Leaders

AWS: The default reference point

Azure: Enterprise gravity at work

Google Cloud: Data and AI credibility

The Strong Second Tier

Alibaba Cloud’s regional strength

Oracle Cloud Infrastructure and the database play

IBM Cloud for regulated workloads

DigitalOcean and OVHcloud in the specialist lane

Why Market Share Still Matters

The economics of scale

The AI acceleration effect

Multi-Cloud Is Now a Default Strategy

Enterprise pragmatism

Technical trade-offs

Competitive Implications for Rivals

The race for platform stickiness

Regulatory and antitrust pressure

How the Ranking Changes by Use Case

Enterprise buyers

Developers and startups

Regional and sovereignty-driven buyers

Strengths and Opportunities

Risks and Concerns

Looking Ahead

Why this is not just a cloud story

The historical backdrop

The CMA’s Strategic Market Status Powers

What SMS designation could change

Why Microsoft is a special case

Why Licensing Is the Flash Point

The mechanics of lock-in

Why rivals are pushing the issue

Microsoft’s Ecosystem Advantage

Windows, Office, Teams, and Copilot

The AI factor

Enterprise Customers Versus Public Sector Buyers

Why procurement teams care

Consumer impact is indirect

Market and Competitive Implications

How Microsoft may respond

A contest over the rules of engagement

Strengths and Opportunities

Risks and Concerns

Looking Ahead