update api versions in Bicep files

Author: mumian

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

@@ -38,7 +38,7 @@ The value in a form that's compatible with any data type in Bicep.
 The following example shows how to use the Bicep `any()` function to provide numeric values as strings.
 
 ```bicep
-resource wpAci 'Microsoft.ContainerInstance/containerGroups@2023-05-01' = {
+resource wpAci 'Microsoft.ContainerInstance/containerGroups@2025-09-01' = {
   name: 'wordpress-containerinstance'
   location: location
   properties: {

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

@@ -209,7 +209,7 @@ param dnsServers array = []
 
 ...
 
-resource vnet 'Microsoft.Network/virtualNetworks@2023-11-01' = {
+resource vnet 'Microsoft.Network/virtualNetworks@2025-01-01' = {
   name: vnetName
   location: location
   properties: {
@@ -652,7 +652,7 @@ param availabilityZones array = [
   '2'
 ]
 
-resource exampleApim 'Microsoft.ApiManagement/service@2023-05-01-preview' = {
+resource exampleApim 'Microsoft.ApiManagement/service@2024-10-01-preview' = {
   name: apiManagementName
   location: location
   sku: {
@@ -802,15 +802,15 @@ The following example is extracted from a quickstart template, [Two VMs in VNET
 ...
 var numberOfInstances = 2
 
-resource networkInterface 'Microsoft.Network/networkInterfaces@2023-11-01' = [for i in range(0, numberOfInstances): {
+resource networkInterface 'Microsoft.Network/networkInterfaces@2025-01-01' = [for i in range(0, numberOfInstances): {
   name: '${networkInterfaceName}${i}'
   location: location
   properties: {
     ...
   }
 }]
 
-resource vm 'Microsoft.Compute/virtualMachines@2024-03-01' = [for i in range(0, numberOfInstances): {
+resource vm 'Microsoft.Compute/virtualMachines@2025-04-01' = [for i in range(0, numberOfInstances): {
   name: '${vmNamePrefix}${i}'
   location: location
   properties: {

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

@@ -79,8 +79,8 @@ var startTime = dateTimeAdd(baseTime, 'PT1H')
 
 ...
 
-resource scheduler 'Microsoft.Automation/automationAccounts/schedules@2023-11-01' = {
-  name: concat(omsAutomationAccountName, '/', scheduleName)
+resource scheduler 'Microsoft.Automation/automationAccounts/schedules@2024-10-23' = {
+  name: '${omsAutomationAccountName}/${scheduleName}'
   properties: {
     description: 'Demo Scheduler'
     startTime: startTime
@@ -232,7 +232,7 @@ The next example shows how to use a value from the function when setting a tag v
 param utcShort string = utcNow('d')
 param rgName string
 
-resource myRg 'Microsoft.Resources/resourceGroups@2024-03-01' = {
+resource myRg 'Microsoft.Resources/resourceGroups@2025-04-01' = {
   name: rgName
   location: 'westeurope'
   tags: {

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

@@ -132,7 +132,7 @@ param location string = resourceGroup().location
 
 var nsgconfig = loadJsonContent('nsg-security-rules.json')
 
-resource newNSG 'Microsoft.Network/networkSecurityGroups@2023-11-01' = {
+resource newNSG 'Microsoft.Network/networkSecurityGroups@2025-01-01' = {
   name: 'example-nsg'
   location: location
   properties: {
@@ -201,7 +201,7 @@ param location string = resourceGroup().location
 
 var nsgconfig = loadYamlContent('nsg-security-rules.yaml')
 
-resource newNSG 'Microsoft.Network/networkSecurityGroups@2023-11-01' = {
+resource newNSG 'Microsoft.Network/networkSecurityGroups@2025-01-01' = {
   name: 'example-nsg'
   location: location
   properties: {

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

@@ -68,7 +68,7 @@ param allowedLocations array = [
   'australiacentral'
 ]
 
-resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2023-04-01' = {
+resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2025-03-01' = {
   name: 'locationRestriction'
   properties: {
     policyType: 'Custom'
@@ -88,7 +88,7 @@ resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2023-04-01'
   }
 }
 
-resource policyAssignment 'Microsoft.Authorization/policyAssignments@2024-04-01' = {
+resource policyAssignment 'Microsoft.Authorization/policyAssignments@2025-03-01' = {
   name: 'locationAssignment'
   properties: {
     policyDefinitionId: policyDefinition.id
@@ -149,7 +149,7 @@ param adminLogin string
 @secure()
 param adminPassword string
 
-resource sqlServer 'Microsoft.Sql/servers@2023-08-01-preview' = {
+resource sqlServer 'Microsoft.Sql/servers@2024-11-01-preview' = {
   ...
 }
 ```
