Applies to Product -Dynamics 365 Lifecycle Services
What’s happening?
Customers have questions regarding the tenant migration process, specifically how it works and whether other applications in different regions, such as Power BI, will be affected.
Reason:
The tenant migration process involves moving all data from an old tenant to a new tenant, including databases and storage components. There are considerations regarding downtime, lead time, and potential impacts on third-party integrations and applications.
Resolution:
- Preparation and Lead Time:
- Provide at least 24 hours of lead time between when the support ticket is created and when the downtime is scheduled to begin.
- Downtime Requirements:
- A minimum of 48 hours of downtime is required for both source and target environments.
- Migration Steps:
- The customer must 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 all customized packages are applied before the migration starts.
- Considerations for Third-Party Applications:
- Any third-party integrations using the environment endpoint will require changes if the migration crosses data resident geographies.
- Post-migration, reconfiguration of third-party integrations and add-ins may be necessary.
- Power BI Integration:
- For Power BI integration, specific steps must be followed post-migration to ensure continued functionality.
- Estimated Timeline:
- Total estimated time for the migration process is approximately 154 hours (about 6.5 days), which includes preparation, downtime, database copying, manual SQL operations, validation, and reconfiguration.
- Documentation Reference:
- For more detailed information, refer to the relevant Microsoft documentation on tenant migration and Power BI integration.