Merge pull request #298975 from mumian/0428-bicep-freshness

[SCOPED] Bicep freshness

Author: denrea

articles/azure-resource-manager/bicep/bicep-config-linter.md

@@ -3,7 +3,7 @@ title: Linter settings for Bicep config
 description: Describes how to customize configuration values for the Bicep linter
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/19/2024
+ms.date: 04/28/2025
 ---
 
 # Add linter settings in the Bicep config file

articles/azure-resource-manager/bicep/bicep-config-modules.md

@@ -3,7 +3,7 @@ title: Module setting for Bicep config
 description: Describes how to customize configuration values for modules in Bicep deployments.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 06/28/2024
+ms.date: 04/28/2025
 ---
 
 # Add module settings in the Bicep config file
@@ -169,7 +169,6 @@ Bicep uses the [Azure.Identity SDK](/dotnet/api/azure.identity) to do authentica
 - [Environment](/dotnet/api/azure.identity.environmentcredential)
 - [ManagedIdentity](/dotnet/api/azure.identity.managedidentitycredential)
 - [VisualStudio](/dotnet/api/azure.identity.visualstudiocredential)
-- [VisualStudioCode](/dotnet/api/azure.identity.visualstudiocodecredential)
 
 [!INCLUDE [vscode authentication](../../../includes/resource-manager-vscode-authentication.md)]
 

articles/azure-resource-manager/bicep/bicep-kubernetes-extension.md

@@ -3,7 +3,7 @@ title: Bicep Kubernetes extension
 description: Learn how to Bicep Kubernetes extension to deploy .NET applications to Azure Kubernetes Service clusters.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-dotnet
-ms.date: 08/07/2024
+ms.date: 04/28/2025
 ---
 
 # Bicep Kubernetes extension (Preview)
@@ -12,9 +12,9 @@ The Kubernetes extension allows you to create Kubernetes resources directly with
 
 > [!NOTE]
 > The Kubernetes extension is not currently supported for private clusters:
-> 
+>
 > ```bicep
-> resource AKS 'Microsoft.ContainerService/managedClusters@2024-02-01' = {
+> resource AKS 'Microsoft.ContainerService/managedClusters@2024-10-01' = {
 >  ...
 >  properties: {
 >   apiServerAccessProfile: {
@@ -60,7 +60,7 @@ extension kubernetes with {
 The following sample shows how to pass `kubeConfig` value from a parent Bicep file:
 
 ```bicep
-resource aks 'Microsoft.ContainerService/managedClusters@2024-08-01' existing = {
+resource aks 'Microsoft.ContainerService/managedClusters@2024-10-01' existing = {
   name: 'demoAKSCluster'
 }
 

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

@@ -3,7 +3,7 @@ title: Child resources in Bicep
 description: Describes how to set the name and type for child resources in Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 09/26/2024
+ms.date: 04/28/2025
 ---
 
 # Set name and type for child resources in Bicep
@@ -67,7 +67,7 @@ A nested resource declaration must appear at the top level of syntax of the pare
 When defined within the parent resource type, you format the type and name values as a single segment without slashes. The following example shows a storage account with a child resource for the file service, and the file service has a child resource for the file share. The file service's name is set to `default` and its type is set to `fileServices`. The file share's name is set `exampleshare` and its type is set to `shares`.
 
 ```bicep
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -119,7 +119,7 @@ When defined outside of the parent resource, you format the type and with slashe
 The following example shows a storage account, file service, and file share that are all defined at the root level.
 
 ```bicep
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -128,12 +128,12 @@ resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   }
 }
 
-resource service 'Microsoft.Storage/storageAccounts/fileServices@2023-04-01' = {
+resource service 'Microsoft.Storage/storageAccounts/fileServices@2024-01-01' = {
   name: 'default'
   parent: storage
 }
 
-resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-04-01' = {
+resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2024-01-01' = {
   name: 'exampleshare'
   parent: service
 }
