Merge branch 'main' into release-build-functions-bindings-mongodb-preview

Author: v-alje

articles/app-service/overview-diagnostics.md

@@ -15,7 +15,7 @@ This article explains how to troubleshoot issues with your app in Azure App Serv
 
 Azure App Service diagnostics is an interactive experience to help you troubleshoot your app with no configuration required. App Service diagnostics points out what's wrong and guides you to the right information to more easily and quickly troubleshoot and resolve the problem.
 
-Although this experience is most helpful for problems that occured within the last 24 hours, all the diagnostic graphs are always available for you to analyze.
+Although this experience is most helpful for problems that occurred within the last 24 hours, all the diagnostic graphs are always available for you to analyze.
 
 App Service diagnostics works for not only apps on Windows, but also for apps on built-in or custom containers, [App Service Environments](./environment/intro.md), and [Azure Functions](../azure-functions/functions-overview.md).
 

articles/app-service/tutorial-java-jboss-mysql-app.md

@@ -665,7 +665,7 @@ If you see the error: `The subscription '701ea799-fb46-4407-bb67-9cbcf289f1c7' i
 
 Depending on your subscription and the region you select, you might see the deployment status for Azure Database for MySQL Flexible Server to be `Conflict`, with the following message in Operation details:
 
-`InternalServerError: An unexpected error occured while processing the request.`
+`InternalServerError: An unexpected error occurred while processing the request.`
 
 This error is most likely caused by a limit on your subscription for the region you select. Try choosing a different region for your deployment.
 

articles/app-service/tutorial-java-tomcat-mysql-app.md

@@ -697,7 +697,7 @@ You can ignore the warnings. The Maven Jetty plugin shows the warnings because t
 
 Depending on your subscription and the region you select, you might see the deployment status for Azure Database for MySQL Flexible Server to be `Conflict`, with the following message in Operation details:
 
-`InternalServerError: An unexpected error occured while processing the request.`
+`InternalServerError: An unexpected error occurred while processing the request.`
 
 This error is most likely caused by a limit on your subscription for the region you select. Try choosing a different region for your deployment.
 

articles/application-gateway/configuration-http-settings.md

@@ -16,7 +16,7 @@ The Backend Settings enable you to manage the configurations for backend connect
 ## Types of Backend Settings in Application Gateway
 While Portal users will only see the "Backend Settings" option, API users will have access to two types of settings. You must utilize the correct configuration, according to the protocol.
 
-* Backend HTTP settings - It is for Layer 7 proxy configurations that support HTTP, HTTPS, and WebSockets protocols.
+* Backend HTTP settings - It is for Layer 7 proxy configurations that support HTTP and HTTPS protocols.
 * Backend settings - It is for Layer 4 proxy (Preview) configurations that support TLS and TCP protocols.
 
 ---

articles/application-gateway/monitor-application-gateway-reference.md

@@ -1,7 +1,7 @@
 ---
 title: Monitoring data reference for Azure Application Gateway
 description: This article contains important reference material you need when you monitor Azure Application Gateway.
-ms.date: 03/28/2025
+ms.date: 05/12/2025
 ms.custom: horz-monitor
 ms.topic: reference
 author: greg-lindsay
@@ -109,7 +109,9 @@ https://management.azure.com/subscriptions/subid/providers/Microsoft.Network/loc
 
 ### TLS/TCP proxy metrics
 
-Application Gateway supports TLS/TCP proxy monitoring. With layer 4 proxy feature now available with Application Gateway, there are some Common metrics that apply to both layer 7 and layer 4. There are some layer 4 specific metrics. The following list summarizes the metrics are the applicable for layer 4 usage.
+The following metrics are available for monitoring Application Gateway's TLS/TCP proxy. In addition to Layer 4-specific metrics, there are several common metrics with Layer 7 (HTTP/S). For details of each, visit the complete [metrics listing](#supported-metrics-for-microsoftnetworkapplicationgateways).
+
+**Metrics that also apply to L4 proxy**
 
 - Current Connections
 - New Connections per second
@@ -118,14 +120,16 @@ Application Gateway supports TLS/TCP proxy monitoring. With layer 4 proxy featur
 - Unhealthy host count
 - Client RTT
 - Backend Connect Time
-- Backend First Byte Response Time. `BackendHttpSetting` dimension includes both layer 7 and layer 4 backend settings.
-
-For more information, see previous descriptions and the [metrics table](#supported-metrics-for-microsoftnetworkapplicationgateways).
+- Backend First Byte Response Time (`BackendHttpSetting` dimension applies to both Layer 7 and 4 backend settings).
+- Bytes Sent
+- Bytes Received
+- Compute Units
+- Capacity Units
 
-These metrics apply to layer 4 only.
+**L4 proxy-specific metrics**
 
-- **Backend Session Duration**. The total time of a backend connection. The average time duration from the start of a new connection to its termination. `BackendHttpSetting` dimension includes both layer 7 and layer 4 backend settings.
-- **Connection Lifetime**. The total time of a client connection to application gateway. The average time duration from the start of a new connection to its termination in milliseconds.
+- Backend Session Duration - The total time of a backend connection. The average time duration from the start of a new connection to its termination. `BackendHttpSetting` dimension includes both layer 7 and layer 4 backend settings.
+- Connection Lifetime - The total time of a client connection to application gateway. The average time duration from the start of a new connection to its termination in milliseconds.
 
 ### TLS/TCP proxy backend health
 

articles/automation/extension-based-hybrid-runbook-worker-install.md

@@ -4,7 +4,7 @@ description: This article provides information about deploying the extension-bas
 services: automation
 ms.subservice: process-automation
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep, linux-related-content
-ms.date: 05/08/2025
+ms.date: 05/12/2025
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
 ms.service: azure-automation
@@ -123,7 +123,7 @@ If you use a proxy server for communication between Azure Automation and machine
 
    The API call will provide the value with the key: `AutomationHybridServiceUrl`. Use the URL in the next step to enable extension on the VM.
 
-1. Install the Hybrid Worker Extension on the VM by running the following PowerShell cmdlet (Required module: Az.Compute). Use the `properties.automationHybridServiceUrl` provided by the above API call  
+1. Install the Hybrid Worker Extension on the VM by running the following PowerShell cmdlet (Required module: Az.Compute). Use the `properties.automationHybridServiceUrl` provided by the above API call. Ensure ProxyServer URL does not contain any blank spaces. 
 
 # [Windows](#tab/windows)
 

articles/azure-resource-manager/templates/syntax.md

@@ -57,7 +57,7 @@ In the `definitions` section of the template, specify the schemas used for valid
 
 ```json
 "definitions": {
-  "<definition-name": {
+  "<definition-name>": {
     "type": "<data-type-of-definition>",
     "allowedValues": [ "<array-of-allowed-values>" ],
     "minValue": <minimum-value-for-int>,
@@ -287,8 +287,8 @@ You define resources with the following structure:
         "<settings-for-the-resource>",
         "copy": [
             {
-                "name": ,
-                "count": ,
+                "name": "<name-of-copy-loop>",
+                "count": <number-of-iterations>,
                 "input": {}
             }
         ]

articles/azure-resource-manager/templates/template-functions-deployment.md

@@ -52,7 +52,7 @@ The following example returns the deployer object.
   "outputs": {
     "developerOutput": {
       "type": "object",
-      "value": "[developer()]"
+      "value": "[deployer()]"
     }
   }
 }

articles/backup/archive-tier-support.md

@@ -2,7 +2,7 @@
 title: Azure Backup - Archive tier overview 
 description: Learn about Archive tier support for Azure Backup.
 ms.topic: overview
-ms.date: 05/07/2025
+ms.date: 05/13/2025
 ms.custom: references_regions
 ms.service: azure-backup
 author: jyothisuri
@@ -23,7 +23,7 @@ Archive tier supports the following workloads:
 
 | Workloads | Operations |
 | --- | --- |
-| Azure Virtual Machines | Only monthly and yearly recovery points. Daily and weekly recovery points aren't supported.  <br><br> Age >= 3 months in Vault-standard tier <br><br> Retention left >= 6 months. <br><br> No active daily and weekly dependencies. There are no un-expired daily or weekly recovery points between the recovery point considered for archival and the next monthly or yearly recovery point. |
+| Azure Virtual Machines | Only monthly and yearly recovery points. Daily and weekly recovery points aren't supported.  <br><br> Age >= 3 months in Vault-standard tier <br><br> Retention left >= 6 months. <br><br> No active on-demand, daily, and weekly dependencies. There are no un-expired daily or weekly recovery points between the recovery point considered for archival and the next monthly or yearly recovery point. |
 | SQL Server in Azure Virtual Machines <br><br> SAP HANA in Azure Virtual Machines | Only full recovery points. Logs and differentials aren't supported. <br><br> Age >= 45 days in Vault-standard tier. <br><br> Retention left >= 6 months. <br><br>  No dependencies. |
 
 A recovery point becomes archivable only if all the above conditions are met.

articles/backup/backup-azure-vm-backup-faq.yml

@@ -4,7 +4,7 @@ metadata:
   description: In this article, discover answers to common questions about backing up Azure VMs with the Azure Backup service.
   ms.topic: faq
   ms.service: azure-backup
-  ms.date: 03/27/2025
+  ms.date: 05/12/2025
   author: jyothisuri
   ms.author: jsuri
 
@@ -157,6 +157,12 @@ sections:
           - **Retention of monthly backup points**: 1188 months
           - **Retention of yearly backup points**: 99 years 
 
+      - question: Can I back up a VM disks that're created in the Azure Classic Storage?
+        answer: |
+          No, the support for disks created in Azure Classic Storage is no longer available. To ensure continued functionality, you must migrate these disks to Azure Resource Manager (ARM) Storage. Also, Classic Storage accounts can't support ARM-based Virtual Machines (VMs), and no workarounds exist to enable compatibility.
+
+          >[!Important]
+          >Support for backup of all Classic VMs is planned for deprecation on September 30, 2025. We recommend that you migrate the Classic VMs and associated disks to ARM Storage before this timeline to avoid disruptions.
   - name: Restore
     questions:
       - question: How do I decide whether to restore disks only or a full VM?
@@ -409,7 +415,7 @@ sections:
 
       - question: Why the expiry time for latest recovery points doesn't appear in the Azure portal for VMs?
         answer: |
-          The expiry time for the latest recovery point doesn't appear because it has infinite retention until a newer one gets created. The expiry time of other recovery points will be available in the Azure Portal after 24 hours of creation, depending on when the garbage collection runs (that will be within 24 hours).
+          The expiry time for the latest recovery point doesn't appear because it has infinite retention until a newer one gets created. The expiry time of other recovery points will be available in the Azure portal after 24 hours of creation, depending on when the garbage collection runs (that will be within 24 hours).
 
       - question: Will an Azure VM restore operation to original or alternate location affect a scheduled backup?
         answer: |
@@ -449,7 +455,7 @@ sections:
         answer: |
           This is the directory used by Backup Extension VMSnapshotLinux and it gets created when backups are enabled on VM using Recovery Services Vault. Logs are written in this location during backups, restores or extension operations such as schedule updates, generally they should use up only a few GB and the size of the logs is not proportional with the size of the backup. 
 
-      - question: If backup fails with time out error for large disk VMs after running sometime, when can I re-trigger the backup job again and will the backup continue from where it failed?
+      - question: If backup fails with a time-out error for large disk VMs after running sometime, when can I re-trigger the backup job again and will the backup continue from where it failed?
         answer: |
           For Initial Replica, a full backup will be re-initiated in case of failure. However, for Incremental the snapshot from the last successful backup will be compared to the latest snapshot to copy the changed data into the vault.