★★★★★ 4.5 CE

Microsoft Azure Regions, Deployment & Data Residency 2026

Azure runs 70+ regions with Container Apps in 55+, the widest footprint of any cloud. Each environment is single-region, so multi-region needs Front Door.

Cloud HostingVerified today

Full review Pricing Official site ↗

Microsoft Azure Regions & Deployment verdict

Verified today·7 sources checked

Azure carries the widest region footprint of any cloud.

70+ regions across 30+ geographies, including sovereign and government clouds, with Container Apps in 55+ of them. The unit of deployment is the environment, and each one is single-region.

How to pick your regions

Two settings you cannot undo shape this. Zone redundancy has to be turned on when you create the environment, never after, so decide before provisioning. A single environment also cannot survive its region failing. Past that, pick a region near your users. For EU residency Azure has the widest choice, from West and North Europe through Germany, France, Sweden, Spain. For region-failure resilience, run an environment per region and front them with Azure Front Door. Enable zone redundancy at creation for the higher SLA.

Honest limits

A Container Apps environment is single-region. A regional outage takes the environment and all its apps down, so multi-region needs Front Door or Traffic Manager.
Zone redundancy must be enabled at environment creation and cannot be added later. Container Apps also has no vertical scaling, so size replicas before deploying.
Specific SLA percentages live in the master Microsoft Online Services SLA, not on the docs page.

Azure regions: 70+
Container Apps regions: 55+
EU regions: 20+
Environment scope: Single-region
Zone redundancy: At creation

View sources

This page covers where Azure deploys and how residency works. Performance and pricing live on their own pages.

Pick your Microsoft Azure region and deployment

Region and deployment planner

Target region

North AmericaDefault region

15 regions across 5 continents · nearest failover West US 3 · residency: North, West, Germany +2

Create a zone-redundant Container Apps environment in East US.

bash

az containerapp env create \
  --name my-env \
  --resource-group my-rg \
  --location East US \
  --zone-redundant

A Container Apps environment is single-region; for multi-region deploy an environment per region behind Azure Front Door. Zone redundancy must be set at environment creation. The nearest region above is a placement hint.

Real Microsoft Azure regions and deployment commands. Confirm residency guarantees against your contract.

Deploy Azure: Container Apps YAML, ARM and the CLI

Used with az containerapp create --yaml. The template defines the container image and resources (cpu/memory), ingress, and the scale block: minReplicas (0 for scale-to-zero), maxReplicas and a KEDA http rule with concurrentRequests. The environmentId ties the app to its regional, optionally zone-redundant environment.

containerapp.yamlyaml

properties:
  environmentId: /subscriptions/<sub>/resourceGroups/rg/providers/Microsoft.App/managedEnvironments/demo
  configuration:
    ingress:
      external: true
      targetPort: 3000
  template:
    containers:
      - image: repo/myapp:v1
        name: myapp
        resources:
          cpu: 0.5
          memory: 1Gi
    scale:
      minReplicas: 1        # 0 = scale to zero
      maxReplicas: 10
      rules:
        - name: httpscalingrule
          custom:
            type: http
            metadata:
              concurrentRequests: '100'

Create the regional environment first (with --zone-redundant for the higher SLA), then the app with an HTTP scale rule. --min-replicas 0 scales to zero; --scale-rule-http-concurrency sets the per-replica concurrent-request target.

Azure CLIbash

# Create a regional, zone-redundant environment
az containerapp env create \
  --name my-env \
  --resource-group my-rg \
  --location __REGION__ \
  --zone-redundant

# Deploy the app with HTTP autoscaling
az containerapp create \
  --name my-app \
  --resource-group my-rg \
  --environment my-env \
  --image repo/myapp:v1 \
  --min-replicas 0 \
  --max-replicas 5 \
  --scale-rule-name http-rule \
  --scale-rule-type http \
  --scale-rule-http-concurrency 100

The managed environment is the regional unit. location pins the region, zoneRedundant: true spreads it across availability zones (immutable after creation), and workloadProfiles defines Consumption, GeneralPurpose (Dedicated) and MemoryOptimized capacity.

ARM environment (JSON)json

{
  "location": "__REGION__",
  "properties": {
    "zoneRedundant": true,
    "workloadProfiles": [
      { "name": "consumption", "workloadProfileType": "Consumption" },
      { "name": "gp1", "workloadProfileType": "GeneralPurpose",
        "minimumCount": 3, "maximumCount": 12 }
    ]
  }
}

Container Apps regions

