Modifica

Move an Environment to another Azure Active Directory organization

  • Articolo

In some cases, the Azure Active Directory (Azure AD) organization (also known as the Azure AD tenant) of a Business Central customer changes after they acquire a Business Central environment. This situation can occur for various reasons, such as the following:

  • Business entities merge.
  • An acquisition takes place.
  • The customer decides to use one Azure AD tenant in a specific region and stop using Azure AD tenants they created in other regions.
  • The environment was mistakenly created by the reselling partner for the wrong Azure AD tenant.

In all such cases, the customers want to preserve the Business Central environments they created for the original Azure AD tenants, and link them to the new ones instead. Microsoft Support can move an environment from one Azure AD tenant to another, based on a support request.

Request to move an environment

As a partner, you can submit a support request to Microsoft Support by following the guidance at Escalating support issues to Microsoft. When submitting these support requests, you must provide the following information:

  • Proof of your delegated admin rights in both Azure AD tenants
  • Confirmation from the customer that the environment move is authorized by them

You can request to move one or more environments. For Microsoft to do the move, you'll need to provide information about the source and destination Azure AD tenants, such as:

  • Environments name, type and country
  • Source tenant ID and domain
  • Destination tenant ID and domain
  • Does the destination tenant have a valid Business Central subscription?
  • Does the destination tenant have enough available user licenses?
  • Does the destination tenant have enough environment licenses?
  • Does the destination tenant have enough storage available for the environments being migrated?

Once the move is completed, your environments will appear in your new tenant.

Considerations

  • Environment data will remain unchanged during the move operation. The exact same environment will be linked to a specified Azure AD tenant.
  • The country, 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 moved (typically not exceeding 2 hours). So the operation needs to be coordinated with the customer and Microsoft Support.
  • Business Central Support doesn't provide help with moving the Business Central subscriptions, domains, and other resources between the Azure AD tenants. Your support representative or account manager will assist you in contacting billing to cancel or credit your previous subscription, if needed.

Before you request your environment to be moved

  • If you don't have a Business Central subscription (paid or trial) in the destination tenant, you'll need to create one. You might need to purchase a new subscription in the destination tenant (or convert a trial to paid), if not already done.
  • Make sure the destination tenant meets the following requirements:
    • It has at least as many active user licenses as the source tenant.
    • It has enough Business Central environment add-on licenses to cover the environments being moved
    • It has at least as much Business Central storage as the source tenant.

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 Azure AD tenant. If so, these users won't be migrated to the new Azure AD 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 Azure AD 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.

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