Skip to main content

Transfer #msdyn365bc environment between Tenant.

Hi Readers,

Moving Environment between tenant is something that some customers and partners are looking for. 

In this article we will discuss about How to Transfer Business Central Environment between Microsoft Tenants.

Create transfer on source tenant.

  • Business Central administration center, select Environments > Environment Transfers.
  • Select Transfer Environments.
  • 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.
  • An environment transfer must be accepted in the destination Entra tenant within 8 hours of creating the transfer on the source tenant.

Accept transfer on destination tenant.

  • Business Central administration center, select Environments > Transfer Environments.
  • Select Receive Environments.
  • Specify the Entra tenant ID of the source tenant you're accepting an environment transfer from
  • Select the environment(s) for which you want to accept a transfer and confirm.

Cancel a pending transfer from source tenant.

  • Business Central administration center, select Environments > Transfer Environments.
  • Select the pending outgoing transfers which you would like to cancel and confirm.

Considerations

  • only Internal Administrators can execute and accept Transfer request. 
  • Max time 8 Hours to Accept Request.
  • Downtime period typically 30 Minutes.
  • Localization, Azure region, and type of the environment will remain the same, and can't be changed during this operation.
  • Need to reconfigure some add-ins, external applications, and settings after the tenant-to-tenant migration.
  • External integrations may have to be updated.
  • User personalization's will be lost.

Demo Video:



Let me know your views in comment to this article.

Regards,
Saurav Dhyani
www.sauravdhyani.com

Comments

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.

🚀 Exploring Vibe Coding with GitHub Copilot for Business Central.

Hi All, In a recent #BCOpenDiscussion session, we delved into the fascinating concept of Vibe Coding —a new way of building software where developers collaborate with AI (like GitHub Copilot) to co-create solutions.  The session covered practical setup, how AI understands context, and even touched on Microsoft's new Model Context Protocol (MCP) integration for enhanced learning. Let’s break down the journey, step by step.