update api versions

Author: mumian

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

@@ -164,7 +164,7 @@ param subscriptionId string
 param kvResourceGroup string
 param kvName string
 
-resource keyVault 'Microsoft.KeyVault/vaults@2023-07-01' existing = {
+resource keyVault 'Microsoft.KeyVault/vaults@2025-05-01' existing = {
   name: kvName
   scope: resourceGroup(subscriptionId, kvResourceGroup )
 }
@@ -601,7 +601,7 @@ To get a property from an existing resource that isn't deployed in the template,
 ```bicep
 param storageAccountName string
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: storageAccountName
 }
 
@@ -652,7 +652,7 @@ To get the resource ID for a resource that isn't deployed in the Bicep file, use
 ```bicep
 param storageAccountName string
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: storageAccountName
 }
 

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

@@ -63,7 +63,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-10-01' existing = {
+resource aks 'Microsoft.ContainerService/managedClusters@2025-08-02-preview' existing = {
   name: 'demoAKSCluster'
 }
 

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

@@ -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@2024-01-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: storageAccountName
 }
 

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

@@ -69,7 +69,7 @@ resource saNew 'Microsoft.Storage/storageAccounts@2025-06-01' = if (newOrExistin
   kind: 'StorageV2'
 }
 
-resource saExisting 'Microsoft.Storage/storageAccounts@2023-04-01' existing = if (newOrExisting == 'existing') {
+resource saExisting 'Microsoft.Storage/storageAccounts@2025-06-01' existing = if (newOrExisting == 'existing') {
   name: storageAccountName
 }
 

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

@@ -72,7 +72,7 @@ Suppose you have the following ARM template:
   "resources": [
     {
       "type": "Microsoft.Storage/storageAccounts",
-      "apiVersion": "2023-04-01",
+      "apiVersion": "2025-06-01",
       "name": "[variables('storageAccountName')]",
       "location": "[parameters('location')]",
       "sku": {

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

@@ -161,7 +161,7 @@ param storageAccountData {
 var storageBlobDataReaderRoleId = '2a2b9908-6ea1-4ae2-8e65-a410df84e7d1'
 
 @description('The storage account to read blobs from.')
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: storageAccountData.name
 }
 

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

@@ -131,15 +131,15 @@ param vnetName string
 param subnetName string
 param userAssignedIdentityName string
 
-resource vnet 'Microsoft.Network/virtualNetworks@2024-05-01' existing = {
+resource vnet 'Microsoft.Network/virtualNetworks@2025-01-01' existing = {
   name: vnetName
 
   resource subnet 'subnets' existing = {
     name: subnetName
   }
 }
 
-resource userAssignedIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2024-11-30' existing = {
+resource userAssignedIdentity 'Microsoft.ManagedIdentity/userAssignedIdentities@2025-01-31-preview' existing = {
   name: userAssignedIdentityName
 }
 

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

@@ -17,7 +17,7 @@ The resource doesn't deploy again when the `existing` keyword references it.
 The following example gets an existing storage account in the same resource group as the current deployment. Notice that you provide only the name of the existing resource. The properties are available through the symbolic name.
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: 'examplestorage'
 }
 
@@ -29,7 +29,7 @@ output blobEndpoint string = stg.properties.primaryEndpoints.blob
 Set the `scope` property to access a resource in a different scope. The following example references an existing storage account in a different resource group:
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: 'examplestorage'
   scope: resourceGroup(exampleRG)
 }

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

@@ -192,7 +192,7 @@ param subscriptionId string
 param kvResourceGroup string
 param kvName string
 
-resource kv 'Microsoft.KeyVault/vaults@2023-07-01' existing = {
+resource kv 'Microsoft.KeyVault/vaults@2025-05-01' existing = {
   name: kvName
   scope: resourceGroup(subscriptionId, kvResourceGroup )
 }

articles/azure-resource-manager/bicep/linter-rule-no-unused-existing-resources.md

@@ -23,7 +23,7 @@ To reduce confusion in your template, delete any [existing resources](./existing
 The following example fails this test because the existing resource **stg** is declared but never used:
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2023-05-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2025-06-01' existing = {
   name: 'examplestorage'
 }
 ```