refresh articles

Author: mumian

articles/azure-resource-manager/templates/child-resource-name-type.md

@@ -3,7 +3,7 @@ title: Child resources in templates
 description: Describes how to set the name and type for child resources in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 06/20/2024
+ms.date: 07/23/2025
 ---
 
 # Set name and type for child resources
@@ -47,7 +47,7 @@ The following example shows a virtual network and with a subnet. Notice that the
 "resources": [
   {
     "type": "Microsoft.Network/virtualNetworks",
-    "apiVersion": "2022-11-01",
+    "apiVersion": "2024-07-01",
     "name": "VNet1",
     "location": "[parameters('location')]",
     "properties": {
@@ -60,7 +60,7 @@ The following example shows a virtual network and with a subnet. Notice that the
     "resources": [
       {
         "type": "subnets",
-        "apiVersion": "2022-11-01",
+        "apiVersion": "2024-07-01",
         "name": "Subnet1",
         "dependsOn": [
           "VNet1"
@@ -106,7 +106,7 @@ The following example shows a virtual network and subnet that are both defined a
 "resources": [
   {
     "type": "Microsoft.Network/virtualNetworks",
-    "apiVersion": "2022-11-01",
+    "apiVersion": "2024-07-01",
     "name": "VNet1",
     "location": "[parameters('location')]",
     "properties": {
@@ -119,7 +119,7 @@ The following example shows a virtual network and subnet that are both defined a
   },
   {
     "type": "Microsoft.Network/virtualNetworks/subnets",
-    "apiVersion": "2022-11-01",
+    "apiVersion": "2024-07-01",
     "name": "VNet1/Subnet1",
     "dependsOn": [
       "VNet1"

articles/azure-resource-manager/templates/conditional-resource-deployment.md

@@ -3,7 +3,7 @@ title: Conditional deployment with templates
 description: Describes how to conditionally deploy a resource in an Azure Resource Manager template (ARM template).
 ms.topic: conceptual
 ms.custom: devx-track-arm-template
-ms.date: 06/20/2024
+ms.date: 07/23/2025
 ---
 
 # Conditional deployment in ARM templates
@@ -26,17 +26,21 @@ You can pass in a parameter value that indicates whether a resource is deployed.
   "contentVersion": "1.0.0.0",
   "parameters": {
     "deployZone": {
-      "type": "bool"
+      "type": "bool",
+      "defaultValue": true
     }
   },
   "functions": [],
   "resources": [
     {
       "condition": "[parameters('deployZone')]",
       "type": "Microsoft.Network/dnsZones",
-      "apiVersion": "2018-05-01",
+      "apiVersion": "2024-07-01-preview",
       "name": "myZone",
-      "location": "global"
+      "location": "global",
+      "properties": {
+        "zoneType": "Public"
+      }
     }
   ]
 }
@@ -73,7 +77,7 @@ You can use conditional deployment to create a new resource or use an existing o
     {
       "condition": "[equals(parameters('newOrExisting'), 'new')]",
       "type": "Microsoft.Storage/storageAccounts",
-      "apiVersion": "2022-09-01",
+      "apiVersion": "2025-01-01",
       "name": "[parameters('storageAccountName')]",
       "location": "[parameters('location')]",
       "sku": {
@@ -84,7 +88,7 @@ You can use conditional deployment to create a new resource or use an existing o
     {
       "condition": "[equals(parameters('newOrExisting'), 'existing')]",
       "type": "Microsoft.Storage/storageAccounts",
-      "apiVersion": "2022-09-01",
+      "apiVersion": "2025-01-01",
       "name": "[parameters('storageAccountName')]"
     }
   ],

articles/azure-resource-manager/templates/copy-outputs.md

@@ -3,7 +3,7 @@ title: Define multiple instances of an output value
 description: Use copy operation in an Azure Resource Manager template (ARM template) to iterate multiple times when returning a value from a deployment.
 ms.topic: how-to
 ms.custom: devx-track-arm-template
-ms.date: 06/20/2024
+ms.date: 07/23/2025
 ---
 
 # Output iteration in ARM templates
@@ -71,7 +71,7 @@ The following example creates a variable number of storage accounts and returns
         "count": "[parameters('storageCount')]"
       },
       "type": "Microsoft.Storage/storageAccounts",
-      "apiVersion": "2022-09-01",
+      "apiVersion": "2025-01-01",
       "name": "[format('{0}{1}', copyIndex(), variables('baseName'))]",
       "location": "[parameters('location')]",
       "sku": {
@@ -128,7 +128,7 @@ The next example returns three properties from the new storage accounts.
         "count": "[length(range(0, parameters('storageCount')))]"
       },
       "type": "Microsoft.Storage/storageAccounts",
-      "apiVersion": "2022-09-01",
+      "apiVersion": "2025-01-01",
       "name": "[format('{0}{1}', range(0, parameters('storageCount'))[copyIndex()], variables('baseName'))]",
       "location": "[parameters('location')]",
       "sku": {

articles/azure-resource-manager/templates/index.yml

@@ -10,7 +10,7 @@ metadata:
   ms.author: jgao
   ms.subservice: templates
   ms.topic: landing-page
-  ms.date: 06/20/2024
+  ms.date: 07/23/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 

articles/azure-resource-manager/templates/key-vault-parameter.md

@@ -2,7 +2,7 @@
 title: Key Vault secret with template
 description: Shows how to pass a secret from a key vault as a parameter during deployment.
 ms.topic: how-to
-ms.date: 06/20/2024
+ms.date: 07/23/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli
 ---
 
@@ -108,51 +108,51 @@ For other users, grant the `Microsoft.KeyVault/vaults/deploy/action` permission.
 
 1. Create a custom role definition JSON file:
 
-    ```json
-    {
-      "Name": "Key Vault resource manager template deployment operator",
-      "IsCustom": true,
-      "Description": "Lets you deploy a resource manager template with the access to the secrets in the Key Vault.",
-      "Actions": [
-        "Microsoft.KeyVault/vaults/deploy/action"
-      ],
-      "NotActions": [],
-      "DataActions": [],
-      "NotDataActions": [],
-      "AssignableScopes": [
-        "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e"
-      ]
-    }
-    ```
-
-    Replace "00000000-0000-0000-0000-000000000000" with the subscription ID.
-
-2. Create the new role using the JSON file:
-
-    # [Azure CLI](#tab/azure-cli)
-
-    ```azurecli-interactive
-    az role definition create --role-definition "<path-to-role-file>"
-    az role assignment create \
-      --role "Key Vault resource manager template deployment operator" \
-      --scope /subscriptions/<Subscription-id>/resourceGroups/<resource-group-name> \
-      --assignee <user-principal-name> \
-      --resource-group ExampleGroup
-    ```
-
-    # [PowerShell](#tab/azure-powershell)
-
-    ```azurepowershell-interactive
-    New-AzRoleDefinition -InputFile "<path-to-role-file>"
-    New-AzRoleAssignment `
-      -ResourceGroupName ExampleGroup `
-      -RoleDefinitionName "Key Vault resource manager template deployment operator" `
-      -SignInName <user-principal-name>
-    ```
-
-    ---
-
-    The samples assign the custom role to the user on the resource group level.
+  ```json
+  {
+    "Name": "Key Vault resource manager template deployment operator",
+    "IsCustom": true,
+    "Description": "Lets you deploy a resource manager template with the access to the secrets in the Key Vault.",
+    "Actions": [
+      "Microsoft.KeyVault/vaults/deploy/action"
+    ],
+    "NotActions": [],
+    "DataActions": [],
+    "NotDataActions": [],
+    "AssignableScopes": [
+      "/subscriptions/aaaa0a0a-bb1b-cc2c-dd3d-eeeeee4e4e4e"
+    ]
+  }
+  ```
+  
+  Replace "00000000-0000-0000-0000-000000000000" with the subscription ID.
+
+1. Create the new role using the JSON file:
+
+  # [Azure CLI](#tab/azure-cli)
+  
+  ```azurecli-interactive
+  az role definition create --role-definition "<path-to-role-file>"
+  az role assignment create \
+    --role "Key Vault resource manager template deployment operator" \
+    --scope /subscriptions/<Subscription-id>/resourceGroups/<resource-group-name> \
+    --assignee <user-principal-name> \
+    --resource-group ExampleGroup
+  ```
+  
+  # [PowerShell](#tab/azure-powershell)
+  
+  ```azurepowershell-interactive
+  New-AzRoleDefinition -InputFile "<path-to-role-file>"
+  New-AzRoleAssignment `
+    -ResourceGroupName ExampleGroup `
+    -RoleDefinitionName "Key Vault resource manager template deployment operator" `
+    -SignInName <user-principal-name>
+  ```
+  
+  ---
+  
+  The samples assign the custom role to the user on the resource group level.
 
 When using a key vault with the template for a [Managed Application](../managed-applications/overview.md), you must grant access to the **Appliance Resource Provider** service principal. For more information, see [Access Key Vault secret when deploying Azure Managed Applications](../managed-applications/key-vault-access.md).
 
@@ -188,7 +188,7 @@ The following template deploys a SQL server that includes an administrator passw
   "resources": [
     {
       "type": "Microsoft.Sql/servers",
-      "apiVersion": "2021-11-01",
+      "apiVersion": "2024-05-01-preview",
       "name": "[parameters('sqlServerName')]",
       "location": "[parameters('location')]",
       "properties": {
@@ -312,7 +312,7 @@ The following template dynamically creates the key vault ID and passes it as a p
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2020-10-01",
+      "apiVersion": "2025-04-01",
       "name": "dynamicSecret",
       "properties": {
         "mode": "Incremental",
@@ -339,7 +339,7 @@ The following template dynamically creates the key vault ID and passes it as a p
           "resources": [
             {
               "type": "Microsoft.Sql/servers",
-              "apiVersion": "2021-11-01",
+              "apiVersion": "2024-05-01-preview",
               "name": "[variables('sqlServerName')]",
               "location": "[parameters('location')]",
               "properties": {

articles/azure-resource-manager/templates/template-spec-convert.md

@@ -2,7 +2,7 @@
 title: Convert portal template to template spec
 description: Describes how to convert an existing template in the Azure portal gallery to a template specs.
 ms.topic: how-to
-ms.date: 06/20/2024
+ms.date: 07/23/2025
 ---
 
 # Convert template gallery in portal to template specs