Merge pull request #280613 from mumian/0711-merge-repo2

update api versions and remove the sample repo - batch 2

Author: prmerger-automator[bot]

articles/azure-resource-manager/bicep/compare-template-syntax.md

@@ -3,7 +3,7 @@ title: Compare syntax for Azure Resource Manager templates in JSON and Bicep
 description: Compares Azure Resource Manager templates developed with JSON and Bicep, and shows how to convert between the languages.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 06/23/2023
+ms.date: 07/11/2024
 ---
 
 # Comparing JSON and Bicep for templates
@@ -134,7 +134,7 @@ targetScope = 'subscription'
 To declare a resource:
 
 ```bicep
-resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = {
+resource virtualMachine 'Microsoft.Compute/virtualMachines@2024-03-01' = {
   ...
 }
 ```
@@ -143,7 +143,7 @@ resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = {
 "resources": [
   {
     "type": "Microsoft.Compute/virtualMachines",
-    "apiVersion": "2020-06-01",
+    "apiVersion": "2024-03-01",
     ...
   }
 ]
@@ -152,7 +152,7 @@ resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = {
 To conditionally deploy a resource:
 
 ```bicep
-resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = if(deployVM) {
+resource virtualMachine 'Microsoft.Compute/virtualMachines@2024-03-01' = if(deployVM) {
   ...
 }
 ```
@@ -162,7 +162,7 @@ resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = if(depl
   {
     "condition": "[parameters('deployVM')]",
     "type": "Microsoft.Compute/virtualMachines",
-    "apiVersion": "2023-03-01",
+    "apiVersion": "2024-03-01",
     ...
   }
 ]
@@ -213,11 +213,11 @@ For Bicep, you can set an explicit dependency but this approach isn't recommende
 The following shows a network interface with an implicit dependency on a network security group. It references the network security group with `netSecurityGroup.id`.
 
 ```bicep
-resource netSecurityGroup 'Microsoft.Network/networkSecurityGroups@2022-11-01' = {
+resource netSecurityGroup 'Microsoft.Network/networkSecurityGroups@2023-11-01' = {
   ...
 }
 
-resource nic1 'Microsoft.Network/networkInterfaces@2022-11-01' = {
+resource nic1 'Microsoft.Network/networkInterfaces@2023-11-01' = {
   name: nic1Name
   location: location
   properties: {
@@ -254,7 +254,7 @@ storageAccount.properties.primaryEndpoints.blob
 To get a property from an existing resource that isn't deployed in the template:
 
 ```bicep
-resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
   name: storageAccountName
 }
 

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

@@ -3,7 +3,7 @@ title: Conditional deployment with Bicep
 description: Describes how to conditionally deploy a resource in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Conditional deployments in Bicep with the if expression
@@ -24,7 +24,7 @@ In Bicep, you can conditionally deploy a resource by passing in a parameter that
 ```bicep
 param deployZone bool
 
-resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = if (deployZone) {
+resource dnsZone 'Microsoft.Network/dnsZones@2023-07-01-preview' = if (deployZone) {
   name: 'myZone'
   location: 'global'
 }
@@ -56,7 +56,7 @@ param location string = resourceGroup().location
 ])
 param newOrExisting string = 'new'
 
-resource saNew 'Microsoft.Storage/storageAccounts@2022-09-01' = if (newOrExisting == 'new') {
+resource saNew 'Microsoft.Storage/storageAccounts@2023-04-01' = if (newOrExisting == 'new') {
   name: storageAccountName
   location: location
   sku: {
@@ -65,7 +65,7 @@ resource saNew 'Microsoft.Storage/storageAccounts@2022-09-01' = if (newOrExistin
   kind: 'StorageV2'
 }
 
-resource saExisting 'Microsoft.Storage/storageAccounts@2022-09-01' existing = if (newOrExisting == 'existing') {
+resource saExisting 'Microsoft.Storage/storageAccounts@2023-04-01' existing = if (newOrExisting == 'existing') {
   name: storageAccountName
 }
 
@@ -88,7 +88,7 @@ param vmName string
 param location string
 param logAnalytics string = ''
 
-resource vmName_omsOnboarding 'Microsoft.Compute/virtualMachines/extensions@2023-03-01' = if (!empty(logAnalytics)) {
+resource vmName_omsOnboarding 'Microsoft.Compute/virtualMachines/extensions@2024-03-01' = if (!empty(logAnalytics)) {
   name: '${vmName}/omsOnboarding'
   location: location
   properties: {

articles/azure-resource-manager/bicep/create-resource-group.md

@@ -22,7 +22,7 @@ targetScope='subscription'
 param resourceGroupName string
 param resourceGroupLocation string
 
-resource newRG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2024-03-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
 }
@@ -65,7 +65,7 @@ param resourceGroupLocation string
 param storageName string
 param storageLocation string
 
-resource newRG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2024-03-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
 }
@@ -86,7 +86,7 @@ The module uses a Bicep file named **storage.bicep** with the following contents
 param storageLocation string
 param storageName string
 
-resource storageAcct 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource storageAcct 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageName
   location: storageLocation
   sku: {

articles/azure-resource-manager/bicep/decompile.md

@@ -106,10 +106,10 @@ param storageAccountType string = 'Standard_LRS'
 @description('Location for all resources.')
 param location string = resourceGroup().location
 
-var storageAccountName_var = 'store${uniqueString(resourceGroup().id)}'
+var storageAccountName = 'store${uniqueString(resourceGroup().id)}'
 
-resource storageAccountName 'Microsoft.Storage/storageAccounts@2019-06-01' = {
-  name: storageAccountName_var
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+  name: storageAccountName
   location: location
   sku: {
     name: storageAccountType
@@ -118,7 +118,7 @@ resource storageAccountName 'Microsoft.Storage/storageAccounts@2019-06-01' = {
   properties: {}
 }
 
-output storageAccountName string = storageAccountName_var
+output storageAccountName string = storageAccountName
 ```
 
 The decompiled file works, but it has some names that you might want to change. The variable `var storageAccountName_var` has an unusual naming convention. Let's change it to:
@@ -152,7 +152,7 @@ param location string = resourceGroup().location
 
 var uniqueStorageName = 'store${uniqueString(resourceGroup().id)}'
 
-resource exampleStorage 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource exampleStorage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: uniqueStorageName
   location: location
   sku: {

articles/azure-resource-manager/bicep/deploy-to-management-group.md

@@ -128,7 +128,7 @@ To deploy resources to the target management group, add those resources with the
 targetScope = 'managementGroup'
 
 // policy definition created in the management group
-resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2021-06-01' = {
+resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2023-04-01' = {
   ...
 }
 ```
@@ -211,7 +211,7 @@ targetScope = 'managementGroup'
 
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
-resource newMG 'Microsoft.Management/managementGroups@2021-04-01' = {
+resource newMG 'Microsoft.Management/managementGroups@2023-04-01' = {
   scope: tenant()
   name: mgName
   properties: {}
@@ -227,7 +227,7 @@ targetScope = 'managementGroup'
 
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
-resource newMG 'Microsoft.Management/managementGroups@2021-04-01' = {
+resource newMG 'Microsoft.Management/managementGroups@2023-04-01' = {
   scope: tenant()
   name: mgName
   properties: {
@@ -268,7 +268,7 @@ param allowedLocations array = [
   'australiacentral'
 ]
 
-resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2021-06-01' = {
+resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2023-04-01' = {
   name: 'locationRestriction'
   properties: {
     policyType: 'Custom'
@@ -288,7 +288,7 @@ resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2021-06-01'
   }
 }
 
-resource policyAssignment 'Microsoft.Authorization/policyAssignments@2022-06-01' = {
+resource policyAssignment 'Microsoft.Authorization/policyAssignments@2024-04-01' = {
   name: 'locationAssignment'
   properties: {
     policyDefinitionId: policyDefinition.id

articles/azure-resource-manager/bicep/deploy-to-resource-group.md

@@ -3,7 +3,7 @@ title: Use Bicep to deploy resources to resource groups
 description: Describes how to deploy resources in a Bicep file. It shows how to target more than one resource group.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Resource group deployments with Bicep files
@@ -81,7 +81,7 @@ To deploy resources to the target resource group, add those resources to the Bic
 
 ```bicep
 // resource deployed to target resource group
-resource exampleResource 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource exampleResource 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   ...
 }
 ```
@@ -172,7 +172,7 @@ Instead of using a module, you can set the scope to `tenant()` for some resource
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
 // ManagementGroup deployed at tenant
-resource managementGroup 'Microsoft.Management/managementGroups@2020-05-01' = {
+resource managementGroup 'Microsoft.Management/managementGroups@2023-04-01' = {
   scope: tenant()
   name: mgName
   properties: {}
@@ -235,7 +235,7 @@ Both modules use the same Bicep file named **storage.bicep**.
 param storageLocation string
 param storageName string
 
-resource storageAcct 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource storageAcct 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageName
   location: storageLocation
   sku: {

articles/azure-resource-manager/bicep/deploy-to-subscription.md

@@ -165,7 +165,7 @@ To deploy resources to the target subscription, add those resources with the `re
 targetScope = 'subscription'
 
 // resource group created in target subscription