@@ -146,7 +146,7 @@ Referencing the child resource symbolic name works the same as referencing the p
 You can also use the full resource name and type when declaring the child resource outside the parent. You don't set the parent property on the child resource. Because the dependency can't be inferred, you must set it explicitly.
 
 ```bicep
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -155,14 +155,14 @@ resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   }
 }
 
-resource service 'Microsoft.Storage/storageAccounts/fileServices@2023-04-01' = {
+resource service 'Microsoft.Storage/storageAccounts/fileServices@2024-01-01' = {
   name: 'examplestorage/default'
   dependsOn: [
     storage
   ]
 }
 
-resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-04-01' = {
+resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2024-01-01' = {
   name: 'examplestorage/default/exampleshare'
   dependsOn: [
     service

articles/azure-resource-manager/bicep/compare-template-syntax.md

@@ -3,7 +3,7 @@ title: Compare syntax for Azure Resource Manager templates in JSON and Bicep
 description: Compares Azure Resource Manager templates developed with JSON and Bicep, and shows how to convert between the languages.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 07/11/2024
+ms.date: 04/28/2025
 ---
 
 # Comparing JSON and Bicep for templates
@@ -213,11 +213,11 @@ For Bicep, you can set an explicit dependency but this approach isn't recommende
 The following shows a network interface with an implicit dependency on a network security group. It references the network security group with `netSecurityGroup.id`.
 
 ```bicep
