Skip to content

Commit ef34c6f

Browse files
edits
1 parent f8e9133 commit ef34c6f

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/container-registry/manual-regional-move.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,8 +27,10 @@ Azure CLI
2727

2828
* Use steps in this article to move the registry to a different region in the same subscription. More configuration may be needed to move a registry to a different Azure subscription in the same Active Directory tenant.
2929
* Exporting and using a Resource Manager template can help re-create many registry settings. You can edit the template to configure more settings, or update the target registry after creation.
30+
* You can also use a Resource Manager to move the registry to a different region to the [new resource group or a new subscription.](../articles/azure-resource-manager/management/move-resource-group-and-subscription.md).
3031
* Currently, Azure Container Registry doesn't support a registry move to a different Active Directory tenant. This limitation applies to both registries encrypted with a [customer-managed key](container-registry-customer-managed-keys.md) and unencrypted registries.
3132
* If you are unable to move a registry is outlined in this article, create a new registry, manually recreate settings, and [Import registry content in the target registry](#import-registry-content-in-target-registry).
33+
* To move
3234

3335
## Export template from source registry
3436

0 commit comments

Comments
 (0)