Merge pull request #310256 from MicrosoftDocs/main

Auto Publish – main to live - 2026-01-08 12:00 UTC

Author: learn-build-service-prod[bot]

articles/application-gateway/application-gateway-diagnostics.md

@@ -60,9 +60,9 @@ Resource-specific mode provides:
 
 For Application Gateway, resource-specific mode creates the following tables: 
 
-- [AGWAccessLogs](/azure/azure-monitor/reference/tables/agwaccesslogs.md)
-- [AGWPerformanceLogs](/azure/azure-monitor/reference/tables/agwperformancelogs.md)
-- [AGWFirewallLogs](/azure/azure-monitor/reference/tables/agwfirewalllogs.md)
+- [AGWAccessLogs](/azure/azure-monitor/reference/tables/agwaccesslogs#columns)
+- [AGWPerformanceLogs](/azure/azure-monitor/reference/tables/agwperformancelogs#columns)
+- [AGWFirewallLogs](/azure/azure-monitor/reference/tables/agwfirewalllogs#columns)
 
 **Selecting the collection type in Log analytics**
 
@@ -157,4 +157,4 @@ You can also connect to your storage account and retrieve the JSON log entries f
 
 - Visualize counter and event logs by using [Azure Monitor logs](/previous-versions/azure/azure-monitor/insights/azure-networking-analytics).
 - [Visualize your Azure activity log with Power BI](https://powerbi.microsoft.com/blog/monitor-azure-audit-logs-with-power-bi/) blog post.
-- [View and analyze Azure activity logs in Power BI and more](https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/) blog post.
+- [View and analyze Azure activity logs in Power BI and more](https://azure.microsoft.com/blog/analyze-azure-audit-logs-in-powerbi-more/) blog post.

articles/application-gateway/how-application-gateway-works.md

@@ -36,8 +36,7 @@ If a request is valid and not blocked by WAF, the application gateway evaluates
 
 Based on the request routing rule, the application gateway determines whether to route all requests on the listener to a specific backend pool, route requests to different backend pools based on the URL path, or redirect requests to another port or external site.
 > [!NOTE]
-> Rules are processed in the order they're listed in the portal for v1 SKU. 
-
+> Rules are processed in the order they're listed in the portal for v1 SKU.
 When the application gateway selects the backend pool, it sends the request to one of the healthy backend servers in the pool (y.y.y.y). The health of the server is determined by a health probe. If the backend pool contains multiple servers, the application gateway uses a round-robin algorithm to route the requests between healthy servers. This load balances the requests on the servers.
 
 After the application gateway determines the backend server, it opens a new TCP session with the backend server based on HTTP settings. HTTP settings specify the protocol, port, and other routing-related settings that are required to establish a new session with the backend server.
@@ -46,6 +45,9 @@ The port and protocol used in HTTP settings determine whether the traffic betwee
 
 When an application gateway sends the original request to the backend server, it honors any custom configuration made in the HTTP settings related to overriding the hostname, path, and protocol. This action maintains cookie-based session affinity, connection draining, host-name selection from the backend, and so on.
 
+> [!NOTE]
+> Application Gateway does not forward the request to WAF when no backend pool members are available
+
  > [!NOTE]
 > If the backend pool:
 > - **Is a public endpoint**, the application gateway uses its frontend public IP to reach the server. If there isn't a frontend public IP address, one is assigned for the outbound external connectivity.

articles/azure-netapp-files/azure-netapp-files-metrics.md

@@ -268,6 +268,13 @@ Azure NetApp Files provides metrics on allocated storage, actual storage usage,
 
     :::image type="content" source="./media/azure-netapp-files-metrics/throughput-limit-reached.png" alt-text="Screenshot that shows Azure NetApp Files metrics a line graph demonstrating throughput limit reached." lightbox="./media/azure-netapp-files-metrics/throughput-limit-reached.png":::
 
+- *QoS Latency Delta*
+    
+    QoS Latency Delta represents the total QoS latency for a volume over a time period (measured in ms).
+    
+    :::image type="content" source="./media/azure-netapp-files-metrics/quality-of-service-latency-delta.png" alt-text="Screenshot that shows Azure NetApp Files metrics displaying the total latency for the exceeded throughput." lightbox="./media/azure-netapp-files-metrics/quality-of-service-latency-delta.png":::
+
+
 ## Performance metrics for volumes
 
 > [!NOTE] 

articles/azure-netapp-files/media/azure-netapp-files-metrics/quality-of-service-latency-delta.png

@@ -2,7 +2,7 @@
 title: About Azure VM backup
 description: In this article, learn how the Azure Backup service backs up Azure Virtual machines, and how to follow best practices.
 ms.topic: overview
-ms.date: 07/25/2025
+ms.date: 01/08/2026
 author: AbhishekMallick-MS
 ms.author: v-mallicka
 # Customer intent: "As an IT admin managing Azure VMs, I want to implement effective backup strategies using Azure Backup, so that I can ensure data protection and quick recovery for my virtual machines while minimizing downtime and costs."
@@ -55,6 +55,14 @@ If you have opted for application or file-system-consistent backups, the VM need
   - If the pre-scripts and post-scripts execute successfully, Azure Backup marks the recovery point as application-consistent. However, when you're using custom scripts, you're ultimately responsible for the application consistency.
   - [Learn more](backup-azure-linux-app-consistent.md) about how to configure scripts.
 
+- **FSFreeze and safeFreezelockFile**: **Fsfreeze** is a utility used to freeze and thaw the *filesystem* to make their state on consistent during VM backups.
+
+  - **Freeze**: When you freeze a filesystem, the currently running operations are allowed to complete. However, new write system operations and the operations that modify the filesystem are stopped.
+
+  - **Thawing**:  This operation reverses the freeze operation. When you thaw a filesystem, the previously stopped operations continue to run effectively, unblocking any modifications.
+
+  During the *Freeze* operation, Azure Backup invokes a file safeFreezelockFile. This prevents the other process to invoke the similar operation so that backup process isn't interrupted. Once the operation is complete, the lock is released.
+
 >[!Note]
 >The snapshot process starts with invoking the backup extension (agent-based), using tools such as VSS for Windows or freeze for Linux to ensure data consistency. When consistent, the Restore Point Collection monitors the extension and initiates snapshot creation. Afterward, metadata is updated with restore point paths and commit details to finalize the backup for restoration.
 

articles/backup/backup-azure-vms-introduction.md

@@ -2,7 +2,7 @@
 title: Azure Backup support matrix
 description: Provides a summary of support settings and limitations for the Azure Backup service.
 ms.topic: reference
-ms.date: 12/12/2025
+ms.date: 01/08/2025
 ms.custom: references_regions, linux-related-content
 ms.service: azure-backup
 author: AbhishekMallick-MS
@@ -32,7 +32,7 @@ The following table describes the features of Recovery Services vaults:
 
 **Feature** | **Details**
 --- | ---
-**Vaults in subscription** | Up to 500 Recovery Services vaults or Backup vaults in a single subscription.
+**Vaults in subscription** | Up to 500 Recovery Services vaults or Backup vaults in a single subscription.<br><br>Up to 5000 Backup Policies for each Data Source under Recovery Services Vault or Backup Vault.
 **Machines in a vault** | Up to 2000 datasources across all workloads (like Azure VMs, SQL Server VM, MABS Servers, and so on) can be protected in a single vault.<br><br>Up to 1,000 Azure VMs in a single vault, but due to security constraints only 250 VM registrations are allowed per day.<br/><br/> Up to 50 MABS servers can be registered in a single vault.<br><br>Up to 100 VM’s can be protected in a single policy.
 **Data sources** | Maximum size of an individual [data source](./backup-azure-backup-faq.yml#how-is-the-data-source-size-determined-) is 54,400 GB. This limit doesn't apply to Azure VM backups. No limits apply to the total amount of data you can back up to the vault.
 **Backups to vault** | **Azure VMs:** Once a day.<br/><br/>**Machines protected by DPM/MABS:** Twice a day.<br/><br/> **Machines backed up directly by using the MARS agent:** Three times a day.

articles/backup/backup-support-matrix.md

@@ -72,7 +72,7 @@ To send SMS, you must have a sender ID—this can be a phone number or an alphan
 | Canada           | ✅        | ✅         | –     | –              | –              | –              |
 | Puerto Rico      | ✅        | –          | –     | –              | –              | –              |
 | United Kingdom   | –         | ✅         | –     | ✅             | –             | ✅             |
-| Australia        | –         | –          | –     | ✅             | –              | ✅             |
+| Australia        | –         | –          | –     | ✅             | –              | -             |
 | Austria          | –         | –          | –     | –              | ✅              |–              |
 | Germany          | –         | –          | –     | –              | ✅             | –              |
 | France           | –         | –          | –     | –              | ✅             | –              |