-resource netSecurityGroup 'Microsoft.Network/networkSecurityGroups@2023-11-01' = {
+resource netSecurityGroup 'Microsoft.Network/networkSecurityGroups@2024-05-01' = {
   ...
 }
 
-resource nic1 'Microsoft.Network/networkInterfaces@2023-11-01' = {
+resource nic1 'Microsoft.Network/networkInterfaces@2024-05-01' = {
   name: nic1Name
   location: location
   properties: {
@@ -254,7 +254,7 @@ storageAccount.properties.primaryEndpoints.blob
 To get a property from an existing resource that isn't deployed in the template:
 
 ```bicep
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2024-01-01' existing = {
   name: storageAccountName
 }
 

articles/azure-resource-manager/bicep/create-resource-group.md

@@ -3,7 +3,7 @@ title: Use Bicep to create a new resource group
 description: Describes how to use Bicep to create a new resource group in your Azure subscription.
 ms.topic: how-to
 ms.custom: devx-track-bicep
-ms.date: 09/26/2024
+ms.date: 04/28/2025
 ---
 
 # Create resource groups by using Bicep
@@ -22,7 +22,7 @@ targetScope='subscription'
 param resourceGroupName string
 param resourceGroupLocation string
 
-resource newRG 'Microsoft.Resources/resourceGroups@2024-03-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2024-11-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
 }
@@ -65,7 +65,7 @@ param resourceGroupLocation string
 param storageName string
 param storageLocation string
 
-resource newRG 'Microsoft.Resources/resourceGroups@2024-03-01' = {
+resource newRG 'Microsoft.Resources/resourceGroups@2024-11-01' = {
   name: resourceGroupName
   location: resourceGroupLocation
 }
@@ -86,7 +86,7 @@ The module uses a Bicep file named **storage.bicep** with the following contents
 param storageLocation string
 param storageName string
 
-resource storageAcct 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAcct 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: storageName
   location: storageLocation
   sku: {

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

@@ -3,7 +3,7 @@ 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.
 ms.topic: how-to
 ms.custom: devx-track-bicep, devx-track-arm-template
-ms.date: 09/26/2024
+ms.date: 04/28/2025
 ---
 
 # Deploy Bicep files from Azure Cloud Shell
@@ -28,7 +28,7 @@ To deploy a local Bicep file, you must first upload your Bicep file to your Clou
 1. Select the Bicep file you want to upload, and then select **Open**.
 1. To deploy the Bicep file, use the following commands:
 
-   # [Azure CLI](#tab/azure-cli)
+   ### [Azure CLI](#tab/azure-cli)
 
    ```azurecli-interactive
    az group create --name ExampleGroup --location "South Central US"
@@ -38,7 +38,7 @@ To deploy a local Bicep file, you must first upload your Bicep file to your Clou
      --parameters storageAccountType=Standard_GRS
    ```
 
-   # [PowerShell](#tab/azure-powershell)
+   ### [PowerShell](#tab/azure-powershell)
 
    ```azurepowershell-interactive
    New-AzResourceGroup -Name ExampleGroup -Location "Central US"

articles/azure-resource-manager/bicep/deploy-what-if.md

@@ -3,7 +3,7 @@ title: Bicep deployment what-if
 description: Determine what changes will happen to your resources before deploying a Bicep file.
 ms.topic: conceptual
 ms.custom: devx-track-bicep, devx-track-azurecli, devx-track-azurepowershell
-ms.date: 09/26/2024
+ms.date: 04/28/2025
 ---
 
 # Bicep deployment what-if operation
@@ -276,7 +276,7 @@ az deployment group create \
 After the deployment completes, you're ready to test the what-if operation. This time you deploy a Bicep file that changes the virtual network. It's missing one of the original tags, a subnet has been removed, and the address prefix has changed. Download a copy of the Bicep file.
 
 ```bicep
-resource vnet 'Microsoft.Network/virtualNetworks@2023-11-01' = {
+resource vnet 'Microsoft.Network/virtualNetworks@2024-05-01' = {
   name: 'vnet-001'
   location: resourceGroup().location
   tags: {

articles/azure-resource-manager/bicep/deployment-script-bicep-configure-dev.md

@@ -2,7 +2,7 @@
 title: Configure development environment for deployment scripts in Bicep | Microsoft Docs
 description: Configure development environment for deployment scripts in Bicep.
 ms.topic: how-to
-ms.date: 09/26/2024
+ms.date: 04/28/2025
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
 ms.devlang: azurecli
 ---
@@ -84,7 +84,7 @@ var fileShareName = '${projectName}share'
 var containerGroupName = '${projectName}cg'
 var containerName = '${projectName}container'
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: storageAccountName
   location: location
   sku: {
@@ -96,14 +96,14 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-01-01' = {
   }
 }
 
-resource fileShare 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-01-01' = {
+resource fileShare 'Microsoft.Storage/storageAccounts/fileServices/shares@2024-01-01' = {
   name: '${storageAccountName}/default/${fileShareName}'
   dependsOn: [
     storageAccount
   ]
 }
 
-resource containerGroup 'Microsoft.ContainerInstance/containerGroups@2023-05-01' = {
+resource containerGroup 'Microsoft.ContainerInstance/containerGroups@2024-11-01-preview' = {
   name: containerGroupName
   location: location
   properties: {
@@ -237,7 +237,7 @@ var fileShareName = '${projectName}share'
 var containerGroupName = '${projectName}cg'
 var containerName = '${projectName}container'
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: storageAccountName
   location: location
   sku: {
@@ -249,14 +249,14 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   }
 }
 
-resource fileshare 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-04-01' = {
+resource fileshare 'Microsoft.Storage/storageAccounts/fileServices/shares@2024-01-01' = {
   name: '${storageAccountName}/default/${fileShareName}'
   dependsOn: [
     storageAccount
   ]
 }
 
-resource containerGroup 'Microsoft.ContainerInstance/containerGroups@2023-05-01' = {
+resource containerGroup 'Microsoft.ContainerInstance/containerGroups@2024-11-01-preview' = {
   name: containerGroupName
   location: location
   properties: {

articles/azure-resource-manager/bicep/deployment-script-vnet-private-endpoint.md

@@ -3,7 +3,7 @@ title: Run Bicep deployment script privately over a private endpoint
 description: Learn how to run Bicep deployment script privately over a private endpoint.
 ms.custom: devx-track-bicep
 ms.topic: how-to
-ms.date: 09/26/2024
+ms.date: 04/28/2025
 ---
 
 # Run Bicep deployment script privately over a private endpoint
@@ -43,12 +43,12 @@ var vnetAddressPrefix = '192.168.4.0/23'
 var subnetEndpointAddressPrefix = '192.168.4.0/24'
 var subnetACIAddressPrefix = '192.168.5.0/24'
 
-resource managedIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2023-01-31' = {
+resource managedIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2024-11-30' = {
   name: userAssignedIdentityName
   location: location
 }
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   name: storageAccountName
   kind: 'StorageV2'
   location: location
@@ -64,7 +64,7 @@ resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   }
 }
 
-resource privateEndpoint 'Microsoft.Network/privateEndpoints@2023-11-01' = {
+resource privateEndpoint 'Microsoft.Network/privateEndpoints@2024-05-01' = {
    name: storageAccount.name
    location: location
    properties: {
@@ -101,7 +101,7 @@ resource roleAssignment 'Microsoft.Authorization/roleAssignments@2022-04-01' = {
   }
 }
 
-resource privateDnsZone 'Microsoft.Network/privateDnsZones@2020-06-01' = {
+resource privateDnsZone 'Microsoft.Network/privateDnsZones@2024-06-01' = {
   name: 'privatelink.file.core.windows.net'
   location: 'global'
 
@@ -129,7 +129,7 @@ resource privateDnsZone 'Microsoft.Network/privateDnsZones@2020-06-01' = {
   }
 }
 
-resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
+resource virtualNetwork 'Microsoft.Network/virtualNetworks@2024-05-01' = {
   name: vnetName
   location: location
   properties:{