Applies to Product – Dynamics 365 Lifecycle Services
What’s happening?
Customers may encounter challenges when attempting to migrate their environments from one tenant to another, specifically regarding the migration of UAT (User Acceptance Testing) environments and ensuring minimal downtime.
Reason:
The migration process requires specific prerequisites and steps to be followed to ensure a successful transition. This includes the need for a minimum downtime period and the creation of deployable packages that match the source production environment.
Resolution:
- Preparation for Migration:
- Confirm the details of the environment to be migrated, including the current UAT region and the target region.
- Ensure that all prerequisites are met before proceeding with the migration.
- Downtime Requirements:
- Schedule a minimum of 48 hours of downtime for both the source and target environments.
- Provide at least 24 hours of lead time between when the migration request is created and when the downtime is scheduled to begin.
- Deployment Steps:
- Create a single deployable package that matches the source production environment.
- Deploy this package into the target sandbox environment.
- Apply the same deployable package to the target production environment.
- Ensure that all customized packages are applied before the migration starts.
- Documentation Reference:
- Refer to the public documentation for detailed guidance on the migration process:
- "Move Lifecycle Services implementation projects to different Microsoft Entra tenants - Finance & Operations | Dynamics 365 | Microsoft Learn"
- "Finance and operations apps environment migration - Finance & Operations | Dynamics 365 | Microsoft Learn"
- Follow-Up:
- After the migration, confirm with the customer that the process was successful and that no further issues are pending.