Merge pull request #280637 from mumian/0711-merge-repo-linter

update api versions and remove the sample repo

Author: v-dirichards

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: 06/23/2023
+ms.date: 07/11/2024
 ---
 
 # 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@2022-09-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-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@2022-09-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
   name: 'examplestorage'
   scope: resourceGroup(exampleRG)
 }

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

@@ -3,7 +3,7 @@ title: Bicep file structure and syntax
 description: Describes the structure and properties of a Bicep file using declarative syntax.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/03/2024
+ms.date: 07/11/2024
 ---
 
 # Understand the structure and syntax of Bicep files
@@ -61,7 +61,7 @@ param location string = resourceGroup().location
 
 var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 
-resource stg 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -118,7 +118,7 @@ param storageAccountConfig storageAccountConfigType = {
   sku: 'Standard_LRS'
 }
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountConfig.name
   location: location
   sku: {
@@ -189,7 +189,7 @@ var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 Apply this variable wherever you need the complex expression.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: uniqueStorageName
 ```
 
@@ -202,7 +202,7 @@ Use the `resource` keyword to define a resource to deploy. Your resource declara
 The resource declaration includes the resource type and API version. Within the body of the resource declaration, include properties that are specific to the resource type.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2019-06-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -255,7 +255,7 @@ By default, resources are deployed in parallel. When you add the `batchSize(int)
 
 ```bicep
 @batchSize(3)
-resource storageAccountResources 'Microsoft.Storage/storageAccounts@2019-06-01' = [for storageName in storageAccounts: {
+resource storageAccountResources 'Microsoft.Storage/storageAccounts@2023-04-01' = [for storageName in storageAccounts: {
   ...
 }]
 ```
@@ -305,7 +305,7 @@ You can add a resource or module to your Bicep file that is conditionally deploy
 ```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'
 }
@@ -320,15 +320,15 @@ Spaces and tabs are ignored when authoring Bicep files.
 Bicep is newline sensitive. For example:
 
 ```bicep
-resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' = if (newOrExisting == 'new') {
+resource sa 'Microsoft.Storage/storageAccounts@2023-04-01' = if (newOrExisting == 'new') {
   ...
 }
 ```
 
 Can't be written as:
 
 ```bicep
-resource sa 'Microsoft.Storage/storageAccounts@2019-06-01' =
+resource sa 'Microsoft.Storage/storageAccounts@2023-04-01' =
     if (newOrExisting == 'new') {
       ...
     }
@@ -344,8 +344,8 @@ The following example shows a single-line comment.
 
 ```bicep
 // This is your primary NIC.
-resource nic1 'Microsoft.Network/networkInterfaces@2020-06-01' = {
-   ...
+resource nic1 'Microsoft.Network/networkInterfaces@2023-11-01' = {
+  ...
 }
 ```
 

articles/azure-resource-manager/bicep/linter-rule-explicit-values-for-loc-params.md

@@ -3,7 +3,7 @@ title: Linter rule - use explicit values for module location parameters
 description: Linter rule - use explicit values for module location parameters.
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - use explicit values for module location parameters
@@ -35,7 +35,7 @@ module m1 'module1.bicep' = {
  name: 'm1'
 }
 
-resource storageaccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource storageaccount 'Microsoft.Storage/storageAccounts@2024-03-01' = {
   name: 'storageaccount'
   location: location
   kind: 'StorageV2'
@@ -50,7 +50,7 @@ resource storageaccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
 ```bicep
 param location string = resourceGroup().location
 
-resource stg 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2024-03-01' = {
   name: 'stg'
   location: location
   kind: 'StorageV2'
@@ -74,7 +74,7 @@ module m1 'module1.bicep' = {
   }
 }
 
-resource storageaccount 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource storageaccount 'Microsoft.Storage/storageAccounts@2024-03-01' = {
   name: 'storageaccount'
   location: location
   kind: 'StorageV2'

articles/azure-resource-manager/bicep/linter-rule-nested-deployment-template-scoping.md

@@ -3,7 +3,7 @@ title: Linter rule - nested deployment template scoping
 description: Linter rule - nested deployment template scoping
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - nested deployment template scoping
@@ -23,7 +23,7 @@ The following example fails this test because `fizz` is defined in the parent te
 ```bicep
 var fizz = 'buzz'
 
-resource nested 'Microsoft.Resources/deployments@2020-10-01' = {
+resource nested 'Microsoft.Resources/deployments@2024-03-01' = {
   name: 'name'
   properties: {
     mode: 'Incremental'
@@ -35,7 +35,7 @@ resource nested 'Microsoft.Resources/deployments@2020-10-01' = {
       contentVersion: '1.0.0.0'
       resources: [
         {
-          apiVersion: '2022-09-01'
+          apiVersion: '2024-03-01'
           type: 'Microsoft.Resources/tags'
           name: 'default'
           properties: {

articles/azure-resource-manager/bicep/linter-rule-no-deployments-resources.md

@@ -3,7 +3,7 @@ title: Linter rule - no deployments resources
 description: Linter rule - no deployments resources
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - no deployments resources
@@ -47,7 +47,7 @@ In ARM templates, you can reuse or modularize a template through nesting or link
           "resources": [
             {
               "type": "Microsoft.Storage/storageAccounts",
-              "apiVersion": "2023-01-01",
+              "apiVersion": "2023-04-01",
               "name": "[parameters('storageAccountName')]",
               "location": "[parameters('location')]",
               "sku": {
@@ -69,7 +69,7 @@ In Bicep, you can still use the `Microsoft.Resources/deployments` resource for n
 param storageAccountName string = 'store${uniqueString(resourceGroup().id)}'
 param location string = resourceGroup().location
 
-resource nestedTemplate1 'Microsoft.Resources/deployments@2023-07-01' = {
+resource nestedTemplate1 'Microsoft.Resources/deployments@2024-03-01' = {
   name: 'nestedTemplate1'
   properties:{
     mode: 'Incremental'
@@ -79,7 +79,7 @@ resource nestedTemplate1 'Microsoft.Resources/deployments@2023-07-01' = {
       resources: [
         {
           type: 'Microsoft.Storage/storageAccounts'
-          apiVersion: '2023-01-01'
+          apiVersion: '2023-04-01'
           name: storageAccountName
           location: location
           sku: {
@@ -116,7 +116,7 @@ _nested_nestedTemplate1.bicep_:
 param storageAccountName string
 param location string
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountName
   location: location
   sku: {
@@ -162,7 +162,7 @@ _createStorage.json_:
   "resources": [
     {
       "type": "Microsoft.Storage/storageAccounts",
-      "apiVersion": "2023-01-01",
+      "apiVersion": "2023-04-01",
       "name": "[parameters('storageAccountName')]",
       "location": "[parameters('location')]",
       "sku": {

articles/azure-resource-manager/bicep/linter-rule-no-hardcoded-environment-urls.md

@@ -3,7 +3,7 @@ title: Linter rule - no hardcoded environment URL
 description: Linter rule - no hardcoded environment URL
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - no hardcoded environment URL
@@ -45,7 +45,7 @@ In some cases, you can fix it by getting a property from a resource you've deplo
 param storageAccountName string
 param location string = resourceGroup().location
 
-resource sa 'Microsoft.Storage/storageAccounts@2022-09-01' = {
+resource sa 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: storageAccountName
   location: location
   sku: {

articles/azure-resource-manager/bicep/linter-rule-no-hardcoded-location.md

@@ -3,7 +3,7 @@ title: Linter rule - no hardcoded locations
 description: Linter rule - no hardcoded locations
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - no hardcoded locations
@@ -25,7 +25,7 @@ Rather than using a hardcoded string or variable value, use a parameter, the str
 The following example fails this test because the resource's `location` property uses a string literal:
 
 ```bicep
-  resource stg 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
       location: 'westus'
   }
 ```
@@ -34,7 +34,7 @@ You can fix it by creating a new `location` string parameter (which may optional
 
 ```bicep
   param location string = resourceGroup().location
-  resource stg 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
       location: location
   }
 ```
@@ -47,7 +47,7 @@ The following example fails this test because the resource's `location` property
 
 ```bicep
   var location = 'westus'
-  resource stg 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
       location: location
   }
 ```
@@ -56,7 +56,7 @@ You can fix it by turning the variable into a parameter:
 
 ```bicep
   param location string = 'westus'
-  resource stg 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+  resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
       location: location
   }
 ```
@@ -77,7 +77,7 @@ where module1.bicep is:
 ```bicep
 param location string
 
-resource storageaccount 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+resource storageaccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   name: 'storageaccount'
   location: location
   kind: 'StorageV2'

articles/azure-resource-manager/bicep/linter-rule-no-loc-expr-outside-params.md

@@ -3,7 +3,7 @@ title: Linter rule - no location expressions outside of parameter default values
 description: Linter rule - no location expressions outside of parameter default values
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - no location expressions outside of parameter default values
@@ -25,7 +25,7 @@ Template users may have limited access to regions where they can create resource
 Best practice suggests that to set your resources' locations, your template should have a string parameter named `location`. If you default the `location` parameter to `resourceGroup().location` or `deployment().location` instead of using these functions elsewhere in the template, users of the template can use the default value when convenient but also specify a different location when needed.
 
 ```bicep
-resource storageaccount 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+resource storageaccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   location: resourceGroup().location
 }
 ```
@@ -35,7 +35,7 @@ You can fix the failure by creating a `location` property that defaults to `reso
 ```bicep
 param location string = resourceGroup().location
 
-resource storageaccount 'Microsoft.Storage/storageAccounts@2021-02-01' = {
+resource storageaccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   location: location
 }
 ```

articles/azure-resource-manager/bicep/linter-rule-no-unnecessary-dependson.md

@@ -3,7 +3,7 @@ title: Linter rule - no unnecessary dependsOn entries
 description: Linter rule - no unnecessary dependsOn entries
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - no unnecessary dependsOn entries
@@ -25,7 +25,7 @@ The following example fails this test because the dependsOn entry `appServicePla
 ```bicep
 param location string = resourceGroup().location
 
-resource appServicePlan 'Microsoft.Web/serverfarms@2022-03-01' = {
+resource appServicePlan 'Microsoft.Web/serverfarms@2023-12-01' = {
   name: 'name'
   location: location
   sku: {
@@ -34,7 +34,7 @@ resource appServicePlan 'Microsoft.Web/serverfarms@2022-03-01' = {
   }
 }
 
-resource webApplication 'Microsoft.Web/sites@2022-03-01' = {
+resource webApplication 'Microsoft.Web/sites@2023-12-01' = {
   name: 'name'
   location: location
   properties: {
@@ -51,7 +51,7 @@ You can fix it by removing the unnecessary dependsOn entry.
 ```bicep
 param location string = resourceGroup().location
 
-resource appServicePlan 'Microsoft.Web/serverfarms@2022-03-01' = {
+resource appServicePlan 'Microsoft.Web/serverfarms@2023-12-01' = {
   name: 'name'
   location: location
   sku: {
@@ -60,7 +60,7 @@ resource appServicePlan 'Microsoft.Web/serverfarms@2022-03-01' = {
   }
 }
 
-resource webApplication 'Microsoft.Web/sites@2022-03-01' = {
+resource webApplication 'Microsoft.Web/sites@2023-12-01' = {
   name: 'name'
   location: location
   properties: {

articles/azure-resource-manager/bicep/linter-rule-no-unused-existing-resources.md

@@ -3,7 +3,7 @@ title: Linter rule - no unused existing resources
 description: Linter rule - no unused existing resources
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 07/11/2024
 ---
 
 # Linter rule - no unused existing resources
@@ -23,7 +23,7 @@ To reduce confusion in your template, delete any [existing resources](./existing
 The following example fails this test because the existing resource **stg** is declared but never used:
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
   name: 'examplestorage'
 }
 ```