A complete regional hub arrives in one announcement

Microsoft's fourth Azure region in India, India South Central, went generally available on 6 August 2026 in Hyderabad, Telangana, built with three availability zones. It joins existing regions in Pune, Chennai and Mumbai, plus two partnership datacenters run with Reliance Jio, making Hyderabad Microsoft's largest single India hub to date.

Four enterprise customers are already live rather than promised: Adani Group, HDFC Bank, Bajaj Finserv and PB Pay. Microsoft describes the site's cooling as enhanced mechanical cooling with air-cooled chillers, part of what it calls next-generation datacenters that consume zero water for cooling.

20.5 billion dollars and paying customers on day one

The region sits inside a cumulative $20.5 billion commitment to India's cloud and AI infrastructure, built from a $3 billion pledge in January 2025 and a further $17.5 billion announced in December 2025. Microsoft has paired the capital with a skilling pledge: 20 million Indians trained in AI by 2030, with 5.6 million reached since January 2025 and more than 125,000 already moved into jobs or entrepreneurship.

Having Adani Group, HDFC Bank, Bajaj Finserv and PB Pay signed and running at general availability, rather than named as future prospects, is the detail that separates this from a speculative build: it gives Microsoft day-one utilization and gives Indian regulators and customers a working reference for data residency claims before the marketing settles.

What Microsoft actually built for the EU is a legal boundary, not a hub

Microsoft's closest EU equivalent, the EU Data Boundary, was first announced in December 2022. Phase 1 launched in January 2023, Phase 2 followed in January 2024 covering pseudonymized personal data, and Phase 3, covering professional-services data such as support logs and case notes, only reached completion on 26 February 2025. The finished boundary covers Microsoft 365, Dynamics 365, Power Platform and most Azure services.

Microsoft's own announcement of that milestone carries a carve-out: in limited security instances that require a coordinated global response, essential data may still be transferred outside the EU. Completion, in other words, delivered GDPR-adjacent residency for support data, not full data localization and not immunity from US jurisdiction.

Microsoft's own critics call it sovereignty washing

A follow-up announcement in November 2025 promised in-country Microsoft 365 Copilot processing across 15 countries, but only four, the UK, Australia, India and Japan, had it by the end of 2025; Germany, Sweden, the UAE and South Africa are due to follow only in 2026. The same update scaled Azure Local from 16 to a promised hundreds of physical servers and brought Microsoft 365 Local to general availability in connected mode only, with a fully disconnected option pushed to early 2026.

Civo chief executive Mark Boost said putting a data centre in Paris or London means little if the company behind it is still governed by US law. Nextcloud founder Frank Karlitschek called the package sovereignty washing, arguing only open-source software removes the underlying vendor dependency. OpenInfra Foundation's Thierry Carrez put it more cautiously: whether the mix of measures proves sufficient is, in his words, unsure and untested.

The benchmark EU and UK buyers should hold Microsoft to

The two projects are not engineering twins. Hyderabad is a greenfield physical region; the EU sovereignty push retrofits legal and operational controls onto more than a dozen regions that were already mature. That difference matters, but it is not the fair test.

The fair test is completeness and pace when a market matters enough to Microsoft: India got a hard date, an environmental commitment, real capacity and paying anchor customers inside a single announcement. EU and UK buyers weighing sovereign-cloud claims for procurement or compliance, and the policymakers who take Microsoft's commitments at face value, now have grounds to ask why Europe still gets a rolling list of future phases instead of a comparable package delivered at once.