Edit

Power Platform and Dynamics 365 macro regions

A macro region represents the data residency boundary that aligns with data residency laws for a given geography. This article lists the regions available in a specific macro region.

The macro region enhancement to environment provisioning enables you to select a macro region during environment creation. This feature applies to public cloud only and is being introduced for tenants in the Canada region.

Customers select a macro region, such as North America, Europe, or Asia-Pacific instead of a specific geography. The platform then automatically assigns the optimal region within the selected macro region based on capacity, availability, and performance considerations. This approach helps ensure a more scalable, resilient, and performant experience for all customers while continuing to respect data residency commitments. The intelligent region selection ensures environments are placed in regions with optimal capacity and health, improving uptime and responsiveness.

Using a macro region provides the following capabilities:

  • As your workloads grow, the platform dynamically places environments in geographies best suited to handle demand at scale, without manual intervention.
  • You no longer need to evaluate and select individual geographies, simplifying environment creation while still maintaining regional control.
  • Microsoft can continuously optimize backend infrastructure, ensuring you benefit from ongoing investments in new regions, capacity, and resiliency.
  • You still control where your data resides at a regional level, ensuring alignment with business, compliance, and regulatory requirements.

Expected changes in your provisioning experience with a macro region

  • For a new tenant that doesn't yet meet geo-selection eligibility criteria, you only see the macro region—given that a macro region is supported for the geography—at the time of new environment creation. You don't see the individual regions. New is associated with creation of the first Power Platform environment for the tenant.
  • Customers see their macro region and region in the environment properties and in the environment list.
  • A macro region is a continental residency boundary, for example, the European Union Data Boundary (EUDB), while a region represents the country for deployment for clarity.
  • The system automatically determines the region within that macro region geography by using capacity-based routing, performance, and availability.
  • Customers continue to see their data location (region) transparently after provisioning.
  • Existing tenants remain unchanged and retain their current region selection capabilities.

Macro region geography

The following table describes each macro region.

# Macro region geography Regions Description
1 North America United States, Canada Your data resides within the United States or Canada.
2 The Americas United States, Canada, Brazil Your data resides within the Americas, including North and South America.
3 European Union (EU) and European Free Trade Association (EFTA) France, Germany, Norway, Sweden, Switzerland, Poland, Italy, Ireland, Netherlands Your data resides within EU and EFTA member states which are European Union Data Boundary (EUDB) regions.
4 Europe and United Kingdom (UK) UK, France, Germany, Norway, Sweden, Switzerland, Poland, Italy, Ireland, Netherlands Your data resides within EU and EFTA or the UK and it shouldn't be considered EUDB.
5 Europe, UK, Middle East, Africa UK, France, Germany, Norway, Sweden, Switzerland, Poland, Italy, Ireland, Netherlands, South Africa, United Arab Emirates (UAE) Your data resides within Europe, UK, Middle East, or Africa.
6 Asia-Pacific Singapore, Australia*, India*, Japan, South Korea Your data resides within the Asia-Pacific region.

* Australia and India geographies have tax restrictions and need data residency alignment and accountability for compliance with local tax reporting rules and for auditability within jurisdiction.

Note

Sovereign clouds like the Government Community Cloud (GCC), Government Community Cloud - High (GCC-H), and Department of Defense (DoD) aren't supported.

Geo-selection eligibility criteria

Customers who meet the criteria can select a specific region during environment creation. Qualifying criteria include any one of the following characteristics:

  • Advanced data residency is enabled for Microsoft 365 in this tenant.
  • High-deployment workloads, such as 100 or more paid Dynamics 365 licenses or 1 TB or more of Dataverse storage.
  • Premium Dynamics 365 workloads, such as Finance or Supply Chain Management with 20 or more paid licenses.
  • Premium Power Platform workloads, such as Power Apps or Power Automate with 5,000 or more paid licenses.
  • Specialized workloads, for example Contact Center.

This criteria ensures customers with region control requirements for regional residency can continue operating with full flexibility.

As tenants mature and begin to meet one of the geo-selection eligibility criteria, the auto Upgrade Enablement feature enables the ability at the tenant-level to select a specific region during environment creation going forward.

Data residency and compliance

  • Data always resides within the selected macro region boundary.
  • Where applicable, compliance constructs, such as the EUDB, are preserved and clearly communicated.
  • The platform doesn't expand residency guarantees beyond contractual commitments.

Customer experience example

Assume that a customer selects Europe and UK as the macro region. The platform then assigns a geography, such as Germany or Italy, based on capacity and availability. The customer can view the assigned region after provisioning.

If the customer requires region selection, such as France, they can qualify for premium criteria or engage with Microsoft support for exception handling.

Continuity for existing customers

There's no impact to existing environments or tenants. Existing customers retain current region selections and continue to have access to geo-based provisioning like they always have, ensuring a non-disruptive rollout while enabling a modern provisioning model for future environments.