Bicep content freshness - 1

Author: mumian

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

@@ -3,7 +3,7 @@ title: Bicep functions - any
 description: Describes the any function that is available in Bicep to convert types.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/09/2021
+ms.date: 06/23/2023
 ---
 
 # Any function for Bicep
@@ -38,7 +38,7 @@ The value in a form that is compatible with any data type.
 The following example shows how to use the `any()` function to provide numeric values as strings.
 
 ```bicep
-resource wpAci 'microsoft.containerInstance/containerGroups@2019-12-01' = {
+resource wpAci 'Microsoft.ContainerInstance/containerGroups@2023-05-01' = {
   name: 'wordpress-containerinstance'
   location: location
   properties: {

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

@@ -1,11 +1,9 @@
 ---
 title: Bicep functions - numeric
 description: Describes the functions to use in a Bicep file to work with numbers.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/30/2021
+ms.date: 06/23/2023
 ---
 
 # Numeric functions for Bicep

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

@@ -1,11 +1,9 @@
 ---
 title: Child resources in Bicep
 description: Describes how to set the name and type for child resources in Bicep.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/13/2021
+ms.date: 06/23/2023
 ---
 
 # Set name and type for child resources in Bicep

articles/azure-resource-manager/bicep/deploy-cloud-shell.md

@@ -1,11 +1,9 @@
 ---
 title: Deploy Bicep files with Cloud Shell
 description: Use Azure Resource Manager and Azure Cloud Shell to deploy resources to Azure. The resources are defined in a Bicep file.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 06/01/2021
+ms.date: 06/23/2023
 ---
 
 # Deploy Bicep files from Azure Cloud Shell

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

@@ -11,9 +11,7 @@ metadata:
   ms.subservice: Bicep
   ms.topic: landing-page
   ms.collection: na
-  author: mumian
-  ms.author: jgao
-  ms.date: 11/17/2021
+  ms.date: 06/23/2023
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 

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

@@ -3,7 +3,7 @@ title: Key Vault secret with Bicep
 description: Shows how to pass a secret from a key vault as a parameter during Bicep deployment.
 ms.topic: conceptual
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
-ms.date: 06/15/2023
+ms.date: 06/23/2023
 ---
 
 # Use Azure Key Vault to pass secure parameter value during Bicep deployment
@@ -187,7 +187,7 @@ param subscriptionId string
 param kvResourceGroup string
 param kvName string
 
-resource kv 'Microsoft.KeyVault/vaults@2019-09-01' existing = {
+resource kv 'Microsoft.KeyVault/vaults@2023-02-01' existing = {
   name: kvName
   scope: resourceGroup(subscriptionId, kvResourceGroup )
 }
@@ -214,16 +214,17 @@ If you don't want to use a module, you can reference the key vault directly in t
 The following Bicep file deploys a SQL server that includes an administrator password. The password parameter is set to a secure string. But the Bicep doesn't specify where that value comes from.
 
 ```bicep
+param location string = resourceGroup().location
 param adminLogin string
 
 @secure()
 param adminPassword string
 
 param sqlServerName string
 
