Merge pull request #242809 from mumian/0623-bicep-fresh-2

Bicep content freshness - 2

Author: JamesJBarnett

articles/azure-resource-manager/bicep/best-practices.md

@@ -5,7 +5,7 @@ author: johndowns
 ms.author: jodowns
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 05/16/2022
+ms.date: 06/23/2023
 ---
 # Best practices for Bicep
 
@@ -68,13 +68,13 @@ For more information about Bicep variables, see [Variables in Bicep](variables.m
 * Avoid using `name` in a symbolic name. The symbolic name represents the resource, not the resource's name. For example, instead of the following syntax:
 
   ```bicep
-  resource cosmosDBAccountName 'Microsoft.DocumentDB/databaseAccounts@2021-04-15' = {
+  resource cosmosDBAccountName 'Microsoft.DocumentDB/databaseAccounts@2023-04-15' = {
   ```
 
   Use:
 
   ```bicep
-  resource cosmosDBAccount 'Microsoft.DocumentDB/databaseAccounts@2021-04-15' = {
+  resource cosmosDBAccount 'Microsoft.DocumentDB/databaseAccounts@2023-04-15' = {
   ```
 
 * Avoid distinguishing variables and parameters by the use of suffixes.

articles/azure-resource-manager/bicep/bicep-functions-date.md

@@ -1,11 +1,9 @@
 ---
 title: Bicep functions - date
 description: Describes the functions to use in a Bicep file to work with dates.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 05/03/2022
+ms.date: 06/23/2023
 ---
 
 # Date functions for Bicep
@@ -67,7 +65,7 @@ var startTime = dateTimeAdd(baseTime, 'PT1H')
 
 ...
 
-resource scheduler 'Microsoft.Automation/automationAccounts/schedules@2015-10-31' = {
+resource scheduler 'Microsoft.Automation/automationAccounts/schedules@2022-08-08' = {
   name: concat(omsAutomationAccountName, '/', scheduleName)
   properties: {
     description: 'Demo Scheduler'
@@ -220,7 +218,7 @@ The next example shows how to use a value from the function when setting a tag v
 param utcShort string = utcNow('d')
 param rgName string
 
-resource myRg 'Microsoft.Resources/resourceGroups@2020-10-01' = {
+resource myRg 'Microsoft.Resources/resourceGroups@2022-09-01' = {
   name: rgName
   location: 'westeurope'
   tags: {

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

@@ -1,12 +1,11 @@
 ---
 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.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 04/26/2022
+ms.date: 06/23/2023
 ---
+
 # Comparing JSON and Bicep for templates
 
 This article compares Bicep syntax with JSON syntax for Azure Resource Manager templates (ARM templates). In most cases, Bicep provides syntax that is less verbose than the equivalent in JSON.
@@ -135,7 +134,7 @@ targetScope = 'subscription'
 To declare a resource:
 
 ```bicep
-resource virtualMachine 'Microsoft.Compute/virtualMachines@2020-06-01' = {
+resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   ...
 }
 ```
@@ -153,7 +152,7 @@ resource virtualMachine 'Microsoft.Compute/virtualMachines@2020-06-01' = {
 To conditionally deploy a resource:
 
 ```bicep
-resource virtualMachine 'Microsoft.Compute/virtualMachines@2020-06-01' = if(deployVM) {
+resource virtualMachine 'Microsoft.Compute/virtualMachines@2023-03-01' = if(deployVM) {
   ...
 }
 ```
@@ -163,7 +162,7 @@ resource virtualMachine 'Microsoft.Compute/virtualMachines@2020-06-01' = if(depl
   {
     "condition": "[parameters('deployVM')]",
     "type": "Microsoft.Compute/virtualMachines",
-    "apiVersion": "2020-06-01",
+    "apiVersion": "2023-03-01",
     ...
   }
 ]
@@ -214,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@2020-06-01' = {
+resource netSecurityGroup 'Microsoft.Network/networkSecurityGroups@2022-11-01' = {
   ...
 }
 
-resource nic1 'Microsoft.Network/networkInterfaces@2020-06-01' = {
+resource nic1 'Microsoft.Network/networkInterfaces@2022-11-01' = {
   name: nic1Name
   location: location
   properties: {
@@ -255,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@2019-06-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
   name: storageAccountName
 }
 

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

@@ -6,7 +6,7 @@ author: johndowns
 ms.author: jodowns
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 03/27/2022
+ms.date: 06/23/2023
 ---
 
 # Contribute to Bicep

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

@@ -3,7 +3,7 @@ title: Use Bicep to deploy resources to management group
 description: Describes how to create a Bicep file that deploys resources at the management group scope.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/22/2021
+ms.date: 06/23/2023
 ---
 
 # Management group deployments with Bicep files
@@ -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@2019-09-01' = {
+resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2021-06-01' = {
   ...
 }
 ```
@@ -211,7 +211,7 @@ targetScope = 'managementGroup'
 
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
-resource newMG 'Microsoft.Management/managementGroups@2020-05-01' = {
+resource newMG 'Microsoft.Management/managementGroups@2021-04-01' = {
   scope: tenant()
   name: mgName
   properties: {}
@@ -227,7 +227,7 @@ targetScope = 'managementGroup'
 
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
-resource newMG 'Microsoft.Management/managementGroups@2020-05-01' = {
+resource newMG 'Microsoft.Management/managementGroups@2021-04-01' = {
   scope: tenant()
   name: mgName
   properties: {
@@ -268,7 +268,7 @@ param allowedLocations array = [
   'australiacentral'
 ]
 
-resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2020-09-01' = {
+resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2021-06-01' = {
   name: 'locationRestriction'
   properties: {
     policyType: 'Custom'
@@ -288,7 +288,7 @@ resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2020-09-01'
   }
 }
 
-resource policyAssignment 'Microsoft.Authorization/policyAssignments@2020-09-01' = {
+resource policyAssignment 'Microsoft.Authorization/policyAssignments@2022-06-01' = {
   name: 'locationAssignment'
   properties: {
     policyDefinitionId: policyDefinition.id

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

@@ -3,7 +3,7 @@ title: Use Bicep to deploy resources to subscription
 description: Describes how to create a Bicep file that deploys resources to the Azure subscription scope. It shows how to create a resource group.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/22/2021
+ms.date: 06/23/2023
 ---
 
 # Subscription deployments with Bicep files
@@ -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@2020-10-01' = {
+resource exampleResource 'Microsoft.Resources/resourceGroups@2022-09-01' = {
   ...
 }
 ```
@@ -229,7 +229,7 @@ targetScope = 'subscription'
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
 // management group created at tenant
-resource managementGroup 'Microsoft.Management/managementGroups@2020-05-01' = {
+resource managementGroup 'Microsoft.Management/managementGroups@2021-04-01' = {
   scope: tenant()
   name: mgName
   properties: {}
@@ -254,7 +254,7 @@ targetScope='subscription'
 param resourceGroupName string
 param resourceGroupLocation string
 
-resource newRG 'Microsoft.Resources/resourceGroups@2021-01-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
 }
@@ -274,7 +274,7 @@ param resourceGroupLocation string
 param storageName string
 param storageLocation string
 
-resource newRG 'Microsoft.Resources/resourceGroups@2021-01-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
 }
@@ -295,7 +295,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@2019-06-01' = {
+resource storageAcct 'Microsoft.Storage/storageAccounts@2022-09-01' = {
   name: storageName
   location: storageLocation
   sku: {
@@ -319,7 +319,7 @@ param policyDefinitionID string
 param policyName string
 param policyParameters object = {}
 
-resource policyAssign 'Microsoft.Authorization/policyAssignments@2020-09-01' = {
+resource policyAssign 'Microsoft.Authorization/policyAssignments@2022-06-01' = {
   name: policyName
   properties: {
     policyDefinitionId: policyDefinitionID
@@ -335,7 +335,7 @@ You can [define](../../governance/policy/concepts/definition-structure.md) and a
 ```bicep
 targetScope = 'subscription'
 
-resource locationPolicy 'Microsoft.Authorization/policyDefinitions@2020-09-01' = {
+resource locationPolicy 'Microsoft.Authorization/policyDefinitions@2021-06-01' = {
   name: 'locationpolicy'
   properties: {
     policyType: 'Custom'
@@ -352,7 +352,7 @@ resource locationPolicy 'Microsoft.Authorization/policyDefinitions@2020-09-01' =
   }
 }
 
-resource locationRestrict 'Microsoft.Authorization/policyAssignments@2020-09-01' = {
+resource locationRestrict 'Microsoft.Authorization/policyAssignments@2022-06-01' = {
   name: 'allowedLocation'
   properties: {
     policyDefinitionId: locationPolicy.id
@@ -386,7 +386,7 @@ param roleAssignmentName string = guid(principalId, roleDefinitionId, resourceGr
 
 var roleID = '/subscriptions/${subscription().subscriptionId}/providers/Microsoft.Authorization/roleDefinitions/${roleDefinitionId}'
 
-resource newResourceGroup 'Microsoft.Resources/resourceGroups@2019-10-01' = {
+resource newResourceGroup 'Microsoft.Resources/resourceGroups@2022-09-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
   properties: {}
@@ -411,7 +411,7 @@ module assignRole 'role.bicep' = {
 The following example shows the module to apply the lock:
 
 ```bicep
-resource createRgLock 'Microsoft.Authorization/locks@2016-09-01' = {
+resource createRgLock 'Microsoft.Authorization/locks@2020-05-01' = {
   name: 'rgLock'
   properties: {
     level: 'CanNotDelete'
@@ -431,7 +431,7 @@ param roleNameGuid string = newGuid()
 
 param roleDefinitionId string
 
-resource roleNameGuid_resource 'Microsoft.Authorization/roleAssignments@2020-04-01-preview' = {
+resource roleNameGuid_resource 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
   name: roleNameGuid
   properties: {
     roleDefinitionId: roleDefinitionId

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: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/22/2021
+ms.date: 06/23/2023
 ---
 
 # 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@2020-02-01' = {
+resource mgName_resource 'Microsoft.Management/managementGroups@2021-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@2020-02-01' = {
+resource mgName_resource 'Microsoft.Management/managementGroups@2021-04-01' = {
   name: mgName
   properties: {}
 }
@@ -226,7 +226,7 @@ param roleDefinitionId string = '8e3af657-a8ff-443c-a75c-2fe8c4bcb635'
 
 var roleAssignmentName = guid(principalId, roleDefinitionId)
 
-resource roleAssignment 'Microsoft.Authorization/roleAssignments@2020-03-01-preview' = {
+resource roleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
   name: roleAssignmentName
   properties: {
     roleDefinitionId: tenantResourceId('Microsoft.Authorization/roleDefinitions', roleDefinitionId)

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

@@ -3,7 +3,7 @@ title: Reference existing resource in Bicep
 description: Describes how to reference a resource that already exists.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 02/04/2022
+ms.date: 06/23/2023
 ---
 
 # Existing resources in Bicep
@@ -17,7 +17,7 @@ The resource isn't redeployed when referenced with the `existing` keyword.
 The following example gets an existing storage account in the same resource group as the current deployment. Notice that you provide only the name of the existing resource. The properties are available through the symbolic name.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
   name: 'examplestorage'
 }
 
@@ -29,7 +29,7 @@ output blobEndpoint string = stg.properties.primaryEndpoints.blob
 Set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
   name: 'examplestorage'
   scope: resourceGroup(exampleRG)
 }