Merge pull request #299111 from MicrosoftDocs/main

4/30/2025 AM Publish

Author: Taojunshen

articles/api-management/api-management-region-availability.md

@@ -6,7 +6,7 @@ author: dlepow
 
 ms.service: azure-api-management
 ms.topic: concept-article
-ms.date: 11/20/2024
+ms.date: 04/29/2025
 ms.author: danlep
 ms.custom: references_regions
 ---
@@ -47,10 +47,11 @@ Information in the following table is updated regularly. Capacity availability i
 | Switzerland North | ✅ |✅ |  | |
 | UK South | ✅  | ✅ | ✅ | ✅ |
 | UK West | ✅  | ✅ | | |
-| West Europe  | ✅ | ✅ | |  |
+| West Europe  | ✅ | ✅ | | ✅<sup>1</sup> |
 | West US | ✅ | ✅ |  | ✅ |
 | West US 2 | ✅ | ✅ |  | |
 
+<sup>1</sup> Request access to this region by emailing `[email protected]` 
 
 ## Related content
 

articles/automation/automation-runbook-types.md

@@ -364,5 +364,5 @@ You can create and edit graphical and graphical PowerShell Workflow runbooks usi
 
 * To learn about PowerShell runbooks, see [Tutorial: Create a PowerShell runbook](./learn/powershell-runbook-managed-identity.md).
 * To learn about PowerShell Workflow runbooks, see [Tutorial: Create a PowerShell Workflow runbook](learn/automation-tutorial-runbook-textual.md).
-* To learn about graphical runbooks, see [Tutorial: Create a graphical runbook](./learn/powershell-runbook-managed-identity.md).
+* To learn about graphical runbooks, see [Tutorial: Create a graphical runbook](automation-graphical-authoring-intro.md).
 * To learn about Python runbooks, see [Tutorial: Create a Python runbook](./learn/automation-tutorial-runbook-textual-python-3.md).

articles/azure-app-configuration/media/azure-app-configuration-create/azure-portal-basic-tab.png

@@ -7,7 +7,7 @@ ms.service: azure-app-configuration
 ms.devlang: csharp
 ms.custom: devx-track-csharp, mode-other
 ms.topic: quickstart
-ms.date: 03/25/2024
+ms.date: 04/16/2025
 
 #Customer intent: As an Azure developer, I want to create an app configuration store to manage all my app settings in one place using Azure App Configuration.
 ---
@@ -44,9 +44,6 @@ An Azure account with an active subscription. [Create one for free](https://azur
     :::image type="content" source="media/azure-app-configuration-create/azure-portal-basic-tab.png" alt-text="Screenshot of the Azure portal that shows the basic tab of the creation for with the free tier selected.":::
 
 1. Select **Review + create** to validate your settings.
-
-    :::image type="content" source="media/azure-app-configuration-create/azure-portal-review.png" alt-text="Screenshot of the Azure portal that shows the configuration settings in the Review + create tab.":::
-
 1. Select **Create**. The deployment might take a few minutes.
 1. After the deployment finishes, go to the App Configuration resource. Select **Settings** > **Access keys**. Make a note of the primary read-only key connection string. You'll use this connection string later to configure your application to communicate with the App Configuration store that you created.
 
@@ -125,8 +122,9 @@ az group delete --name <name>
 
 ---
 
-## Next steps
+## Next step
 
 Advance to the next article to learn how to create an ASP.NET Core app with Azure App Configuration to centralize storage and management of its application settings.
+
 > [!div class="nextstepaction"]
 > [Quickstart ASP.NET Core](quickstart-aspnet-core-app.md)

articles/azure-app-configuration/media/azure-app-configuration-create/azure-portal-review.png

@@ -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-app-configuration/quickstart-azure-app-configuration-create.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-config-linter.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/bicep-config-modules.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/bicep-kubernetes-extension.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
 }