Azure regions

Azure regions supported for e6data Serverless and In Your VPC deployments.

e6data supports the following Azure regions. Pick a region close to where your data lives to minimize cost and latency.

Generally available

These regions support both Serverless and In Your VPC deployments:

Region	Display name
eastus	East US
eastus2	East US 2
westus2	West US 2
westus3	West US 3
centralus	Central US
westeurope	West Europe
northeurope	North Europe
uksouth	UK South
southeastasia	Southeast Asia
eastasia	East Asia
australiaeast	Australia East
centralindia	Central India

Available on request

These regions can be enabled on request. Contact your e6data CSM:

Region	Display name
germanywestcentral	Germany West Central
francecentral	France Central
swedencentral	Sweden Central
switzerlandnorth	Switzerland North
uaenorth	UAE North
southafricanorth	South Africa North
koreacentral	Korea Central
japaneast	Japan East
brazilsouth	Brazil South

Considerations when choosing a region

• Data locality - pick the region where your ADLS Gen2 storage lives. Cross-region access works but adds latency and egress cost.
• Compliance - if you have data-residency requirements (GDPR, regional compliance), pick a region in the relevant geography.
• Cost - Azure prices vary by region; refer to Azure's pricing page for current rates.
• Service availability - some Azure services (e.g., specific VM SKUs) are not in every region; confirm your required compute SKU is available before committing.

Cross-region scenarios

Scenario	Supported?
Workspace and storage in same region	Yes (recommended)
Workspace in one region, catalogs in another	Yes - adds latency
Multiple workspaces, one per region	Yes
Single workspace querying across multiple regions	Yes but lower performance; consider separate workspaces per region

See also

• Azure setup
• Services and dependencies