Applies to Product - Dynamics 365 Lifecycle Services
What’s happening?
Customers are requesting the migration of their environments from one geographical region to another, specifically from Central US to East US or from East US to Central region.
Reason:
The migration requests are initiated due to the need for data residency compliance, client requirements, or to involve specific teams based in the target region.
Resolution:
- For migration requests, ensure the following details are collected:
- Environment Name
- Environment ID
- Project ID
- Source Region
- Target Region
- Preferred Migration Date and Time
- Raise a request with the appropriate engineering team to perform the region migration as per the guidelines provided in the relevant documentation.
- Inform the customer about the migration process, which consists of two phases:
- Pre-migration: The environment remains available for end-user use but is put into an Infrastructure Maintenance state to prepare for migration.
- Migration: The environment enters a downtime during which it is unavailable for use as resources are moved to the new region.
- Notify the customer to provide the necessary details at least 5 days before the planned downtime.
- Keep the customer updated on the status of the migration and any required actions from their side.
- If there are any questions or additional information required, schedule a call with the customer to discuss further.
- Ensure to follow up on the migration status and confirm completion with the customer.
- If the migration is completed, document the resolution and close the case.
- If any issues arise during the migration, escalate to the appropriate team for further assistance.
- For any additional inquiries or follow-ups, maintain communication with the customer to ensure their needs are met.