Region	Location	Continent
East US	Virginia, USA	North America
West US 3	Arizona, USA	North America
Central US	Iowa, USA	North America
Canada Central	Toronto, Canada	North America
Brazil South	Sao Paulo, Brazil	South America
North Europe	Ireland	Europe
West Europe	Netherlands	Europe
Germany West Central	Frankfurt, Germany	Europe
France Central	Paris, France	Europe
UK South	London, UK	Europe
Sweden Central	Gavle, Sweden	Europe
Central India	Pune, India	Asia
Southeast Asia	Singapore	Asia
Japan East	Tokyo, Japan	Asia
Australia East	Sydney, Australia	Oceania

Microsoft Azure footprint and region selection

Aspect	Value	Notes
Azure footprint	70+ regions	Across 30+ geographies, including sovereign
Container Apps reach	55+ regions	Consumption in all supported regions
Environment scope	Single region	Region down = environment and apps down
Multi-region	Front Door / Traffic Manager	Deploy environments per region and load-balance
Zone redundancy	Set at env creation	Across availability zones; immutable
Sovereign / gov	China, US Gov, sovereign EU	Separate sovereign regions

Microsoft Azure data residency and regions

Control	Option	Notes
EU regions	20+ European	North/West Europe, Germany, France, Sweden, Norway, Switzerland, Spain, Poland, Italy, Denmark, Belgium, Austria, Finland, Greece
Sovereign clouds	China, Germany sovereign	Operated separately for sovereignty
Zone redundancy	Across availability zones	Physically separate zones within a region
Government regions	US Gov, DoD, Sec	For US public sector
Data scope	Regional environment	App and data live in the environment's region

What to verify before you commit to Microsoft Azure

A Container Apps environment is single-region, and if that region goes down the environment and all its apps go with it, so multi-region resilience means deploying an environment per region behind Azure Front Door or Traffic Manager
Zone redundancy must be enabled when the environment is created and cannot be turned on later, so decide before you provision
Specific SLA percentages are not on the reliability page; they live in the master Microsoft Online Services SLA, and zone redundancy increases the guaranteed uptime
Container Apps has no vertical scaling, so size the replica's CPU and memory correctly up front and rely on horizontal replica scaling

Microsoft Azure Regions & Deployment FAQ

How many regions does Azure have?

More than 70 regions across 30+ geographies, the largest footprint of any cloud, including sovereign clouds like China and sovereign Germany, plus US government regions for Gov, DoD, Sec workloads. Container Apps is available in 55+ of them, while App Service and VMs reach more. EU coverage is the deepest of any provider, at 20+ European regions.

Is Azure Container Apps multi-region?

No, an environment is single-region. If its region becomes unavailable, the environment and every app inside it go down too. For multi-region resilience you create a Container Apps environment in each region and put Azure Front Door or Traffic Manager in front for load balancing and failover. There is no single multi-region environment object.

Does Azure support EU data residency?

Extensively, more than any other cloud. Container Apps covers North Europe in Ireland and West Europe in the Netherlands. The list continues with Germany West Central, France Central, Sweden Central, Norway, Switzerland, Spain, Poland, Italy, Denmark, Belgium, Austria, Finland. Azure also runs sovereign clouds, sovereign Germany among them, and zone redundancy keeps data inside a region across availability zones.

What is zone redundancy in Container Apps?

It spreads a Container Apps environment across physically separate availability zones inside a region, raising the uptime the SLA guarantees. It is available in every region that has availability zones, and applies to both Consumption and Dedicated profiles. The catch is timing: you must enable it when you create the environment, because it cannot be turned on afterward.

How do I deploy and pin a region on Container Apps?

Create the environment in the region first with az containerapp env create --location <region> --zone-redundant. Then deploy the app into it using az containerapp create --environment <env> ... --min-replicas 0 --scale-rule-http-concurrency 100, or apply a YAML or ARM template. The app inherits the environment's region, so another region means another environment.

Sources & verification

Verified by ComparEdgeMethod: Vendor docs, official pages, and selected independent sources

Source	What was checked	Last checked
Microsoft Official	Official product page	July 10, 2026
Microsoft Details Container Apps	Details Container Apps	July 10, 2026
Microsoft Global Infrastructure Geographies	Global Infrastructure Geographies	July 10, 2026
Microsoft Learn	Container Apps Azure Resource Manager API Spec	July 10, 2026
Microsoft Learn	Container Apps Scale App	July 10, 2026
Microsoft Learn	Container Apps Workload Profiles Overview	July 10, 2026
Microsoft Learn	Reliability Reliability Container Apps	July 10, 2026

Every fact on this Microsoft Azure page is tied to a named source and a verification date. Freshness-sensitive figures trace to the sources above; verify against the vendor before relying on them.