Can we integrate a vnet to an azure container registry by passing the vnet id in the ARM template?

Question

"networkRuleSet":{
            "defaultAction": "[if(equals(parameters('networkRuleSetStatus'), 'Enabled'), 'Deny', 'Allow')]",
            "virtualNetworkRules":[{
              "action": "Allow",
              "id": "[resourceId('Microsoft.Network/virtualNetworks/subnets', parameters('existingVnetName'), parameters('existingSubnetName'))]"
          }],
            "copy":[{
              "name":"ipRules",
              "count":"[length(parameters('ip'))]",
              "input":{
              "action": "Allow",
              "value": "[parameters('ip') [copyIndex('ipRules')]]"
              }
            }]
          },

The above lines are part of the ARM to pass the vnetid in the network section.

score 1 · Accepted Answer · answered Apr 26 '21 at 06:27

1

It's possible to integrate a vnet to the Azure container registry and what you did is right. But there is one thing you may miss. The thing is when you want to allow a subnet to access the container registry, you need to enable the private endpoint for the container registry in that subnet. The example CLI command here:

az network vnet subnet update \
  --name myDockerVMSubnet \
  --vnet-name myDockerVMVNET \
  --resource-group myResourceGroup \
  --service-endpoints Microsoft.ContainerRegistry

After this action, then you can add the network rule through the template as you showed.

answered Apr 26 '21 at 06:27

Charles Xu

29,862
2
22
39

Okay ..Thank you ! but could you please tell me how to check if the vnet is integrated with the container registry after the ARM deployment as I don't see a tab in portal. TIA @charles-xu – twinkle hema Apr 27 '21 at 13:18
appreciate the quick help @CharlesXu – twinkle hema Apr 27 '21 at 13:25
@twinklehema Sure. You can use the command, for example, CLI command `az acr show -n acrName--query networkRuleSet.virtualNetworkRules` to check the subnet resource id. – Charles Xu Apr 28 '21 at 01:02
but this still shows null "virtualNetworkRules": [] in the export template and with the above command also. – twinkle hema Apr 28 '21 at 06:28
vnet id is not being passed – twinkle hema Apr 28 '21 at 06:30
@twinklehema It shows the subnet id, when you know the subnet id, you also know the vnet id, doesn't it? – Charles Xu Apr 28 '21 at 06:41
unrecognized arguments: networkRuleSet.virtualNetworkRules it throws this error not showing any id – twinkle hema Apr 28 '21 at 07:28
@twinklehema Can you share the screenshot about the command you use? – Charles Xu Apr 28 '21 at 08:06
Let us [continue this discussion in chat](https://chat.stackoverflow.com/rooms/231693/discussion-between-twinkle-hema-and-charles-xu). – twinkle hema Apr 28 '21 at 09:41
there is an error in passing the resource id – twinkle hema Apr 29 '21 at 16:04
@twinklehema What is that? Share the details of the error. – Charles Xu Apr 30 '21 at 01:07

Can we integrate a vnet to an azure container registry by passing the vnet id in the ARM template?

1 Answers1