AzMigration Feature not enabled to migrate cosmosdb account to zone redundant

Question

Observing this issue while migrating cosmosdb to zone redundancy

Answer 1

Hi @Navpreet Kaur

Azure Cosmos DB validates both Availability Zone support for the target region and whether the subscription is enabled to use Availability Zones in that region. If the subscription capability isn't enabled, the required capability must be enabled before zonal redundancy can be configured.

For existing Azure Cosmos DB accounts, zone redundancy cannot be enabled directly on a region that is already part of the account. The supported approach is to:

• Add a temporary region.
• Remove the existing target region.
• Re-add the region with isZoneRedundant=True.
• Remove the temporary region after replication completes.

This process can be automated using Azure CLI, Bicep, ARM templates, or PowerShell, but it requires multiple deployment stages because region changes are implemented as add/remove operations rather than an in-place update.

For example, if an account contains Region A and Region B, and you need to enable zone redundancy for Region B, the supported method is to remove Region B and re-add it with isZoneRedundant=True. Once the new region is added, Azure Cosmos DB must fully replicate and commit all data before the region is marked as available. The duration depends on the amount of data stored in the account.

Reference:
https://learn.microsoft.com/en-us/azure/cosmos-db/enable-zone-redundancy?tabs=portal
https://docs.azure.cn/en-us/cosmos-db/how-to-manage-database-account#add-remove-regions-from-your-database-account
https://learn.microsoft.com/en-us/azure/reliability/reliability-cosmos-db

Please let us know if you have any questions or concerns.