Merge pull request #303318 from mumian/0725-bicep-refresh

Refresh Bicep articles

Author: Stacyrch140

articles/azure-resource-manager/bicep/deployment-script-develop.md

@@ -3,7 +3,7 @@ title: Develop a deployment script in Bicep
 description: Learn how to develop a deployment script within a Bicep file or store one externally as a separate file.
 ms.custom: devx-track-bicep
 ms.topic: conceptual
-ms.date: 09/26/2024
+ms.date: 07/25/2025
 ---
 
 # Develop a deployment script in Bicep

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

@@ -3,7 +3,7 @@ title: Bicep file structure and syntax
 description: Understand how to use declarative syntax to understand the structure and properties of Bicep files.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 03/25/2025
+ms.date: 07/25/2025
 ---
 
 # Bicep file structure and syntax
@@ -68,7 +68,7 @@ param location string = resourceGroup().location
 
 var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -168,7 +168,7 @@ var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 Apply this variable wherever you need the complex expression.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: uniqueStorageName
 ```
 
@@ -195,7 +195,7 @@ param storageAccountConfig storageAccountConfigType = {
   sku: 'Standard_LRS'
 }
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: storageAccountConfig.name
   location: location
   sku: {
@@ -228,7 +228,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@2023-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -250,7 +250,7 @@ Some resources have a parent/child relationship. You can define a child resource
 The following example shows how to define a child resource within a parent resource. It contains a storage account with a child resource (file service) that's defined within the storage account. The file service also has a child resource (share) that's defined within it.
 
 ```bicep
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -271,7 +271,7 @@ resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 The next example shows how to define a child resource outside of the parent resource. You use the parent property to identify a parent/child relationship. The same three resources are defined.
 
 ```bicep
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -373,15 +373,15 @@ Spaces and tabs are ignored when you author Bicep files.
 Bicep is newline sensitive. For example:
 
 ```bicep