-resource sqlServer 'Microsoft.Sql/servers@2020-11-01-preview' = {
+resource sqlServer 'Microsoft.Sql/servers@2022-11-01-preview' = {
   name: sqlServerName
-  location: resourceGroup().location
+  location: location
   properties: {
     administratorLogin: adminLogin
     administratorLoginPassword: adminPassword

articles/azure-resource-manager/bicep/linter-rule-admin-username-should-not-be-literal.md

@@ -3,7 +3,7 @@ title: Linter rule - admin user name should not be literal
 description: Linter rule - admin user name should not be a literal
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/18/2021
+ms.date: 06/23/2023
 ---
 
 # Linter rule - admin user name should not be literal
@@ -23,7 +23,7 @@ Don't use a literal value or an expression that evaluates to a literal value. In
 The following example fails this test because the user name is a literal value.
 
 ```bicep
-resource vm 'Microsoft.Compute/virtualMachines@2020-12-01' = {
+resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   name: 'name'
   location: location
   properties: {
@@ -38,7 +38,7 @@ The next example fails this test because the expression evaluates to a literal v
 
 ```bicep
 var defaultAdmin = 'administrator'
-resource vm 'Microsoft.Compute/virtualMachines@2020-12-01' = {
+resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   name: 'name'
   location: location
   properties: {
@@ -55,7 +55,7 @@ This example passes this test.
 @secure()
 param adminUsername string
 param location string
-resource vm 'Microsoft.Compute/virtualMachines@2020-12-01' = {
+resource vm 'Microsoft.Compute/virtualMachines@2023-03-01' = {
   name: 'name'
   location: location
   properties: {

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: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/18/2021
+ms.date: 06/23/2023
 ---
 
 # Linter rule - no hardcoded environment URL
@@ -43,10 +43,11 @@ In some cases, you can fix it by getting a property from a resource you've deplo
 
 ```bicep
 param storageAccountName string
+param location string = resourceGroup().location
 
-resource sa 'Microsoft.Storage/storageAccounts@2021-04-01' = {
+resource sa 'Microsoft.Storage/storageAccounts@2022-09-01' = {
   name: storageAccountName
-  location: 'westus'
+  location: location
   sku: {
     name: 'Standard_LRS'
   }
@@ -61,7 +62,7 @@ output endpoint string = sa.properties.primaryEndpoints.web
 
 ## Configuration
 
-By default, this rule uses the following settings for determining which URLs are disallowed. 
+By default, this rule uses the following settings for determining which URLs are disallowed.
 
 ```json
 "analyzers": {

articles/azure-resource-manager/bicep/operators-access.md

@@ -1,11 +1,9 @@
 ---
 title: Bicep accessor operators
 description: Describes Bicep resource access operator and property access operator.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/10/2021
+ms.date: 06/23/2023
 ---
 
 # Bicep accessor operators
@@ -41,7 +39,7 @@ var arrayVar = [
 ]
 
 output accessorResult string = arrayVar[1]
-``` 
+```
 
 Output from the example:
 
@@ -81,7 +79,7 @@ Two functions - [getSecret](bicep-functions-resource.md#getsecret) and [list*](b
 The following example references an existing key vault, then uses `getSecret` to pass a secret to a module.
 
 ```bicep
-resource kv 'Microsoft.KeyVault/vaults@2019-09-01' existing = {
+resource kv 'Microsoft.KeyVault/vaults@2023-02-01' existing = {
   name: kvName
   scope: resourceGroup(subscriptionId, kvResourceGroup )
 }
@@ -109,7 +107,7 @@ Within the parent resource, you reference the nested resource with just the symb
 The following example shows how to reference a nested resource from within the parent resource and from outside of the parent resource.
 
 ```bicep
-resource demoParent 'demo.Rp/parentType@2020-01-01' = {
+resource demoParent 'demo.Rp/parentType@2023-01-01' = {
   name: 'demoParent'
   location: 'West US'
 
@@ -168,7 +166,7 @@ Output from the example:
 Typically, you use the property accessor with a resource deployed in the Bicep file. The following example creates a public IP address and uses property accessors to return a value from the deployed resource.
 
 ```bicep
-resource publicIp 'Microsoft.Network/publicIPAddresses@2020-06-01' = {
+resource publicIp 'Microsoft.Network/publicIPAddresses@2022-11-01' = {
   name: publicIpResourceName
   location: location
   properties: {

articles/azure-resource-manager/bicep/operators-comparison.md

@@ -1,11 +1,9 @@
 ---
 title: Bicep comparison operators
 description: Describes Bicep comparison operators that compare values.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/07/2021
+ms.date: 06/23/2023
 ---
 
 # Bicep comparison operators