Data residency for GCC — Azure Central India / Mumbai / Singapore.it.decisions.d12

P0 GCC

Summary

Latency + compliance. Decision owner (sheet): Data Lead + Legal. Sheet target: Wk 2.

Rationale prompt skeleton

Capture the rationale for this decision. Sheet-recorded justification: "Latency + compliance.". Reference the evidence questions, name the alternatives considered, and explain how this decision propagates to design, BoM, and operating model.

Default options (3)

azure_central_india Azure Central India (Pune)

India-region cloud for GCC analytics workloads.

Pros

+ Lowest latency for Chennai
+ India residency

Cons

− Azure-only

azure_mumbai Azure South India / Mumbai

Alternative India region.

Pros

+ India residency

Cons

− Slightly higher latency from Chennai

singapore Singapore

Regional hub option.

Pros

+ Strong connectivity to Middle East

Cons

− India PDPL cross-border review
− Higher latency to KSA than India region

Default approval chain

Admin
ExecutiveViewer

Linked evidence questions (2)

id	prompt	workstream
it.applications_data.q09	Data residency for HR/finance data — KSA, India, EU, multi-region? Cross-border-transfer permissibility documented?	it.applications_data
it.gcc_context.q06	Snowflake (or DW) residency — Azure Central India / Mumbai / Singapore for GCC analytics? Cross-border transfer rules.	it.gcc_context