Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into copstu

Author: gitName

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

@@ -14,7 +14,7 @@ ms.custom: fasttrack-edit, references_regions
 
 Application Gateway and WAF can be configured to scale in two modes:
 
-- **Autoscaling** - With autoscaling enabled, the Application Gateway and WAF v2 SKUs scale out or in based on application traffic requirements. This mode offers better elasticity to your application and eliminates the need to guess the application gateway size or instance count. This mode also allows you to save cost by not requiring the gateway to run at peak-provisioned capacity for expected maximum traffic load. You must specify a minimum and optionally maximum instance count. Minimum capacity ensures that Application Gateway and WAF v2 don't fall below the minimum instance count specified, even without traffic. Each instance is roughly equivalent to 10 more reserved Capacity Units. Zero signifies no reserved capacity and is purely autoscaling in nature. You can also optionally specify a maximum instance count, which ensures that the Application Gateway doesn't scale beyond the specified number of instances. You are only billed for the amount of traffic served by the Gateway. The instance counts can range from 0 to 125. The default value for maximum instance count is 10 if not specified. Autoscaling should always be enabled to minimize the impact of any zonal failure. 
+- **Autoscaling** - With autoscaling enabled, the Application Gateway and WAF v2 SKUs scale out or in based on application traffic requirements. This mode offers better elasticity to your application and eliminates the need to guess the application gateway size or instance count. This mode also allows you to save cost by not requiring the gateway to run at peak-provisioned capacity for expected maximum traffic load. You must specify a minimum and optionally maximum instance count. Minimum capacity ensures that Application Gateway and WAF v2 don't fall below the minimum instance count specified, even without traffic. The minimum instance count can range from 0 to 100. Each instance is roughly equivalent to 10 more reserved Capacity Units. Zero signifies no reserved capacity and is purely autoscaling in nature. You can also optionally specify a maximum instance count, which ensures that the Application Gateway doesn't scale beyond the specified number of instances. You are only billed for the amount of traffic served by the Gateway. The instance counts can range from 0 to 125. The default value for maximum instance count is 10 if not specified. Autoscaling should always be enabled to minimize the impact of any zonal failure. 
 
 > [!NOTE]
 > If the maximum instance count is updated to a value less than the current instance count, the new setting will not take immediate effect. The newly updated maximum will only be enforced after a scale-in operation brings  the  current count below newly updated maximum count. If the scale-in operation does not occur because the autoscaling  scale in thresholds are not met, the new maximum setting will not be applied.

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

@@ -46,7 +46,7 @@ For Application Gateway v2 SKU, the following metrics are available. What follow
 - **Client TLS protocol**. Count of TLS and non-TLS requests.
 - **Current capacity units**. There are three determinants to capacity unit: compute unit, persistent connections, and throughput. Each capacity unit is composed of at most one compute unit, or 2500 persistent connections, or 2.22-Mbps throughput.
 - **Current compute units**. Factors affecting compute unit are TLS connections/sec, URL Rewrite computations, and WAF rule processing.
-- **Current connections**. The total number of concurrent connections active from clients to the Application Gateway.
+- **Current connections**. The total number of concurrent connections active from clients to the Application Gateway, including probes for the health of the application gateway's instances.
 - **Estimated Billed Capacity units**. With the v2 SKU, consumption drives the pricing model. Capacity units measure consumption-based cost that is charged in addition to the fixed cost. *Estimated Billed Capacity units indicate the number of capacity units using which the billing is estimated. This amount is calculated as the greater value between *Current capacity units* (capacity units required to load balance the traffic) and *Fixed billable capacity units* (minimum capacity units kept provisioned).
 - **Failed Requests**. This value includes the 5xx codes that are generated from the Application Gateway and the 5xx codes that are generated from the backend. The request count can be further filtered to show count per each/specific backend pool-http setting combination.
 - **Fixed Billable Capacity Units**. The minimum number of capacity units kept provisioned as per the *Minimum scale units* setting in the Application Gateway configuration. One instance translates to 10 capacity units.

