Merge pull request #269622 from mumian/0320-bicep-freshness

Refresh Bicep content

Author: v-shils

articles/azure-resource-manager/bicep/bicep-extensibility-kubernetes-provider.md

@@ -3,7 +3,7 @@ title: Bicep extensibility Kubernetes provider
 description: Learn how to Bicep Kubernetes provider  to deploy .NET applications to Azure Kubernetes Service clusters.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-dotnet
-ms.date: 04/18/2023
+ms.date: 03/20/2024
 ---
 
 # Bicep extensibility Kubernetes provider (Preview)

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

@@ -1,11 +1,9 @@
 ---
 title: Bicep functions - deployment
 description: Describes the functions to use in a Bicep file to retrieve deployment information.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/09/2022
+ms.date: 03/20/2024
 ---
 
 # Deployment functions for Bicep
@@ -49,7 +47,7 @@ When deploying a local Bicep file to a resource group, the function returns the
 }
 ```
 
-When you deploy to an Azure subscription, management group, or tenant, the return object includes a `location` property. The `location` property is not included when deploying a local Bicep file. The format is:
+When you deploy to an Azure subscription, management group, or tenant, the return object includes a `location` property. The `location` property isn't included when deploying a local Bicep file. The format is:
 
 ```json
 {

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

@@ -1,11 +1,9 @@
 ---
 title: Bicep functions - logical
 description: Describes the functions to use in a Bicep file to determine logical values.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 01/30/2023
+ms.date: 03/20/2024
 ---
 
 # Logical functions for Bicep

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

@@ -3,12 +3,12 @@ title: Bicep functions - parameters file
 description: This article describes the Bicep functions to be used in Bicep parameter files.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/05/2023
+ms.date: 03/20/2024
 ---
 
 # Parameters file function for Bicep
 
-Bicep provides a function called `readEnvironmentVariable()` that allows you to retrieve values from environment variables. It also offers the flexibility to set a default value if the environment variable does not exist. This function can only be used in the `.bicepparam` files. For more information, see [Bicep parameters file](./parameter-files.md).
+Bicep provides a function called `readEnvironmentVariable()` that allows you to retrieve values from environment variables. It also offers the flexibility to set a default value if the environment variable doesn't exist. This function can only be used in the `.bicepparam` files. For more information, see [Bicep parameters file](./parameter-files.md).
 
 ## getSecret
 
@@ -26,7 +26,7 @@ param secureUserName = getSecret('exampleSubscription', 'exampleResourceGroup',
 param securePassword = getSecret('exampleSubscription', 'exampleResourceGroup', 'exampleKeyVault', 'exampleSecretPassword')
 ```
 
-You'll get an error if you use this function with string interpolation.
+You get an error if you use this function with string interpolation.
 
 A [namespace qualifier](bicep-functions.md#namespaces-for-functions) (`az`) can be used, but it's optional, because the function is available from the _default_ Azure Namespace.
 
@@ -46,15 +46,15 @@ The value for the secret.
 
 ### Example
 
-The following `.bicepparam` file has a `securePassword` parameter that will have the latest value of the _\<secretName\>_ secret.
+The following `.bicepparam` file has a `securePassword` parameter that has the latest value of the _\<secretName\>_ secret.
 
 ```bicep
 using './main.bicep'
 
 param securePassword = getSecret('exampleSubscription', 'exampleResourceGroup', 'exampleKeyVault', 'exampleSecretPassword')
 ```
 
-The following `.bicepparam` file has a `securePassword` parameter that will have the value of the _\<secretName\>_ secret, but it's pinned to a specific _\<secretValue\>_.
+The following `.bicepparam` file has a `securePassword` parameter that has the value of the _\<secretName\>_ secret, but it's pinned to a specific _\<secretValue\>_.
 
 ```bicep
 using './main.bicep'
@@ -75,7 +75,7 @@ Namespace: [sys](bicep-functions.md#namespaces-for-functions).
 | Parameter | Required | Type | Description |
 |:--- |:--- |:--- |:--- |
 | variableName | Yes | string | The name of the variable. |
-| defaultValue | No | string | A default string value to be used if the environment variable does not exist. |
+| defaultValue | No | string | A default string value to be used if the environment variable doesn't exist. |
 
 ### Return value
 

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

@@ -1,11 +1,9 @@
 ---
 title: Bicep functions - resources
 description: Describes the functions to use in a Bicep file to retrieve values about resources.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/03/2023
+ms.date: 03/20/2024
 ---
 
 # Resource functions for Bicep
@@ -502,7 +500,7 @@ Returns an object representing a resource's runtime state.
 
 Namespace: [az](bicep-functions.md#namespaces-for-functions).
 
-The Bicep files provide access to the reference function, although it is typically unnecessary. Instead, it is recommended to use the symbolic name of the resource. The reference function can only be used within the `properties` object of a resource and cannot be employed for top-level properties like `name` or `location`. The same generally applies to references using the symbolic name. However, for properties such as `name`, it is possible to generate a template without utilizing the reference function. Sufficient information about the resource name is known to directly emit the name. It is referred to as compile-time properties. Bicep validation can identify any incorrect usage of the symbolic name.
+The Bicep files provide access to the reference function, although it's typically unnecessary. Instead, it's recommended to use the symbolic name of the resource. The reference function can only be used within the `properties` object of a resource and can't be employed for top-level properties like `name` or `location`. The same generally applies to references using the symbolic name. However, for properties such as `name`, it's possible to generate a template without utilizing the reference function. Sufficient information about the resource name is known to directly emit the name. It's referred to as compile-time properties. Bicep validation can identify any incorrect usage of the symbolic name.
 
 The following example deploys a storage account. The first two outputs give you the same results.
 
@@ -588,7 +586,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing
 output storageID string = storageAccount.id
 ```
 
-For more information, see the [JSON template resourceId function](../templates/template-functions-resource.md#resourceid)
+For more information, see the [JSON template resourceId function](../templates/template-functions-resource.md#resourceid).
 
 ## subscriptionResourceId
 

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

@@ -3,7 +3,7 @@ title: Bicep functions - scopes
 description: Describes the functions to use in a Bicep file to retrieve values about deployment scopes.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/17/2022
+ms.date: 03/20/2024
 ---
 
 # Scope functions for Bicep

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

@@ -1,12 +1,9 @@
 ---
 title: Conditional deployment with Bicep
 description: Describes how to conditionally deploy a resource in Bicep.
-
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 10/20/2023
+ms.date: 03/20/2024
 ---
 
 # Conditional deployments in Bicep with the if expression

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

@@ -2,7 +2,7 @@
 title: Decompile ARM template JSON to Bicep
 description: Describes commands for decompiling Azure Resource Manager templates to Bicep files.
 ms.topic: conceptual
-ms.date: 03/03/2023
+ms.date: 03/20/2024
 ms.custom: devx-track-bicep, devx-track-arm-template
 ---
 

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: conceptual
 ms.custom: devx-track-bicep
-ms.date: 08/05/2022
+ms.date: 03/20/2024
 ---
 
 # Resource group deployments with Bicep files

articles/azure-resource-manager/bicep/deploy-vscode.md

@@ -1,11 +1,9 @@
 ---
-title: Deploy Bicep files with visual Studio Code
+title: Deploy Bicep files with Visual Studio Code
 description: Deploy Bicep files from Visual Studio Code.
-author: mumian
-ms.author: jgao
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 12/06/2022
+ms.date: 03/20/2024
 ---
 
 # Deploy Bicep files from Visual Studio Code