Views:

Applies to Product -Dynamics 365 Lifecycle Services


What’s happening?
Customers are requesting to migrate their Finance and Operations (F&O) instances to a new Microsoft Entra tenant to address various business challenges.


Reason:
The migration process requires specific steps to ensure that the instances are successfully transferred from the old tenant to the new tenant, including the activation of subscriptions and configuration of Lifecycle Services.


Resolution:

  1. Activate subscriptions on the new tenant: The customer should work with their cloud service provider or volume license reseller to activate the subscriptions against the new Microsoft Entra tenant. All subscriptions for users and for add-on environments must be activated.
  2. Configure Lifecycle Services on the new tenant: The customer and partner will create a new Lifecycle Services project that must be initiated and set up.
  3. Move sandbox environments to the new tenant: The customer and partner will deploy and perform testing with the non-production environments in the new Lifecycle Services project.
  4. Move the production environment to the new tenant:
  5. The customer needs to send an email to Dynamics 365 FO Go-Live stating that the new Lifecycle Services project is ready for Microsoft to move the production database and Azure Blob Storage.
  6. When the tenant move assessment is successfully completed, the FastTrack team will enable the Production environment slot in Lifecycle Services to deploy.
  7. After the production environment has been deployed, verify that the source and target environments have exactly the same code; otherwise, migration will fail. If necessary, deployable packages must be installed on the target production environment.
  8. Reimport users and validate the new production environment: After Microsoft has completed the tenant migration activity, the customer needs to reimport all users from the new Microsoft Entra tenant and validate the new production environment to ensure that all business processes are successful. If any issues are encountered after the migration, a support ticket should be filed.
  9. Delete the Lifecycle Services project on the old tenant and suspend subscriptions:
  10. The customer and partner will delete the old Lifecycle Services project and work with their cloud service provider or Volume Licensing Support to suspend all licenses on the old Microsoft Entra tenant.
  11. For the cloud service provider, suspend the existing subscriptions against the old tenant. For Volume Licensing Support, confirm that the work is completed and that the subscriptions can now be suspended against the old tenant.
For more detailed guidance, refer to the documentation: Move Lifecycle Services implementation projects to different Microsoft Entra tenants - Finance & Operations | Dynamics 365 | Microsoft Learn.