The executive brief
The decision in front of the business.
Choose a business layer: infrastructure supply, enterprise implementation or a customer-facing AI service. Each has a different buyer and qualification process.
Distinguish operational cloud capacity from services still being rolled out and infrastructure planned for later delivery.
Cloud geography is one input to compliance and resilience; organisations must still design, contract and operate their own workloads appropriately.
Evaluate supplier demand through identified packages and customers. A country-wide investment commitment is not a single available construction budget.
Policy and project context
The developments that matter.
An operating region with phased service expansion
Microsoft announced on 21 September that India South Central in Hyderabad is live as its fourth Indian cloud region, with three availability zones. Additional Azure and AI capabilities will roll out progressively. The region forms part of the company’s US$20.5-billion India commitment.
Cooling and future connectivity
Microsoft describes effectively zero water use for cooling, not an absence of every form of water use. It is also a consortium partner in the planned 3,600-km I-2SEA cable linking India, Malaysia and Singapore, targeted for service in 2029.
Workload responsibility remains with the customer
The company describes controls designed to support Indian regulatory and sovereignty requirements while expressly retaining customers’ responsibility to determine the requirements applicable to their organisations and workloads.
TLGS assessment
The commercial and operating implications.
Map the customer before mapping the opportunity
Infrastructure owners, their appointed contractors, enterprise cloud customers and software buyers procure different products. An electrical-equipment firm should not use the same pursuit strategy as a cloud-integrator or industry application provider. Build a buyer map around the budget holder and acceptance criteria for the particular service; this prevents a broad AI investment announcement from being mistaken for a direct order pipeline.
Power and facility services require lifecycle economics
Candidate infrastructure work can include electrical systems, backup arrangements, monitoring, maintenance, efficiency improvements and facility-support services where the owner commissions them. The commercial case should examine availability obligations, service response, spares, replacement cycles and the cost of interruption. A supplier’s proposition is stronger when it demonstrates how performance will be measured and maintained, rather than relying only on an equipment specification or low initial price.
Cooling claims should be translated accurately
For project evaluation, distinguish cooling technology from the facility’s wider resource footprint. Ask how power demand, maintenance, seasonal operating conditions and lifecycle cost interact with the chosen design. Sustainability analysis should use clearly defined boundaries and measurable indicators. Avoid turning a narrowly stated cooling attribute into an unsupported claim that every aspect of an AI service or data-centre operation has no environmental impact.
Enterprise deployment creates immediate advisory work
A cloud customer can begin with a workload inventory: business purpose, data classification, users, dependencies, access rights, recovery objectives and applicable obligations. Convert that inventory into procurement requirements and a migration sequence. Contract review should connect service availability, support, audit evidence, incident handling and exit arrangements. A locally hosted workload still needs an accountable operating model and controls appropriate to its use.
Resilience must be designed and tested
The existence of multiple availability zones does not, by itself, demonstrate that an individual application will recover as intended. Enterprise teams should specify failure scenarios, recovery priorities and acceptable data loss, then test the architecture and operating procedures with qualified technical teams. The resulting evidence should show what happens to customer access, dependent systems and reconciliation during an interruption, not merely confirm that infrastructure exists.
Treat the subsea cable as a separate development programme
Connectivity investment can create work in route and landing interfaces, terrestrial backhaul, permissions, network integration and maintenance, subject to the eventual package structure. The planned I-2SEA system should be tracked separately from the already operational cloud region. A prospective supplier should identify the consortium or package counterparty and the relevant procurement stage before committing pursuit expenditure; consortium participation is not a general invitation to tender.
AI startups should sell a measurable operating result
Additional infrastructure creates options for product delivery, but compute availability alone does not establish customer demand. A startup should select a bounded workflow, define performance and cost targets, secure rights to its inputs and agree human review where consequences warrant it. The commercial model should include inference costs, support, security, integration and migration options. This makes the proposition useful to an enterprise buyer beyond an initial demonstration.
From insight to action
Priorities for leadership.
Identify target buyers and work categories; prepare qualification, service-capacity and lifecycle-performance evidence rather than relying on aggregate investment figures.
Build a workload-specific operating and regulatory assessment, then align architecture, contracts, controls and recovery tests.
Develop a customer-backed pilot with measurable benefits, full delivery costs, data rights and a credible support model.
Strategic milestones
What to track next.
Follow service availability by workload, enterprise implementation decisions, separately announced infrastructure packages and cable development milestones. Track procurement, power and connectivity commitments independently of the broader investment narrative.
Reference documents
Sources and further reading.
- 1 · Company announcement
India South Central cloud region and India’s AI infrastructure ↗Microsoft · 21 September 2026Operational region, phased capabilities, cooling scope, customer responsibilities and planned I-2SEA connectivity.