Édition

Partage via

Transfer environments

  • Article

Environments can be transferred between Microsoft Entra tenants, for example when multiple Entra tenants are consolidated, when a business is acquired by or merging with another business, or when a partner prepares a demo environment in their tenant that needs to be transferred to the customer tenant for the customer to evaluate.

About transferring environments

An environment transfer is initiated by an internal administrator in the Business Central administration center for the source tenant and must be accepted by an internal administrator in the Business Central administration center for the destination tenant before the transfer will execute. Once the transfer starts, all users in the source tenant will be disconnected and the environment will no longer be available in the source tenant. There is some post-transfer setup required in the environment from the destination tenant before the environment can be used again, so plan the environment transfer carefully to avoid unneccessary downtime.

Important

All environment transfer operations must be executed by internal administrators; this feature cannot be used by delegated administrators.

Create transfer on source tenant

  1. Authenicated as an internal administrator, navigate to the Business Central administration center in the source Entra tenant
  2. In the navigation pane of the Business Central administration center, select Environments > Environment Transfers
  3. Select Transfer Environments
  4. Select the environment(s) to be transferred, specify the Entra tenant ID of the destination tenant, choose a date and time at which the chosen environment(s) should transfer to the destination, and confirm

After creating a transfer on the source tenant you can review the status on the Pending outgoing transfers list.

Important

An environment transfer must be accepted in the destination Entra tenant within 8 hours of creating the transfer on the source tenant. If you specify a time when initiating a transfer on the source tenant the transfer will not start before the chosen time even if the transfer is accepted on the destination tenant before the chosen time. If the transfer is accepted on the destination tenant after the time chosen on the source tenant the transfer will run immediately upon acceptance in the destination tenant. If a transfer is not accepted in the destination tenant within 8 hours of creating the request in the source tenant the created operation will have status 'Skipped' on the Operations page in the Business Central administration center.

Transfer requests are valid for two weeks if accepted on the destination tenant within 8 hours; it is not possible to choose a date and time on the source tenant that is more than two weeks in the future.

Accept transfer on destination tenant

To confirm the transfer it has to be accepted on the destination tenant within 8 hours of creating the request on the source tenant.

  1. Ensure the destination tenant has at least one paid user license and sufficient environment and storage quota available to receive the new environments
  2. Authenicated as an internal administrator, navigate to the Business Central administration center in the source Entra tenant
  3. In the navigation pane of the Business Central administration center, select Environments > Transfer Environments
  4. Select Receive Environments
  5. Specify the Entra tenant ID of the source tenant you're accepting an environment transfer from
  6. Select the environment(s) for which you want to accept a transfer and confirm. If a selected environment has a name that already exists in the destination tenant you will be prompted to enter a new name to avoid duplicate environment names. If you are prompted to rename multiple selected environments, you must enter unique names for each selected environment.
  7. Accepted environments with a transfer time set when the request was created in the source tenant that is in the past will transfer immediately; environments with a transfer time in the future will transfer at the specified time.

Important

You can only transfer environments if you have environment quota available for the environments you're transferring in the destination tenant and if the destination tenant has at least one paid user license. Ensure there is sufficient available environment quota before accepting a transfer.

If a transfer is scheduled to take place at a time in the future you must ensure that the destination tenant has environment quota available at the time for which the transfer is scheduled; accepting a transfer does not reserve the quota for the accepted environment(s) and the transfer will fail if environment quota is no longer available when the transfer starts.

Cancel a pending transfer from source tenant

  1. Authenicated as an internal administrator, navigate to the Business Central administration center in the source Entra tenant
  2. In the navigation pane of the Business Central administration center, select Environments > Transfer Environments
  3. Select the pending outgoing transfers which you would like to cancel and confirm

Important

Pending transfers can be cancelled by internal administrators until the transfer starts, i.e. as long as the transfer has not been accepted on the destination tenant or the scheduled time for the transfer is in the future.

After the environment has been moved

  • Users may have been added to the environment prior to the move operation, while it was still connected to the old Microsoft Entra tenant. If so, these users won't be migrated to the new Microsoft Entra tenant. You'll need to recreate the users on the target tenant if you still want them. You can add multiple user accounts at once using Excel spreadsheet or other file saved in CSV format. After the users are created on the target Microsoft Entra tenant, assign them the required roles or licenses and import these users into the moved environment.

    Note

    User personalizations will be lost.

  • You might need to reconfigure some add-ins, external applications, and settings after the tenant-to-tenant migration. Some examples include the Business Central Outlook add-in, Excel add-in, Power BI, Power Apps, Power Automate connectors, Dataverse, user personalizations, and more.

  • External integrations may have to be updated to reflect the new environment url, including the new Entra Tenant ID.

Transfer auditing

Environment transfers create two distinct operations that can be audited on the Operations page in the Business Central administration center. The Transfer Request operation is created upon initiating a transfer in the source tenant and is only visible in the source tenant. The Transfer operation is created once a transfer is accepted in the destination tenant and lives in the tenant where the environment is located; before the transfer is executed this operation can be found in the source tenant, and after the environment has transferred the operation can be found in the destination tenant.

Telemetry signals for the environment transfer operation are emitted to the Application Insights resource to which the environment that is transferred is emitting telemetry. Signals related to this operation are emitted from the moment a transfer is accepted on the destination tenant, see Environment Lifecycle Telemetry.

Considerations

  • Environment data will remain unchanged during the move operation. The exact same environment will be linked to a specified Microsoft Entra tenant.
  • The localization, Azure region, and type of the environment (Production or Sandbox) will remain the same, and can't be changed during this operation.
  • The operation will involve a downtime period for the environment being transferred (typically not exceeding 30 minutes).
  • The operation does not move subscriptions, domains, and other resources between the Microsoft Entra tenants. Ensure the destination tenant has a paid Business Central user subscription and sufficient environment quota before accepting the transfer.
  • If you rename an environment upon acceptance in the destination tenant to avoid duplicate environment names in your tenant no Rename operation will be created on the Operations page in the Admin Center. Rather, the Transfer Operation will include the source and destination environment names.
  • Environment settings are carried over from the source to the destination tenant. Depending on the nature of the environment transfer settings such as the Application Insights Connection String set up on the environment may need to be changed or removed.
  • Environments that are linked to a Power Platform environment cannot be transferred. Unlink the Business Central environment before creating a transfer on the source tenant.

See also

Managing Tenant Notifications Managing Apps Updating Environments Rename Environments Restoring an Environment Managing Production and Sandbox Environments The Business Central Administration Center Introduction to automation APIs