-resource exampleResource 'Microsoft.Resources/resourceGroups@2022-09-01' = {
+resource exampleResource 'Microsoft.Resources/resourceGroups@2024-03-01' = {
   ...
 }
 ```
@@ -229,7 +229,7 @@ targetScope = 'subscription'
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
 // management group created at tenant
-resource managementGroup 'Microsoft.Management/managementGroups@2021-04-01' = {
+resource managementGroup 'Microsoft.Management/managementGroups@2023-04-01' = {
   scope: tenant()
   name: mgName
   properties: {}
@@ -257,7 +257,7 @@ param policyDefinitionID string
 param policyName string
 param policyParameters object = {}
 
-resource policyAssign 'Microsoft.Authorization/policyAssignments@2022-06-01' = {
+resource policyAssign 'Microsoft.Authorization/policyAssignments@2024-04-01' = {
   name: policyName
   properties: {
     policyDefinitionId: policyDefinitionID
@@ -273,7 +273,7 @@ You can [define](../../governance/policy/concepts/definition-structure.md) and a
 ```bicep
 targetScope = 'subscription'
 
-resource locationPolicy 'Microsoft.Authorization/policyDefinitions@2021-06-01' = {
+resource locationPolicy 'Microsoft.Authorization/policyDefinitions@2023-04-01' = {
   name: 'locationpolicy'
   properties: {
     policyType: 'Custom'
@@ -290,7 +290,7 @@ resource locationPolicy 'Microsoft.Authorization/policyDefinitions@2021-06-01' =
   }
 }
 
-resource locationRestrict 'Microsoft.Authorization/policyAssignments@2022-06-01' = {
+resource locationRestrict 'Microsoft.Authorization/policyAssignments@2024-04-01' = {
   name: 'allowedLocation'
   properties: {
     policyDefinitionId: locationPolicy.id
@@ -324,7 +324,7 @@ param roleAssignmentName string = guid(principalId, roleDefinitionId, resourceGr
 
 var roleID = '/subscriptions/${subscription().subscriptionId}/providers/Microsoft.Authorization/roleDefinitions/${roleDefinitionId}'
 
-resource newResourceGroup 'Microsoft.Resources/resourceGroups@2022-09-01' = {
+resource newResourceGroup 'Microsoft.Resources/resourceGroups@2024-03-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
   properties: {}

articles/azure-resource-manager/bicep/deploy-to-tenant.md

@@ -3,7 +3,7 @@ title: Use Bicep to deploy resources to tenant
 description: Describes how to deploy resources at the tenant scope in a Bicep file.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 06/23/2023
+ms.date: 07/11/2024
 ---
 
 # Tenant deployments with Bicep file
@@ -141,7 +141,7 @@ Resources defined within the Bicep file are applied to the tenant.
 targetScope = 'tenant'
 
 // create resource at tenant
-resource mgName_resource 'Microsoft.Management/managementGroups@2021-04-01' = {
+resource mgName_resource 'Microsoft.Management/managementGroups@2023-04-01' = {
   ...
 }
 ```
@@ -203,7 +203,7 @@ The following template creates a management group.
 targetScope = 'tenant'
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
-resource mgName_resource 'Microsoft.Management/managementGroups@2021-04-01' = {
+resource mgName_resource 'Microsoft.Management/managementGroups@2023-04-01' = {
   name: mgName
   properties: {}
 }

articles/azure-resource-manager/bicep/deployment-script-bicep-configure-dev.md

@@ -2,7 +2,7 @@
 title: Configure development environment for deployment scripts in Bicep | Microsoft Docs
 description: Configure development environment for deployment scripts in Bicep.
 ms.topic: how-to
-ms.date: 12/13/2023
+ms.date: 07/11/2024
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
 ms.devlang: azurecli
 ---
@@ -237,7 +237,7 @@ var fileShareName = '${projectName}share'
 var containerGroupName = '${projectName}cg'
 var containerName = '${projectName}container'
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountName
   location: location
   sku: {
@@ -249,7 +249,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
   }
 }
 
-resource fileshare 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-01-01' = {
+resource fileshare 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-04-01' = {
   name: '${storageAccountName}/default/${fileShareName}'
   dependsOn: [
     storageAccount