Applies to Product -Dynamics 365 Lifecycle Services
What’s happening?
The client is attempting to migrate their data center from one geographical location to another and enable Azure Synapse for the data lake export process. This requires the introduction of Dataverse, which is not currently being utilized.
Reason:
The client configured their production environment without enabling Power Platform integration during the initial implementation, which restricts the addition of Dataverse to the existing production environment.
Resolution:
- Assess Requirements: Determine if the migration involves only the environments, only the Lifecycle Services (LCS) projects, or both.
- Plan the Migration: Review the availability of features in the target geography (East US) to ensure all necessary functionalities are supported and that the target geography meets data residency requirements if applicable.
- Prepare for Migration:
- Backup all data and configurations.
- Inform stakeholders about the migration plan and potential downtime.
- Use Lifecycle Services (LCS) Project Migration Manager: This tool assists in moving LCS project data between geographies.
- Environment Migration: Utilize the environment migration feature to move environments between geographies.
- Post-Migration Tasks:
- Verify that all data and configurations have been successfully migrated.
- Test the system thoroughly to ensure everything is functioning as expected.
- Re-enable Azure Synapse: After migration, re-enable Azure Synapse to synchronize data.
- Documentation Reference: Follow the documentation for prerequisites and requirements while creating the link to Dataverse, including:
- Ensure the Azure Data Storage account is created in the same Azure Active Directory (Azure AD) tenant as the Power Apps tenant.
- The storage account and Synapse workspace must be in the same region as the Power Apps environment.
- Ensure the necessary roles and permissions are assigned for access to the Azure Data Storage account.