Geo to geo migrations

We continue to open new datacenter regions for business services, and to add datacenters to existing regions.

The Geo Migration feature will allow customers to move their environments in a single tenant from one region to another. There are no user-interface changes or version changes as part of this move. In the case of an environment residing in an Microsoft 365 environment in a single tenant, moving the environment doesn't move the Microsoft 365 environment; they are separate services. Your environment will still appear in your tenant alongside the Microsoft 365 environment.

Supported environment types

Impact of migrating

Moving an environment to a different region changes your tenant to be multiregional - enabling regional features in the Dynamics 365 admin center.

The other significant change is to your organization URL. Each of the regional datacenters has a unique identifier in the URL. When your organization is moved from one regional datacenter to another this identifier will change. For example:

• South America (LATAM/SAM) = .crm2.dynamics.com
• Canada (CAN) = .crm3.dynamics.com
• Europe, Middle East, Africa (EMEA) = .crm4.dynamics.com
• Asia Pacific (APAC) = *.crm5.dynamics.com
• Australia (OCE) = *.crm6.dynamics.com
• Germany (GER) = *.crm16.dynamics.com
• Japan (JPN) = *.crm7.dynamics.com
• India (IND) = *.crm8.dynamics.com
• United Kingdom (UK) = *.crm11.dynamics.com
• United Arab Emirates (UAE) = *.crm15.dynamics.com

For example, if your existing organization URL is https://myorg.crm5.dynamics.com and you request it to be moved to Australia, the new organization URL will be https://myorg.crm6.dynamics.com.

You'll need to update any direct references to your organization URL.

See Where your data is located.

The following topics have information that could be helpful to understand the move process:

• New datacenter regions
• About Microsoft Cloud Australia
• About Microsoft Cloud Canada
• About the Microsoft Cloud Germany datacenter
• About Microsoft Cloud Japan
• About Microsoft Cloud India

Do the following steps for Power Apps, Power Automate, Microsoft Copilot Studio, Power Apps portals, and marketing before and after the migration:

For Power Apps and Power Automate:

• Any Power Apps and Power Automate flows must be manually exported prior to the date and time arranged for performing the Geo-to-Geo migration.
• We do not support the migration of customer connectors, connections, or gateways. If you have any of these components set up, they must be manually reconfigured after the migration.

For apps which are solution aware

Before the migration:

1. For apps that are solution aware, you can go to https://make.powerapps.com/, navigate to the Solutions page, and export all apps/solutions either individually or group them together into a single solution (if they're not already).
2. Once the canvas apps have been exported, delete the apps in the environment.

After the migration:

1. Select the new environment from https://make.powerapps.com/ and navigate to the Solutions page.
2. Select Import, and use the file selector to pick the packages exported from the above steps.
3. Confirm that the import was successfully completed by checking the solution contents in the target environment.

For apps which are not solution aware

Before the migration:

1. Go to https://make.powerapps.com, and then select Apps.
2. For each app that you want to move, select More Commands (…), and then select Export package (preview).
3. Fill in the details required to perform the export of the app, and then select Export. Once the export completes, a download should begin. The resulting file contains the app package that was selected.
4. Repeat these steps until all apps have been exported.

After the migration:

1. Go to https://make.powerapps.com.
2. Select the new environment from the environment picker in the upper-right.
3. Select Apps.
4. Select Import canvas app.
5. Upload the app package file.
6. Complete all of the import option selections, and then select Import.
7. Repeat these steps until all apps have been imported.

For Microsoft Copilot Studio:

• Any Microsoft Copilot Studio chatbots must be manually exported.
• Some chatbots' dependent components must be manually reconfigured during or after the migration - for example, connections, environment variables, custom connectors.

Before the migration:

1. Chatbots are solution aware. You can go to https://make.powerapps.com/, navigate to the Solutions page, and export all chatbots'solutions - either individually or group them together in a single solution. For more information, see Export and import bots using solutions.

After the migration:

1. Select the new environment from https://make.powerapps.com/, and navigate to the Solutions page.
2. Select Import, and use the file selector to pick the packages exported from the above steps.
3. Confirm that the import was successfully completed by checking the solution contents in the target environment.

For Power Apps portals (must be done for each portal in the environment(s)):

Before the migration:

1. Sign in to the environment.
2. Open the Power Apps portals admin center.
3. Reset the portal.

After the migration:

1. Sign in to the environment.
2. Open the Power Apps portals admin center.
3. Provision the portal with the same portal type and language.

For Dynamics 365 Marketing app:

The Dynamics 365 Marketing app does not support geo migration, due to component dependencies. For more information, see Manage your Dynamics 365 Marketing instances. If installed, the app must be uninstalled prior to the migration.

Before the migration:

1. Follow the Uninstall Dynamics 365 Marketing guide to uninstall Marketing app from the environment.

How the move works

You'll be provided with a list of prerequisites and post-requisites for your migration. The following table describes what Microsoft does before, during, and after your move.

We will adhere to the terms of the Microsoft Online Services Service Level Agreement for all moves.

See also