AZ migration capability is disabled
Made post on behalf of: @Solomon Tefera
We have an issue with AZ migration capability:
AZ migration capability is disabled for subscription 52a11d32-2a8b-4a14-9c95-14e83665faa4. Please contact sotofera on teams.
Status: Failed Error: Code: BadRequest Message: AZ migration capability is disabled for subscription 52a11d32-2a8b-4a14-9c95-14e83665faa4. ActivityId: 38f17e54-883b-46f3-a442-839e671448cb, Microsoft.Azure.Documents.Common/2.14.0 Help Link: https://aka.ms/ev2/errors/troubleshooting Deployment Name: 32BF89787D724EED89E1817ED5236FDB0CosmosDb.UnifiedCredentials.ST Operation Id: 19BC0DA20D309390 Operation: Create Mode: Incremental Correlation Id: 32bf8978-7d72-4eed-89e1-817ed5236fd1
-
SAI JAGADEESH KUDIPUDI 3,470 Reputation points • Microsoft External Staff • Moderator
Hi Evan Wong,**
**Could you please share requested details in private message? -
SAI JAGADEESH KUDIPUDI 3,470 Reputation points • Microsoft External Staff • Moderator
Hi Evan Wong,
I just wanted to kindly follow up regarding the requested details. Could you please share the information via private message at your convenience?Your response will help us proceed further with the investigation. Please let us know if you need any assistance from our side.
-
SAI JAGADEESH KUDIPUDI 3,470 Reputation points • Microsoft External Staff • Moderator
Hi @Evan Wong ,
Sure, we will reach out to Solomon Tefera (sotefera) on Teams and update you accordingly. -
SAI JAGADEESH KUDIPUDI 3,470 Reputation points • Microsoft External Staff • Moderator
Hi @Evan Wong
Thank you for reaching out and for sharing the details.
We understand that you are seeing the error:
"AZ migration capability is disabled for subscription."This issue usually happens when trying to update an existing region with Availability Zone (zone redundancy) enabled, which is currently not supported.
Explanation:
Zone redundancy can only be configured while adding a new region to an Azure Cosmos DB account. It cannot be enabled directly on an existing region.To resolve this, we kindly request you to follow the below steps:
If you want to enable zone redundancy for an existing region:
- Remove the existing region from the Cosmos DB account
- Re-add the same region with zone redundancy enabled
- First, add a **temporary failover region** - Then remove the original region - Re-add it with **zone redundancy enabled**
- Before adding a region, please verify if your subscription and region support zone redundancy using Azure CLI.
These steps should help you configure the required setup correctly.
Please let us know if you need any further assistance. We are happy to help.
- Remove the existing region from the Cosmos DB account
Sign in to comment
1 answer
-
Alex Burlachenko 22,120 Reputation points • MVP • Volunteer Moderator
hi Evan Wong & thanks for join me here at Q&A portal,
yeah this is a subscription capability flag, not a normal Cosmos DB template error. AZ migration capability is disabled for subscription means the deployment is trying to enable or migrate Availability Zone support for Cosmos DB, but that feature is not enabled for that subscription or not supported for that account type.
See what the deployment is doing. Look for isZoneRedundant, region failover changes, or any Cosmos DB account migration step in CosmosDb.UnifiedCredentials.ST. Azure Cosmos DB availability zone guidance https://learn.microsoft.com/en-us/azure/reliability/reliability-cosmos-db If this is Free Tier, Serverless, or another restricted Cosmos account type, AZ migration may not be supported. There is a similar Microsoft Q&A case where this exact error was tied to unsupported Free Tier AZ migration https://learn.microsoft.com/en-us/answers/questions/5579780/az-migration-capability-is-disabled-for-this-subsc If this is an internal Microsoft production subscription, this likely needs Cosmos DB backend enablement. Open a Cosmos DB support ticket or internal engineering request and include subscription ID, operation ID 19BC0DA20D309390, activity ID 38f17e54-883b-46f3-a442-839e671448cb, deployment name, region, account name, and whether the account is serverless, provisioned throughput, or free tier. Retrying the deployment will not help until the subscription is enabled for AZ migration or the deployment is changed to avoid AZ migration.
rgds,
Alex
&
If my answer was helpful pls mark it and additional thx if u follow me at Q&A portal