-resource sa 'Microsoft.Storage/storageAccounts@2023-04-01' = if (newOrExisting == 'new') {
+resource sa 'Microsoft.Storage/storageAccounts@2025-01-01' = if (newOrExisting == 'new') {
   ...
 }
 ```
 
 Can't be written as:
 
 ```bicep
-resource sa 'Microsoft.Storage/storageAccounts@2023-04-01' =
+resource sa 'Microsoft.Storage/storageAccounts@2025-01-01' =
     if (newOrExisting == 'new') {
       ...
     }
@@ -397,7 +397,7 @@ The following example shows a single-line comment.
 
 ```bicep
 // This is your primary NIC.
-resource nic1 'Microsoft.Network/networkInterfaces@2023-11-01' = {
+resource nic1 'Microsoft.Network/networkInterfaces@2024-07-01' = {
   ...
 }
 ```

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

@@ -2,7 +2,7 @@
 title: Install Bicep tools
 description: Learn how to install tools to set up Bicep development and deployment environments.
 ms.topic: how-to
-ms.date: 03/25/2025
+ms.date: 07/25/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
 ---
 
@@ -49,19 +49,20 @@ To see the settings:
 
 1. From the `View` menu, select `Extensions`.
 1. Select `Bicep` from the list of extensions.
-1. Select the `FEATURE CONTRIBUTIONS` tab:
+1. Select the `FEATURE` tab.
+1. Select **Settings**.
 
     :::image type="content" source="./media/install/bicep-extension-feature-contributions-settings.png" alt-text="Screenshot of Bicep extension settings.":::
 
     The Bicep extension has these settings and default values:
 
     | ID | Default value | Description |
     |-----|-------------|---------|
-    | bicep.decompileOnPaste | true | Automatically convert pasted JSON values, Azure Resource Manager JSON templates (ARM templates,) or resources from an ARM template into Bicep (use Undo to revert). For more information, see the [Paste JSON as Bicep command](./visual-studio-code.md#paste-json-as-bicep-command).|
+    | bicep.completions.getAllAccessibleAzureContainerRegistries | false | When completing 'br:' module references, query Azure for all container registries accessible to the user (may be slow). If this option is off, only registries configured under moduleAliases in bicepconfig.json will be listed. |
+    | bicep.decompileOnPaste | true | Automatically convert pasted JSON values, JSON ARM templates or resources from a JSON ARM template into Bicep (use Undo to revert).|
     | bicep.enableOutputTimestamps | true | Prepend each line displayed in the Bicep Operations output channel with a timestamp. |
-    | bicep.suppressedWarnings | | Warnings that are being suppressed because a 'Don't show again' button was pressed. Remove items to reset.|
     | bicep.enableSurveys | true | Enable occasional surveys to collect feedback that helps us improve the Bicep extension. |
-    | bicep.completions.getAllAccessibleAzureContainerRegistries | false | When completing 'br:' module references, query Azure for all container registries accessible to the user (might be slow). If this option is off, only  registries configured under [moduleAliases](./bicep-config-modules.md#aliases-for-modules) in [_bicepconfig.json_ files](./bicep-config.md) will be listed. |
+    | bicep.suppressedWarnings | | Warnings that are being suppressed because a 'Don't show again' button was pressed. Remove items to reset.|
     | bicep.trace.server | off | Configure tracing of messages sent to the Bicep language server. |
 
 To configure the settings:

articles/azure-resource-manager/bicep/media/install/bicep-extension-feature-contributions-settings.png

@@ -3,7 +3,7 @@ title: Migrate blueprints to deployment stacks
 description: Learn how to migrate blueprints to deployment stacks.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 11/11/2024
+ms.date: 07/25/2025
 ---
 
 # Migrate blueprints to deployment stacks

articles/azure-resource-manager/bicep/media/install/bicep-extension-settings.png

@@ -5,7 +5,7 @@ ms.topic: conceptual
 ms.custom:
   - devx-track-bicep
   - build-2025
-ms.date: 05/09/2025
+ms.date: 07/25/2025
 ---
 
 # Bicep modules
@@ -69,7 +69,7 @@ The path can be either a local file or a file in a registry. The local file can
 
 The `name` property is optional. It becomes the name of the nested deployment resource in the generated template. If no name is provided, a GUID will be generated as the name for the nested deployment resource.
 
-If a module with a static name is deployed concurrently to the same scope, there's the potential for one deployment to interfere with the output from the other deployment. For example, if two Bicep files use the same module with the same static name (`examplemodule`) and are targeted to the same resource group, one deployment might show the wrong output. If you're concerned about concurrent deployments to the same scope, give your module a unique name. Another way to ensure unique module names is to leave out the `name` property, an unique module name will be generated automatically.
+If a module with a static name is deployed concurrently to the same scope, there's the potential for one deployment to interfere with the output from the other deployment. For example, if two Bicep files use the same module with the same static name (`examplemodule`) and are targeted to the same resource group, one deployment might show the wrong output. If you're concerned about concurrent deployments to the same scope, give your module a unique name. Another way to ensure unique module names is to leave out the `name` property, a unique module name will be generated automatically.
 
 The following example concatenates the deployment name to the module name. If you provide a unique name for the deployment, the module name is also unique.
 
@@ -80,7 +80,7 @@ module stgModule 'storageAccount.bicep' = {
 }
 ```
 
-Not providing any module name is also valid. A GUID will be generate as the module name.
+Not providing any module name is also valid. A GUID will be generated as the module name.
 
 ```bicep
 module stgModule 'storageAccount.bicep' = {
@@ -353,7 +353,7 @@ param location string
 
 var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -377,7 +377,7 @@ targetScope = 'subscription'
 @maxLength(11)
 param namePrefix string
 
-resource demoRG 'Microsoft.Resources/resourceGroups@2024-03-01' existing = {
+resource demoRG 'Microsoft.Resources/resourceGroups@2025-04-01' existing = {
   name: 'demogroup1'
 }
 
@@ -411,7 +411,7 @@ param location string = deployment().location
 
 var resourceGroupName = '${namePrefix}rg'
 
-resource newRG 'Microsoft.Resources/resourceGroups@2024-03-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2025-04-01' = {
   name: resourceGroupName
   location: location
 }
@@ -433,11 +433,11 @@ The next example deploys storage accounts to two different resource groups. Both
 ```bicep
 targetScope = 'subscription'
 
-resource firstRG 'Microsoft.Resources/resourceGroups@2024-03-01' existing = {
+resource firstRG 'Microsoft.Resources/resourceGroups@2025-04-01' existing = {
   name: 'demogroup1'
 }
 
-resource secondRG 'Microsoft.Resources/resourceGroups@2024-03-01' existing = {
+resource secondRG 'Microsoft.Resources/resourceGroups@2025-04-01' existing = {
   name: 'demogroup2'
 }
 
@@ -507,7 +507,7 @@ param location string
 
 var uniqueStorageName = '${storagePrefix}${uniqueString(resourceGroup().id)}'
 
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-01-01' = {
   name: uniqueStorageName
   location: location
   sku: {
@@ -531,7 +531,7 @@ targetScope = 'subscription'
 @maxLength(11)
 param namePrefix string
 
-resource demoRG 'Microsoft.Resources/resourceGroups@2024-03-01' existing = {
+resource demoRG 'Microsoft.Resources/resourceGroups@2025-04-01' existing = {
   name: 'demogroup1'
 }