articles/application-gateway/application-gateway-autoscaling-zone-redundant.md

@@ -1,11 +1,11 @@
 ---
-title: Configure Unix permissions and change ownership mode for Azure NetApp Files NFS and dual-protocol volumes | Microsoft Docs
-description: Describes how to set the Unix permissions and the change ownership mode options for Azure NetApp Files NFS and dual-protocol volumes.
+title: Configure Unix permissions and change ownership mode for Azure NetApp Files NFS and dual-protocol volumes
+description: Learn how to set the Unix permissions and the change ownership mode options for Azure NetApp Files NFS and dual-protocol volumes.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
 ms.topic: how-to
-ms.date: 02/28/2023
+ms.date: 04/25/2025
 ms.author: anfdocs
 ---
 # Configure Unix permissions and change ownership mode for NFS and dual-protocol volumes
@@ -22,31 +22,35 @@ The Unix permissions setting is set to `0770` by default. This default setting g
 
 ## Change ownership mode   
 
-The change ownership mode (**`Chown Mode`**) functionality enables you to set the ownership management capabilities of files and directories.  You can specify or modify the setting under a volume's export policy. Two options for **`Chown Mode`** are available:   
+The change ownership mode (**`Chown Mode`**) functionality enables you to set the ownership management capabilities of files and directories. You can specify or modify the setting under a volume's export policy. Two options for **`Chown Mode`** are available:   
 
 * `Restricted` (default) - Only the root user can change the ownership of files and directories.
 * `Unrestricted` - Non-root users can change the ownership for files and directories that they own.
 
 ## Considerations  
 
 * The Unix permissions you specify apply only for the volume mount point (root directory).  
-* You can modify the Unix permissions on the source volume *but not on the destination volume* that is in a cross-region replication configuration.
+* You can modify the Unix permissions on the source volume *but not the destination volume* that is in a replication configuration.
 
-## Steps
+## Set Unix permissions for new volumes
 
 1. You can specify the **Unix permissions** and change ownership mode (**`Chown Mode`**) settings under the **Protocol** tab when you [create an NFS volume](azure-netapp-files-create-volumes.md) or [create a dual-protocol volume](create-volumes-dual-protocol.md). 
 
-    The following example shows the Create a Volume screen for an NFS volume. 
+    The following example shows the Create a volume screen for an NFS volume. 
 
-    ![Screenshots that shows the Create a Volume screen for NFS.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-create-nfs-volume.png)
+    ![Screenshot that shows the Create a Volume screen for NFS.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-create-nfs-volume.png)
 
-2. For existing NFS or dual-protocol volumes, you can set or modify **Unix permissions** and **change ownership mode** as follows:  
+## Set Unix permissions for existing volumes
 
-    1. To modify Unix permissions, right-click the **volume**, and select **Edit**. In the Edit window that appears, specify a value for **Unix Permissions**.  
-        ![Screenshots that shows the Edit screen for Unix permissions.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-edit.png)
+For existing NFS or dual-protocol volumes, you can set or modify **Unix permissions** and **change ownership mode** as follows:  
 
-    2. To modify the change ownership mode, click the **volume**, click **Export policy**, then modify the **`Chown Mode`** setting.  
-        ![Screenshots that shows the Export Policy screen.](./media/configure-unix-permissions-change-ownership-mode/chown-mode-edit.png)
+1. To modify Unix permissions, right-click the **volume**, and select **Edit**. In the Edit window that appears, specify a value for **Unix Permissions**.
+
+    ![Screenshot that shows the Edit screen for Unix permissions.](./media/configure-unix-permissions-change-ownership-mode/unix-permissions-edit.png)
+
+2. To modify the change ownership mode, select the **volume**, click **Export policy** then modify the **`Chown Mode`** setting.  
+
+    ![Screenshot that shows the Export Policy screen.](./media/configure-unix-permissions-change-ownership-mode/chown-mode-edit.png)
 
 ## Next steps  
 

articles/application-gateway/monitor-application-gateway-reference.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