Merge pull request #280657 from mumian/0711-merge-repo-p

v-dirichards · web-flow · commit a9372e37e338 · 2024-07-12T09:49:34.000-05:00
update api versions
diff --git a/articles/azure-resource-manager/bicep/linter-rule-no-deployments-resources.md b/articles/azure-resource-manager/bicep/linter-rule-no-deployments-resources.md
@@ -37,7 +37,7 @@ In ARM templates, you can reuse or modularize a template through nesting or link
   "resources": [
     {
       "type": "Microsoft.Resources/deployments",
-      "apiVersion": "2022-09-01",
+      "apiVersion": "2024-03-01",
       "name": "nestedTemplate1",
       "properties": {
         "mode": "Incremental",
diff --git a/articles/azure-resource-manager/bicep/msbuild-bicep-file.md b/articles/azure-resource-manager/bicep/msbuild-bicep-file.md
@@ -478,7 +478,7 @@ Run MSBuild to convert the Bicep file and the Bicep parameter file to JSON.
       "resources": [
         {
           "type": "Microsoft.Storage/storageAccounts",
-          "apiVersion": "2022-05-01",
+          "apiVersion": "2023-04-01",
           "name": "[variables('storageAccountName')]",
           "location": "[parameters('location')]",
           "sku": {
diff --git a/articles/azure-resource-manager/bicep/patterns-configuration-set.md b/articles/azure-resource-manager/bicep/patterns-configuration-set.md
@@ -7,6 +7,7 @@ ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 06/23/2023
 ---
+
 # Configuration set pattern
 
 Rather than define lots of individual parameters, create predefined sets of values. During deployment, select the set of values to use.
diff --git a/articles/azure-resource-manager/bicep/patterns-logical-parameter.md b/articles/azure-resource-manager/bicep/patterns-logical-parameter.md
@@ -7,6 +7,7 @@ ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 06/23/2023
 ---
+
 # Logical parameter pattern
 
 Use parameters to specify the logical definition of a resource, or even of multiple resources. The Bicep file converts the logical parameter to deployable resource definitions. By following this pattern, you can separate *what's* deployed from *how* it's deployed.
diff --git a/articles/azure-resource-manager/bicep/patterns-name-generation.md b/articles/azure-resource-manager/bicep/patterns-name-generation.md
@@ -7,6 +7,7 @@ ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 06/23/2023
 ---
+
 # Name generation pattern
 
 Within your Bicep files, use string interpolation and Bicep functions to create resource names that are unique, deterministic, meaningful, and different for each environment that you deploy to.
diff --git a/articles/azure-resource-manager/bicep/patterns-shared-variable-file.md b/articles/azure-resource-manager/bicep/patterns-shared-variable-file.md
@@ -7,6 +7,7 @@ ms.topic: conceptual
 ms.custom: devx-track-bicep
 ms.date: 07/28/2023
 ---
+
 # Shared variable file pattern
 
 Reduce the repetition of shared values in your Bicep files. Instead, load those values from a shared JSON file within your Bicep file. When using arrays, concatenate the shared values with deployment-specific values in your Bicep code.
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md b/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio-code.md
@@ -179,7 +179,7 @@ When finished, you have:
 @maxLength(24)
 param storageAccountName string = 'store${uniqueString(resourceGroup().id)}'
 
-resource virtualNetwork 'Microsoft.Network/virtualNetworks@2019-11-01' = {
+resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
   name: 'exampleVNet'
   location: resourceGroup().location
   properties: {
@@ -205,7 +205,7 @@ resource virtualNetwork 'Microsoft.Network/virtualNetworks@2019-11-01' = {
   }
 }
 
-resource exampleStorage 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+resource exampleStorage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountName
   location: 'eastus'
   sku: {
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md b/articles/azure-resource-manager/bicep/quickstart-create-bicep-use-visual-studio.md
@@ -36,7 +36,7 @@ In *main.bicep*, type **vnet**. Select **res-vnet** from the list, and then pres
 Your Bicep file now contains the following code:
 
 ```bicep
-resource virtualNetwork 'Microsoft.Network/virtualNetworks@2019-11-01' = {
+resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
   name: 'name'
   location: location
   properties: {
@@ -147,7 +147,7 @@ After the single quote for the resource type, add `=` and a space. You're presen
 This option adds all of the properties for the resource type that are required for deployment. After selecting this option, your storage account has the following properties:
 
 ```bicep
-resource exampleStorage 'Microsoft.Storage/storageAccounts@2021-09-01' = {
+resource exampleStorage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 	name: 1
 	location: 2
 	sku: {
@@ -168,7 +168,7 @@ When you've finished, you have:
 param storageName string
 param location string = resourceGroup().location
 
-resource virtualNetwork 'Microsoft.Network/virtualNetworks@2019-11-01' = {
+resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
   name: storageName
   location: location
   properties: {
@@ -194,7 +194,7 @@ resource virtualNetwork 'Microsoft.Network/virtualNetworks@2019-11-01' = {
   }
 }
 
-resource exampleStorage 'Microsoft.Storage/storageAccounts@2021-09-01' = {
+resource exampleStorage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageName
   location: location
   sku: {
diff --git a/articles/azure-resource-manager/bicep/quickstart-create-template-specs.md b/articles/azure-resource-manager/bicep/quickstart-create-template-specs.md
@@ -44,7 +44,7 @@ param location string = resourceGroup().location
 
 var storageAccountName = 'storage${uniqueString(resourceGroup().id)}'
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountName
   location: location
   sku: {
@@ -165,7 +165,7 @@ You can create a template spec with a Bicep file but the `mainTemplate` must be
           'resources': [
             {
               'type': 'Microsoft.Storage/storageAccounts'
-              'apiVersion': '2022-09-01'
+              'apiVersion': '2023-04-01'
               'name': '[variables(\'storageAccountName\')]'
               'location': '[parameters(\'location\')]'
               'sku': {
@@ -526,7 +526,7 @@ Rather than create a new template spec for the revised template, add a new versi
           'resources': [
             {
               'type': 'Microsoft.Storage/storageAccounts'
-              'apiVersion': '2022-09-01'
+              'apiVersion': '2023-04-01'
               'name': '[variables(\'storageAccountName\')]'
               'location': '[parameters(\'location\')]'
               'sku': {
diff --git a/articles/azure-resource-manager/bicep/quickstart-private-module-registry.md b/articles/azure-resource-manager/bicep/quickstart-private-module-registry.md
@@ -45,7 +45,7 @@ param location string
 
 var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 
-resource stg 'Microsoft.Storage/storageAccounts@2021-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: uniqueStorageName
   location: location
   sku: {
diff --git a/articles/azure-resource-manager/bicep/resource-declaration.md b/articles/azure-resource-manager/bicep/resource-declaration.md
@@ -23,7 +23,7 @@ resource <symbolic-name> '<full-type-name>@<api-version>' = {
 So, a declaration for a storage account can start with:
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2021-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   ...
 }
 ```
@@ -64,7 +64,7 @@ resource <symbolic-name> '<full-type-name>@<api-version>' = {
 Each resource has a name. When setting the resource name, pay attention to the [rules and restrictions for resource names](../management/resource-name-rules.md).
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: 'examplestorage'
   ...
 }
@@ -77,7 +77,7 @@ Typically, you'd set the name to a parameter so you can pass in different values
 @maxLength(24)
 param storageAccountName string
 
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountName
   ...
 }
@@ -88,7 +88,7 @@ resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
 Many resources require a location. You can determine if the resource needs a location either through intellisense or [template reference](/azure/templates/). The following example adds a location parameter that is used for the storage account.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: 'examplestorage'
   location: 'eastus'
   ...
@@ -100,7 +100,7 @@ Typically, you'd set location to a parameter so you can deploy to different loca
 ```bicep
 param location string = resourceGroup().location
 
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: 'examplestorage'
   location: location
   ...
@@ -140,7 +140,7 @@ You can use either system-assigned or user-assigned identities.
 The following example shows how to configure a system-assigned identity for an Azure Kubernetes Service cluster.
 
 ```bicep
-resource aks 'Microsoft.ContainerService/managedClusters@2020-09-01' = {
+resource aks 'Microsoft.ContainerService/managedClusters@2024-02-01' = {
   name: clusterName
   location: location
   tags: tags
@@ -154,7 +154,7 @@ The next example shows how to configure a user-assigned identity for a virtual m
 ```bicep
 param userAssignedIdentity string
 
-resource vm 'Microsoft.Compute/virtualMachines@2020-06-01' = {
+resource vm 'Microsoft.Compute/virtualMachines@2024-03-01' = {
   name: vmName
   location: location
   identity: {
@@ -172,7 +172,7 @@ The preceding properties are generic to most resource types. After setting those
 Use intellisense or [Bicep resource reference](/azure/templates/) to determine which properties are available and which ones are required. The following example sets the remaining properties for a storage account.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: 'examplestorage'
   location: 'eastus'
   sku: {
diff --git a/articles/azure-resource-manager/bicep/resource-dependencies.md b/articles/azure-resource-manager/bicep/resource-dependencies.md
@@ -17,12 +17,12 @@ Azure Resource Manager evaluates the dependencies between resources, and deploys
 An implicit dependency is created when one resource declaration references another resource in the same deployment. In the following example, `otherResource` gets a property from  `exampleDnsZone`. The resource named `otherResource` is implicitly dependent on `exampleDnsZone`.
 
 ```bicep
-resource exampleDnsZone 'Microsoft.Network/dnszones@2018-05-01' = {
+resource exampleDnsZone 'Microsoft.Network/dnsZones@2023-07-01-preview' = {
   name: 'myZone'
   location: 'global'
 }
 
-resource otherResource 'Microsoft.Example/examples@2023-05-01' = {
+resource otherResource 'Microsoft.Example/examples@2024-05-01' = {
   name: 'exampleResource'
   properties: {
     // get read-only DNS zone property
@@ -34,7 +34,7 @@ resource otherResource 'Microsoft.Example/examples@2023-05-01' = {
 A nested resource also has an implicit dependency on its containing resource.
 
 ```bicep
-resource myParent 'My.Rp/parentType@2023-05-01' = {
+resource myParent 'My.Rp/parentType@2024-05-01' = {
   name: 'myParent'
   location: 'West US'
 
@@ -62,12 +62,12 @@ An explicit dependency is declared with the `dependsOn` property. The property a
 The following example shows a DNS zone named `otherZone` that depends on a DNS zone named `dnsZone`:
 
 ```bicep
-resource dnsZone 'Microsoft.Network/dnszones@2018-05-01' = {
+resource dnsZone 'Microsoft.Network/dnszones@2023-07-01-preview' = {
   name: 'demoeZone1'
   location: 'global'
 }
 
-resource otherZone 'Microsoft.Network/dnszones@2018-05-01' = {
+resource otherZone 'Microsoft.Network/dnszones@2023-07-01-preview' = {
   name: 'demoZone2'
   location: 'global'
   dependsOn: [
diff --git a/articles/azure-resource-manager/bicep/scenarios-secrets.md b/articles/azure-resource-manager/bicep/scenarios-secrets.md
@@ -67,7 +67,7 @@ When you use Bicep modules, you can provide secure parameters by using [the `get
 You can also reference a key vault defined in another resource group by using the `existing` and `scope` keywords together. In the following example, the Bicep file is deployed to a resource group named *Networking*. The value for the module's parameter *mySecret* is defined in a key vault named *contosonetworkingsecrets* located in the *Secrets* resource group:
 
 ```bicep
-resource networkingSecretsKeyVault 'Microsoft.KeyVault/vaults@2019-09-01' existing = {
+resource networkingSecretsKeyVault 'Microsoft.KeyVault/vaults@2023-07-01' existing = {
   scope: resourceGroup('Secrets')
   name: 'contosonetworkingsecrets'
 }
diff --git a/articles/azure-resource-manager/bicep/scope-extension-resources.md b/articles/azure-resource-manager/bicep/scope-extension-resources.md
@@ -28,7 +28,7 @@ To apply an extension resource type at the target deployment scope, add the reso
 When deployed to a resource group, the following template adds a lock to that resource group.
 
 ```bicep
-resource createRgLock 'Microsoft.Authorization/locks@2016-09-01' = {
+resource createRgLock 'Microsoft.Authorization/locks@2020-05-01' = {
   name: 'rgLock'
   properties: {
     level: 'CanNotDelete'
@@ -59,7 +59,7 @@ var role = {
   Reader: '/subscriptions/${subscription().subscriptionId}/providers/Microsoft.Authorization/roleDefinitions/acdd72a7-3385-48ef-bd42-f606fba81ae7'
 }
 
-resource roleAssignSub 'Microsoft.Authorization/roleAssignments@2020-04-01-preview' = {
+resource roleAssignSub 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
   name: guid(subscription().id, principalId, role[builtInRoleType])
   properties: {
     roleDefinitionId: role[builtInRoleType]
@@ -95,7 +95,7 @@ var role = {
 }
 var uniqueStorageName = 'storage${uniqueString(resourceGroup().id)}'
 
-resource demoStorageAcct 'Microsoft.Storage/storageAccounts@2019-04-01' = {
+resource demoStorageAcct 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -105,7 +105,7 @@ resource demoStorageAcct 'Microsoft.Storage/storageAccounts@2019-04-01' = {
   properties: {}
 }
 
-resource roleAssignStorage 'Microsoft.Authorization/roleAssignments@2020-04-01-preview' = {
+resource roleAssignStorage 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
   name: guid(demoStorageAcct.id, principalId, role[builtInRoleType])
   properties: {
     roleDefinitionId: role[builtInRoleType]
@@ -118,11 +118,11 @@ resource roleAssignStorage 'Microsoft.Authorization/roleAssignments@2020-04-01-p
 You can apply an extension resource to an existing resource. The following example adds a lock to an existing storage account.
 
 ```bicep
-resource demoStorageAcct 'Microsoft.Storage/storageAccounts@2021-04-01' existing = {
+resource demoStorageAcct 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
   name: 'examplestore'
 }
 
-resource createStorageLock 'Microsoft.Authorization/locks@2016-09-01' = {
+resource createStorageLock 'Microsoft.Authorization/locks@2020-05-01' = {
   name: 'storeLock'
   scope: demoStorageAcct
   properties: {
@@ -162,12 +162,12 @@ The following example shows how to apply a lock on a storage account that reside
 
     ```bicep
     param storageAccountName string
-
-    resource storage 'Microsoft.Storage/storageAccounts@2021-09-01' existing = {
+    
+    resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
       name: storageAccountName
     }
-
-    resource storeLock 'Microsoft.Authorization/locks@2017-04-01' = {
+    
+    resource storeLock 'Microsoft.Authorization/locks@2020-05-01' = {
       scope: storage
       name: 'storeLock'
       properties: {
diff --git a/articles/azure-resource-manager/bicep/template-specs.md b/articles/azure-resource-manager/bicep/template-specs.md
@@ -67,7 +67,7 @@ The following example shows a simple Bicep file for creating a storage account i
 ])
 param storageAccountType string = 'Standard_LRS'
 
-resource stg 'Microsoft.Storage/storageAccounts@2021-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name:  'store${uniqueString(resourceGroup().id)}'
   location: resourceGroup().location
   sku: {
@@ -105,7 +105,7 @@ param templateSpecName string = 'CreateStorageAccount'
 param templateSpecVersionName string = '0.1'
 param location string = resourceGroup().location
 
-resource createTemplateSpec 'Microsoft.Resources/templateSpecs@2021-05-01' = {
+resource createTemplateSpec 'Microsoft.Resources/templateSpecs@2022-02-01' = {
   name: templateSpecName
   location: location
   properties: {
@@ -114,7 +114,7 @@ resource createTemplateSpec 'Microsoft.Resources/templateSpecs@2021-05-01' = {
   }
 }
 
-resource createTemplateSpecVersion 'Microsoft.Resources/templateSpecs/versions@2021-05-01' = {
+resource createTemplateSpecVersion 'Microsoft.Resources/templateSpecs/versions@2022-02-01' = {
   parent: createTemplateSpec
   name: templateSpecVersionName
   location: location
@@ -137,7 +137,7 @@ resource createTemplateSpecVersion 'Microsoft.Resources/templateSpecs/versions@2
       'resources': [
         {
           'type': 'Microsoft.Storage/storageAccounts'
-          'apiVersion': '2019-06-01'
+          'apiVersion': '2023-04-01'
           'name': 'store$uniquestring(resourceGroup().id)'
           'location': resourceGroup().location
           'kind': 'StorageV2'
@@ -149,7 +149,6 @@ resource createTemplateSpecVersion 'Microsoft.Resources/templateSpecs/versions@2
     }
   }
 }
-
 ```
 
 The JSON template embedded in the Bicep file needs to make these changes:
@@ -309,7 +308,6 @@ az deployment group create \
 
     For more information, see [Bicep parameters file](./parameter-files.md).
 
-
     To pass parameter file with:
 
     # [PowerShell](#tab/azure-powershell)
@@ -328,10 +326,8 @@ az deployment group create \
 
     ---
 
-
 - Use JSON parameters file
 
-
     The following JSON is a sample JSON parameters file:
 
     ```json
diff --git a/articles/azure-resource-manager/bicep/user-defined-data-types.md b/articles/azure-resource-manager/bicep/user-defined-data-types.md
diff --git a/articles/azure-resource-manager/bicep/visual-studio-code.md b/articles/azure-resource-manager/bicep/visual-studio-code.md

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ In ARM templates, you can reuse or modularize a template through nesting or link`
`37`	`37`	`"resources": [`
`38`	`38`	`{`
`39`	`39`	`"type": "Microsoft.Resources/deployments",`
`40`		`- "apiVersion": "2022-09-01",`
	`40`	`+ "apiVersion": "2024-03-01",`
`41`	`41`	`"name": "nestedTemplate1",`
`42`	`42`	`"properties": {`
`43`	`43`	`"mode": "Incremental",`
Original file line number	Diff line number	Diff line change
`@@ -478,7 +478,7 @@ Run MSBuild to convert the Bicep file and the Bicep parameter file to JSON.`
`478`	`478`	`"resources": [`
`479`	`479`	`{`
`480`	`480`	`"type": "Microsoft.Storage/storageAccounts",`
`481`		`- "apiVersion": "2022-05-01",`
	`481`	`+ "apiVersion": "2023-04-01",`
`482`	`482`	`"name": "[variables('storageAccountName')]",`
`483`	`483`	`"location": "[parameters('location')]",`
`484`	`484`	`"sku": {`