Merge pull request #298890 from MicrosoftDocs/main

4/25/2025 PM Publish

Author: Albertyang0

articles/api-management/export-api-power-platform.md

@@ -15,7 +15,7 @@ ms.custom: engagement-fy23
 
 [!INCLUDE [api-management-availability-all-tiers](../../includes/api-management-availability-all-tiers.md)]
 
-Citizen developers using the Microsoft [Power Platform](https://powerplatform.microsoft.com) often need to reach the business capabilities that are developed by professional developers and deployed in Azure. [Azure API Management](https://aka.ms/apimrocks) enables professional developers to publish their backend service as APIs, and easily export these APIs to the Power Platform ([Power Apps](/powerapps/powerapps-overview) and [Power Automate](/power-automate/getting-started)) as custom connectors for discovery and consumption by citizen developers. 
+Citizen developers using the Microsoft [Power Platform](https://powerplatform.microsoft.com) often need to reach the business capabilities that are developed by professional developers and deployed in Azure. [Azure API Management](https://aka.ms/apimrocks) enables professional developers to publish their backend service as APIs, and easily export these APIs to the Power Platform ([Copilot Studio](/microsoft-copilot-studio/fundamentals-what-is-copilot-studio), [Power Apps](/powerapps/powerapps-overview) and [Power Automate](/power-automate/getting-started)) as custom connectors for discovery and consumption by citizen developers. 
 
 This article walks through the steps in the Azure portal to create a Power Platform [custom connector](/connectors/custom-connectors/) to an API in API Management. With this capability, citizen developers can use the Power Platform to create and distribute apps that are based on internal and external APIs managed by API Management.
 ## Prerequisites

articles/app-service/invoke-openapi-web-app-from-azure-ai-agent-service.md

@@ -10,28 +10,24 @@ metadata:
   ms.author: jgao
   ms.subservice: bicep
   ms.topic: landing-page
-  ms.date: 03/17/2025
+  ms.date: 04/24/2025
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
 landingContent:
   # Card (optional)
-  - title: Bicep
+  - title: Get started
     linkLists:
       - linkListType: overview
         links:
           - text: What is Bicep?
             url: overview.md
-      - linkListType: video
+      - linkListType: get-started
         links:
-          - text: Learn live - Bicep
-            url: /events/learntv/learnlive-iac-and-bicep/
-          - text: Learn Live - Bicep and GitHub Actions
-            url: /events/learn-events/learnlive-automate-azure-deployments-bicep-github-actions/
-
-  # Card (optional)
-  - title: Get started
-    linkLists:
+          - text: Install Bicep tools
+            url: install.md
+          - text: Decompile JSON to Bicep
+            url: decompile.md
       - linkListType: quickstart
         links:
           - text: Create Bicep files - VS Code
@@ -42,10 +38,6 @@ landingContent:
             url: quickstart-create-template-specs.md
           - text: Create deployment stacks
             url: quickstart-create-deployment-stacks.md
-          - text: Use private module registry
-            url: quickstart-private-module-registry.md
-          - text: Create and deploy Microsoft Graph resources
-            url: https://learn.microsoft.com/graph/templates/quickstart-create-bicep-interactive-mode
       - linkListType: learn
         links:
           - text: Fundamentals of Bicep
@@ -54,100 +46,111 @@ landingContent:
             url: /training/paths/intermediate-bicep/
           - text: Advanced Bicep
             url: /training/paths/advanced-bicep/
-          - text: Use deployment stacks
+          - text: Deployment stacks
             url: /training/modules/introduction-to-deployment-stacks/
-
+      - linkListType: video
+        links:
+          - text: Learn live - Bicep
+            url: /events/learntv/learnlive-iac-and-bicep/
+          - text: Learn Live - Bicep and GitHub Actions
+            url: /events/learn-events/learnlive-automate-azure-deployments-bicep-github-actions/
+      - linkListType: how-to-guide
+        links:
+          - text: Best practices
+            url: best-practices.md
   # Card
   - title: Author Bicep files
     linkLists:
       - linkListType: how-to-guide
         links:
           - text: Bicep file structure & syntax
             url: ./file.md
-          - text: Define parameters
-            url: ./parameters.md
-          - text: Define variables
-            url: ./variables.md
           - text: Define resources
             url: ./resource-declaration.md
           - text: Define modules
             url: ./modules.md
-          - text: Define outputs
-            url: ./outputs.md
           - text: User-defined data types
             url: ./user-defined-data-types.md
           - text: User-defined functions
             url: ./user-defined-functions.md
+          - text: Create parameters file
+            url: ./parameter-files.md
+          - text: Use iterative loops
+            url: ./loops.md
+          - text: Use conditionals
+            url: ./conditional-resource-deployment.md
+          - text: Reference existing resources
+            url: ./existing-resource.md
+          - text: Use deployment script
+            url: ./deployment-script-bicep.md
       - linkListType: reference
         links:
           - text: Data types
             url: ./data-types.md
-          - text: Operators
-            url: ./operators.md
           - text: Functions
             url: ./bicep-functions.md
+          - text: Operators
+            url: ./operators.md
   # Card
   - title: Deploy Bicep files
     linkLists:
+      - linkListType: how-to-guide
+        links:
+          - text: Deploy with Azure CLI
+            url: deploy-cli.md
+          - text: Deploy with Azure PowerShell
+            url: deploy-powershell.md
+          - text: Deploy with Cloud Shell
+            url: deploy-cloud-shell.md
+          - text: Use What-if operation
+            url: deploy-what-if.md
       - linkListType: quickstart
         links:
           - text: Bicep with pipelines
             url: add-template-to-azure-pipelines.md
           - text: Bicep with GitHub Actions
             url: deploy-github-actions.md
+  # Card
+  - title: Patterns
+    linkLists:
       - linkListType: how-to-guide
         links:
-          - text: PowerShell
-            url: deploy-powershell.md
-          - text: Azure CLI
-            url: deploy-cli.md
-          - text: Cloud Shell
-            url: deploy-cloud-shell.md
-          - text: What-if deployment
-            url: deploy-what-if.md
+        - text: Configuration set pattern
+          url: patterns-configuration-set.md
+        - text: Shared variable file pattern
+          url: patterns-shared-variable-file.md            
   # Card
-  - title: Scoped deployments
+  - title: Deployment scopes
     linkLists:
       - linkListType: how-to-guide
         links:
-          - text: Resource group
+          - text: Resource group scope
             url: deploy-to-resource-group.md
-          - text: Subscription
+          - text: Subscription scope
             url: deploy-to-subscription.md
-          - text: Management group
+          - text: Management group scope
             url: deploy-to-management-group.md
-          - text: Tenant
+          - text: Tenant scope
             url: deploy-to-tenant.md
-          - text: Scoping extension resource
+          - text: Scope extension resource
             url: scope-extension-resources.md
   # Card
-  - title: Guidance & patterns
-    linkLists:
-      - linkListType: how-to-guide
-        links:
-        - text: Best practices
-          url: best-practices.md
-        - text: Configuration set pattern
-          url: patterns-configuration-set.md
-        - text: Shared variable file pattern
-          url: patterns-shared-variable-file.md
-  # Card
   - title: Explore reference content
     linkLists:
       - linkListType: reference
         links:
         - text: Bicep resource reference
           url: /azure/templates/
-        - text: Bicep CLI
-          url: ./bicep-cli.md
-        - text: Bicep core diagnostics
-          url: ./bicep-core-diagnostics.md
         - text: Azure Quickstart Templates
           url: https://azure.microsoft.com/resources/templates/
+        - text: Bicep CLI reference
+          url: ./bicep-cli.md
+        - text: Bicep warning and error codes
+          url: ./bicep-core-diagnostics.md
+        - text: Azure CLI reference
+          url: /cli/azure/resource
+        - text: Azure PowerShell reference
+          url: /powershell/module/az.resources
         - text: Microsoft Graph Bicep reference
           url: https://learn.microsoft.com/graph/templates/reference/overview
-        - text: Azure PowerShell
-          url: /powershell/module/az.resources
-        - text: Azure CLI
-          url: /cli/azure/resource
 

articles/app-service/media/invoke-openapi-web-app-from-azure-ai-agent-service/browse-app.png

@@ -3,7 +3,7 @@ title: Create virtual network resources by using Bicep
 description: Describes how to create virtual networks, network security groups, and route tables by using Bicep.
 ms.topic: conceptual
 ms.custom: devx-track-bicep
-ms.date: 03/17/2025
+ms.date: 04/25/2025
 ---
 
 # Create virtual network resources by using Bicep
@@ -16,69 +16,12 @@ Define your virtual networks by creating a resource with the type [`Microsoft.Ne
 
 ### Configure subnets by using the subnets property
 
-Virtual networks contain subnets, which are logical groups of IP addresses within the virtual network. There are two ways to define subnets in Bicep: by using the `subnets` property on the virtual network resource, and by creating a [child resource](child-resource-name-type.md) with type `Microsoft.Network/virtualNetworks/subnets`.
+Virtual networks contain subnets, which are logical groupings of IP addresses within the network. Subnets should always be managed as child resources, and the **subnets** property should never be defined within the virtual network resource. This approach ensures a safe and independent lifecycle for both resource types.
 
-> [!WARNING]
-> Avoid defining subnets as child resources. This approach can result in downtime for your resources during subsequent deployments, or failed deployments.
+> [!NOTE]
+> The Azure Virtual Network API is updated to allow modifications to virtual networks without requiring the inclusion of the subnet property in PUT requests. Previously, omitting the subnet property would result in the deletion of existing subnets. With the new behavior, if the subnet property isn't included in a PUT request, the existing subnets remain unchanged. Explicitly setting the subnet property to an empty value deletes all existing subnets, while providing specific subnet configurations creates or updates subnets accordingly. This change simplifies virtual network management by preventing unintended subnet deletions during updates. For more information, see [Azure Virtual Network now supports updates without subnet property](https://techcommunity.microsoft.com/blog/azurenetworkingblog/azure-virtual-network-now-supports-updates-without-subnet-property/4067952).
 
-It's best to define your subnets within the virtual network definition, as in this example:
-
-> The following example is part of a larger example. For a Bicep file that you can deploy, [see the complete file](https://raw.githubusercontent.com/Azure/azure-docs-bicep-samples/main/samples/scenarios-virtual-networks/vnet.bicep).
-
-```bicep
-param location string = resourceGroup().location
-
-var virtualNetworkName = 'my-vnet'
-var subnet1Name = 'Subnet-1'
-var subnet2Name = 'Subnet-2'
-
-resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
-  name: virtualNetworkName
-  location: location
-  properties: {
-    addressSpace: {
-      addressPrefixes: [
-        '10.0.0.0/16'
-      ]
-    }
-    subnets: [
-      {
-        name: subnet1Name
-        properties: {
-          addressPrefix: '10.0.0.0/24'
-        }
-      }
-      {
-        name: subnet2Name
-        properties: {
-          addressPrefix: '10.0.1.0/24'
-        }
-      }
-    ]
-  }
-
-  resource subnet1 'subnets' existing = {
-    name: subnet1Name
-  }
-
-  resource subnet2 'subnets' existing = {
-    name: subnet2Name
-  }
-}
-
-output subnet1ResourceId string = virtualNetwork::subnet1.id
-output subnet2ResourceId string = virtualNetwork::subnet2.id
-```
-
-Although both approaches enable you to define and create your subnets, there is an important difference. When you define subnets by using child resources, the first time your Bicep file is deployed, the virtual network is deployed. Then, after the virtual network deployment is complete, each subnet is deployed. This sequencing occurs because Azure Resource Manager deploys each individual resource separately.
-
-When you redeploy the same Bicep file, the same deployment sequence occurs. However, the virtual network is deployed without any subnets configured on it because the `subnets` property is effectively empty. Then, after the virtual network is reconfigured, the subnet resources are redeployed, which re-establishes each subnet. In some situations, this behavior causes the resources within your virtual network to lose connectivity during your deployment. In other situations, Azure prevents you from modifying the virtual network and your deployment fails.
-
-### Access subnet resource IDs
-
-You often need to refer to a subnet's resource ID. When you use the `subnets` property to define your subnet, [you can use the `existing` keyword](existing-resource.md) to also obtain a strongly typed reference to the subnet, and then access the subnet's `id` property:
-
-> The following example is part of a larger example. For a Bicep file that you can deploy, [see the complete file](https://raw.githubusercontent.com/Azure/azure-docs-bicep-samples/main/samples/scenarios-virtual-networks/vnet.bicep).
+It's best to define your subnets as [child resources](./child-resource-name-type.md#within-parent-resource), as in this example:
 
 ```bicep
 param location string = resourceGroup().location
@@ -87,7 +30,7 @@ var virtualNetworkName = 'my-vnet'
 var subnet1Name = 'Subnet-1'
 var subnet2Name = 'Subnet-2'
 
-resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
+resource virtualNetwork 'Microsoft.Network/virtualNetworks@2024-05-01' = {
   name: virtualNetworkName
   location: location
   properties: {
@@ -96,38 +39,27 @@ resource virtualNetwork 'Microsoft.Network/virtualNetworks@2023-11-01' = {
         '10.0.0.0/16'
       ]
     }
-    subnets: [
-      {
-        name: subnet1Name
-        properties: {
-          addressPrefix: '10.0.0.0/24'
-        }
-      }
-      {
-        name: subnet2Name
-        properties: {
-          addressPrefix: '10.0.1.0/24'
-        }
-      }
-    ]
   }
 
-  resource subnet1 'subnets' existing = {
+  resource subnet1 'subnets' = {
     name: subnet1Name
-  }
+    properties: {
+      addressPrefix: '10.0.0.0/24'
+    }  }
 
-  resource subnet2 'subnets' existing = {
+  resource subnet2 'subnets' = {
     name: subnet2Name
+    properties: {
+      addressPrefix: '10.0.1.0/24'
+    }    
   }
 }
 
 output subnet1ResourceId string = virtualNetwork::subnet1.id
 output subnet2ResourceId string = virtualNetwork::subnet2.id
 ```
 
-Because this example uses the `existing` keyword to access the subnet resource, instead of defining the complete subnet resource, it doesn't have the risks outlined in the previous section.
-
-You can also combine the `existing` and `scope` keywords to refer to a virtual network or subnet resource in another resource group.
+To reference a nested resource outside the parent resource, it must be qualified with the containing resource name and the :: operator as shown in the preceding example.
 
 ## Network security groups
 
@@ -148,4 +80,3 @@ Private endpoint approval is an operation, so you can't perform it directly with
 - Quickstart templates
   - [Create a Virtual Network with two Subnets](https://azure.microsoft.com/resources/templates/vnet-two-subnets/)
   - [Virtual Network with diagnostic logs](https://github.com/Azure/azure-quickstart-templates/tree/master/quickstarts/microsoft.network/vnet-create-with-diagnostic-logs)
-