Bring site, application and provider owners together before choosing a move date. For an APAC programme, including China, Hong Kong and India, separate equipment handling, installation, workload migration and network connectivity. Check each location’s dependencies and agree the change, recovery and acceptance decisions across the full route.
Establish readiness at both ends
Confirm racks, power, cooling, access and provider arrangements at the origin and destination. Give each dependency an owner. Equipment packing and transport require their own scope, while applications need a migration and validation plan.
Build the change around business dependencies
List which identity, storage and network services each application needs. Agree interruption limits, shutdown order and decision points. If a prerequisite is late, the plan should identify who can defer the move or approve an alternative.
Check the destination environment independently
Cloud accounts and services should be checked for the chosen environment. Microsoft describes Azure in China as a separated, independently operated instance. Use current provider documentation rather than assuming a global account or design transfers unchanged.
Technical reference
Microsoft Azure in China operations overview: learn.microsoft.com This reference concerns the cloud environment, not approval of equipment transport or Express capabilities.
Does the transport plan cover application migration?
No. List migration tasks, owners and acceptance separately.
When should the date be confirmed?
After assessing the critical site and provider dependencies, with change approval and contingency decisions recorded.