Applies to Product - Dynamics 365 Lifecycle Services
What’s happening?
Assistance is required for the geo-to-geo migration process of Dynamics 365 Finance and Operations (F&O) and Customer Relationship Management (CRM) databases from one region to another, specifically from Europe to the UAE region.
Reason:
- The endpoint will change as it is defined based on data residency in specific geographies, resulting in a different URL for the new geographic location.
- The Azure Entra ID tenant ID will remain unchanged during the migration process.
Resolution:
- Endpoint Change: Confirm that the endpoint will change due to the migration to a different geographic location.
- Cost of Migration: There are no costs associated with migrating to a different geo location.
- Attachments in F&O:
- If attachments are stored in Azure blob storage, they should migrate normally.
- If attachments are stored in other locations (e.g., SharePoint), ensure to take backups before migration and import them again post-migration.
- Attachments in CRM: Information regarding the migration of attachments in CRM is being verified internally.
- Microservices Identification: Identify any microservices (add-ins) used in F&O (e.g., Financial Reporting Add-in, Azure Synapse) and remove them before proceeding with the migration.
- Downtime: Allocate a total downtime window of 34 hours, which includes a 24-hour lead time plus 6 hours for the migration process.
- LCS Region Check: The LCS region can be checked from the top right corner of the LCS page.