This article provides the specific configuration requirements for migrating data when the source or destination is a Microsoft 365 tenant operated in China (for example, those operated by 21Vianet).
Environment Overview
Microsoft 365 instances in China are physically isolated from the global Microsoft cloud. Due to this isolation, standard global endpoints for Graph API, Exchange Web Services (EWS), and Authentication do not function with these tenants.
Supported Data Types
Most core data types are supported for migration within this environment:
- Mail, Calendar, and Contacts
- OneDrive for Business
- SharePoint Online
- Microsoft Teams (Core functionality)
Note: Services such as Planner, Forms, Stream, and Sway are typically not available in these regional tenants and are out of scope for migration.
Configuration Steps
To migrate to or from a China-based tenant, use a Custom plan in the CloudM Migrate connection settings to manually override default global endpoints.
Connection Configuration - Page 1
| Setting | Value |
|---|---|
| Plan | Custom |
| Cloud Deployment | China |
| Autodiscovery Service URL | https://partner.outlook.cn/autodiscover/autodiscover.xml |
| Direct Exchange EWS URL | https://partner.outlook.cn/EWS/Exchange.asmx |
Connection Configuration - Page 2 (Azure AD Application)
The application registration must reside within the regional Azure portal (e.g., the 21Vianet portal).
- App Registration Portal: Use portal.azure.cn. Tokens from the global Azure portal are not interchangeable with national cloud tenants.
- Creation Method: Use the CloudM PowerShell (manual) method. Ensure the China deployment option is selected within the script parameters to generate the app correctly.
Technical Considerations
Fixed Endpoints
When the China deployment option is selected, CloudM Migrate automatically routes the following fixed endpoints:
- Login URL: https://login.partner.microsoftonline.cn
- Graph API Endpoint: https://microsoftgraph.chinacloudapi.cn
Performance and Infrastructure
- Network Latency: Data transfer speeds to global destinations may be slower due to cross-border network constraints.
- Throttling: Regional instances often enforce stricter throttling policies than global Microsoft 365. Reduce migration thread counts if 429 errors occur.
- Self-Hosted Migration: It is recommended to use a Self-Hosted CloudM Migrate instance installed on an Azure VM located within the China region (e.g., Azure China North) for optimal throughput.
Pilot Migrations
Perform a small pilot batch to validate authentication and data access before commencing a full-scale migration, as API availability in these regions can differ from global environments.