@@ -237,7 +237,7 @@ Other `list` functions have different return formats. To see the format of a fun
 The following example deploys a storage account and then calls `listKeys` on that storage account. The key is used when setting a value for [deployment scripts](../templates/deployment-script-template.md).
 
 ```bicep
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: 'dscript${uniqueString(resourceGroup().id)}'
   location: location
   kind: 'StorageV2'
@@ -454,7 +454,7 @@ param allowedLocations array = [
 var mgScope = tenantResourceId('Microsoft.Management/managementGroups', targetMG)
 var policyDefinitionName = 'LocationRestriction'
 
-resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2023-04-01' = {
+resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2025-03-01' = {
   name: policyDefinitionName
   properties: {
     policyType: 'Custom'
@@ -474,7 +474,7 @@ resource policyDefinition 'Microsoft.Authorization/policyDefinitions@2023-04-01'
   }
 }
 
-resource location_lock 'Microsoft.Authorization/policyAssignments@2024-04-01' = {
+resource location_lock 'Microsoft.Authorization/policyAssignments@2025-03-01' = {
   name: 'location-lock'
   properties: {
     scope: mgScope
@@ -581,7 +581,7 @@ The following example deploys a storage account. The first two outputs give you
 param storageAccountName string = uniqueString(resourceGroup().id)
 param location string = resourceGroup().location
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: storageAccountName
   location: location
   kind: 'Storage'
@@ -635,7 +635,7 @@ For example:
 param storageAccountName string
 param location string = resourceGroup().location
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: storageAccountName
   location: location
   kind: 'Storage'
@@ -743,7 +743,7 @@ param policyDefinitionID string = '0a914e76-4921-4c19-b460-a2d36003525a'
 @description('Specifies the name of the policy assignment, can be used defined or an idempotent name as the defaultValue provides.')
 param policyAssignmentName string = guid(policyDefinitionID, resourceGroup().name)
 
-resource policyAssignment 'Microsoft.Authorization/policyAssignments@2024-04-01' = {
+resource policyAssignment 'Microsoft.Authorization/policyAssignments@2025-03-01' = {
   name: policyAssignmentName
   properties: {
     scope: subscriptionResourceId('Microsoft.Resources/resourceGroups', resourceGroup().name)
@@ -807,7 +807,7 @@ param location string = 'westus2'
 
 var logicalZone = toLogicalZone(subscriptionId, location, physicalZone)
 
-resource vm 'Microsoft.Compute/virtualMachines@2024-03-01' = {
+resource vm 'Microsoft.Compute/virtualMachines@2025-04-01' = {
   name: 'myVM'
   location: location
   zones: logicalZone != '' ? [logicalZone] : []
@@ -921,7 +921,7 @@ param location string = 'westus2'
 
 var physicalZone = toPhysicalZone(subscriptionId, location, logicalZone)
 
-resource vm 'Microsoft.Compute/virtualMachines@2024-03-01' = {
+resource vm 'Microsoft.Compute/virtualMachines@2025-04-01' = {
   name: 'myVM'
   location: location
   zones: [logicalZone]

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

@@ -95,7 +95,7 @@ targetScope = 'managementGroup'
 
 param mgName string = 'mg-${uniqueString(newGuid())}'
 
-resource newMG 'Microsoft.Management/managementGroups@2023-04-01' = {
+resource newMG 'Microsoft.Management/managementGroups@2024-02-01-preview' = {
   scope: tenant()
   name: mgName
   properties: {
@@ -319,7 +319,7 @@ It returns:
 Some resources require setting the tenant ID for a property. Rather than passing the tenant ID as a parameter, you can retrieve it with the tenant function.
 
 ```bicep
