ACR Connected Registries error in Azure Portal for CanadaCentral region
Closed this issue · 2 comments
Describe the bug
Documentation bug. The Connected Registries feature docs states that it's available in the CanadaCentral
region, but an error occurs when trying to enable this feature via the portal.
To Reproduce
Steps to reproduce the behavior:
- Create a new Premium ACR instance in
CanadaCentral
region - Once created, navigate to the connected registries feature blade.
- Notice that the warning message/bar at the top of the page states that the connected registries feature isn't available in the CanadaCentral region.
- Enabling this feature in the CanadaCentral region via the Azure CLI seems to work OK (steps from docs below).
RESOURCE_GROUP=acr-test-rg
LOCATION=canadacentral
REGISTRY_NAME=acrtest78491823
CONNECTED_REGISTRY_RW=acrtest78491823cxnregrw
az acr create --name $REGISTRY_NAME \
--resource-group $RESOURCE_GROUP \
--location $LOCATION \
--sku Premium
az acr update --name $REGISTRY_NAME \
--data-endpoint-enabled
az acr import \
--name $REGISTRY_NAME \
--source mcr.microsoft.com/acr/connected-registry:0.8.0
az acr import \
--name $REGISTRY_NAME \
--source mcr.microsoft.com/azureiotedge-agent:1.2.4
az acr connected-registry create --registry $REGISTRY_NAME \
--name $CONNECTED_REGISTRY_RW \
--repository "acr/connected-registry" "azureiotedge-agent"
az acr connected-registry list \
--registry $REGISTRY_NAME \
--output table
Expected behavior
As per the docs, CanadaCentral
region should support the Connected Registries feature. Please remove the error message in the Portal.
If any information is a concern to post here, you can create a support ticket or send an email to acrsup@microsoft.com.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days.
This issue was closed because it has been stalled for 30 days with no activity.