If your service supports multiple regions, you may be able to move it from its current region to another one directly from the client area.
Region migration is designed for customers who want to relocate service placement without ordering a new service. The destination is still chosen according to current platform capacity and operational policy.
1. When You Can Use Region Migration
You can use region migration only when all of the following are true:
- Your product has region migration enabled.
- Your service is assigned to a region-aware plan.
- At least one destination region is currently available.
- Your migration request is allowed by the platform's current migration quota and policy.
2. Before You Start
- Review the current region shown on your service overview page.
- Make sure you actually need to change regions, because migration is an operational action rather than a cosmetic setting.
- If you are using BYOE, review your existing BYOE bindings before migrating.
- Be aware that migration requests may be blocked temporarily if your migration quota for the current window has been exhausted.
3. How to Start a Region Migration
- Log into your Client Area and open your Product Details Page.
- Open Region Migration.
- Review your Current region.
- Select a destination under Target region.
- Click Migrate region.
After you submit the request, the client area opens the migration status page and automatically starts a preflight check.
4. What Happens During Preflight
Before the actual migration starts, the platform checks whether the request can proceed.
- It verifies whether migration is currently allowed.
- It checks migration quota limits for the current time window.
- It checks whether the service has existing BYOE bindings that would be affected.
5. How to Read the Migration Status Page
The migration status page shows the current step and final result of your request.
- Checking migration requirements... The preflight validation is in progress.
- Blocked: The migration cannot continue right now, usually because of quota or policy limits.
- Confirm and migrate: A confirmation step is required before execution continues.
- Migrating your service to the new region, please wait... The platform is executing the migration.
- Migration completed successfully. The move finished successfully.
- Migration failed. The request did not complete and may need to be retried later.
The page also includes action buttons such as Retry, Back to region migration, and Back to overview.
6. BYOE and Region Migration
If your service has active BYOE bindings, the migration flow may show a warning before it proceeds.
- The platform may warn that existing BYOE bindings will be unbound after migration.
- You may need to review and reconfigure BYOE bindings after the region change is complete.
- If you rely on BYOE for production traffic, make sure you understand this impact before confirming the migration.
7. Important Notes and Limitations
- Region migration is available only for products that expose this feature.
- The list of target regions can change based on current platform capacity and policy.
- Migration may be rate-limited or quota-limited within a given time window.
- If the request is blocked, you may need to wait and try again later.
- BYOE bindings may be cleared as part of the migration process.
- After migration, always verify that your service is operating as expected in the new region.
Recommended Workflow
- Check whether the destination region you want is currently available.
- Review any seat, BYOE, or access-related settings that may need attention after migration.
- Start the migration from the client area and wait for the preflight result.
- If a confirmation warning appears, read it carefully before proceeding.
- After the migration completes, return to the overview page and confirm that the new region and service behavior are correct.