-resource kv 'Microsoft.KeyVault/vaults@2023-07-01' = {
+resource kv 'Microsoft.KeyVault/vaults@2025-05-01' = {
   name: 'examplekeyvault'
   location: 'westus'
   properties: {

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

@@ -907,7 +907,7 @@ param guidValue string = newGuid()
 
 var storageName = 'storage${uniqueString(guidValue)}'
 
-resource myStorage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource myStorage 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: storageName
   location: 'West US'
   sku: {
@@ -1502,7 +1502,7 @@ uniqueString(resourceGroup().id, deployment().name)
 The following example shows how to create a unique name for a storage account based on your resource group. Inside the resource group, the name isn't unique if constructed the same way.
 
 ```bicep
-resource mystorage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource mystorage 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: 'storage${uniqueString(resourceGroup().id)}'
   ...
 }

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

@@ -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@2024-01-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2025-06-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@2024-01-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -128,12 +128,12 @@ resource storage 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   }
 }
 
-resource service 'Microsoft.Storage/storageAccounts/fileServices@2024-01-01' = {
+resource service 'Microsoft.Storage/storageAccounts/fileServices@2025-06-01' = {
   name: 'default'
   parent: storage
 }
 
-resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2024-01-01' = {
+resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2025-06-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@2024-01-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2025-06-01' = {
   name: 'examplestorage'
   location: resourceGroup().location
   kind: 'StorageV2'
@@ -155,14 +155,14 @@ resource storage 'Microsoft.Storage/storageAccounts@2024-01-01' = {
   }
 }
 
-resource service 'Microsoft.Storage/storageAccounts/fileServices@2024-01-01' = {
+resource service 'Microsoft.Storage/storageAccounts/fileServices@2025-06-01' = {
   name: 'examplestorage/default'
   dependsOn: [
     storage
   ]
 }
 
-resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2024-01-01' = {
+resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2025-06-01' = {
   name: 'examplestorage/default/exampleshare'
   dependsOn: [
     service

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

@@ -134,7 +134,7 @@ targetScope = 'subscription'
 To declare a resource:
 
 ```bicep
-resource virtualMachine 'Microsoft.Compute/virtualMachines@2024-03-01' = {
+resource virtualMachine 'Microsoft.Compute/virtualMachines@2025-04-01' = {
   ...
 }
 ```
@@ -152,7 +152,7 @@ resource virtualMachine 'Microsoft.Compute/virtualMachines@2024-03-01' = {
 To conditionally deploy a resource:
 
 ```bicep
-resource virtualMachine 'Microsoft.Compute/virtualMachines@2024-03-01' = if(deployVM) {
+resource virtualMachine 'Microsoft.Compute/virtualMachines@2025-04-01' = if(deployVM) {
   ...
 }
 ```
@@ -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@2024-05-01' = {
+resource netSecurityGroup 'Microsoft.Network/networkSecurityGroups@2025-01-01' = {
   ...
 }
 
-resource nic1 'Microsoft.Network/networkInterfaces@2024-05-01' = {
+resource nic1 'Microsoft.Network/networkInterfaces@2025-01-01' = {
   name: nic1Name
   location: location
   properties: {

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

@@ -60,7 +60,7 @@ param location string = resourceGroup().location
 ])
 param newOrExisting string = 'new'
 
-resource saNew 'Microsoft.Storage/storageAccounts@2023-04-01' = if (newOrExisting == 'new') {
+resource saNew 'Microsoft.Storage/storageAccounts@2025-06-01' = if (newOrExisting == 'new') {
   name: storageAccountName
   location: location
   sku: {
@@ -92,7 +92,7 @@ param vmName string
 param location string
 param logAnalytics string = ''
 
-resource vmName_omsOnboarding 'Microsoft.Compute/virtualMachines/extensions@2024-03-01' = if (!empty(logAnalytics)) {
+resource vmName_omsOnboarding 'Microsoft.Compute/virtualMachines/extensions@2025-04-01' = if (!empty(logAnalytics)) {
   name: '${vmName}/omsOnboarding'
   location: location
   properties: {