Hello Varma,
I have reproduced the issue with your script in our environment, and finally we were able to create a RG, Key vault and ACR.
Used script for your reference:
{
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"resourceGroupName": {
"type": "string"
},
"acrName": {
"type": "string"
},
"keyVaultName": {
"type": "string"
}
},
"resources": [
{
"type": "Microsoft.ContainerRegistry/registries",
"apiVersion": "2019-05-01",
"name": "[parameters('acrName')]",
"location": "[resourceGroup().location]",
"sku": {
"name": "Basic"
}
},
{
"type": "Microsoft.KeyVault/vaults",
"apiVersion": "2019-09-01",
"name": "[parameters('keyVaultName')]",
"location": "[resourceGroup().location]",
"properties": {
"sku": {
"family": "A",
"name": "standard"
},
"tenantId": "[subscription().tenantId]",
"accessPolicies": []
}
}
// Add VNet and other resources similarly
]
}
Please validated the below points before deploying.
- The subscription has to be registered with the Resource provider
- ACR name should be globally unique with minimum 5 letters.
- Key vault should be globally unique.
Eventual results for your reference.
If you find the answer helps your query, please click upvote it.
Thanks