Merge pull request #310634 from MicrosoftDocs/main

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

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

articles/azure-vmware/toc.yml

@@ -390,7 +390,7 @@ items:
     href: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/resources/vmware_private_cloud
   - name: Configure VMware Cloud Director Service in Azure VMware Solution
     href: configure-vmware-cloud-director-service-azure-vmware-solution.md
-  - name: Plan self-service maintenance for Azure VMware Solution (public preview)
+  - name: Plan self-service maintenance for Azure VMware Solution
     href: self-service-maintenance-orchestration.md
   - name: Enable VMware Cloud Director Service with Azure VMware Solution
     href: enable-vmware-cds-with-azure.md

articles/network-watcher/vnet-flow-logs-overview.md

@@ -251,6 +251,8 @@ Currently, these Azure services don't support virtual network flow logs:
 - If traffic analytics is enabled with virtual network flow logs, traffic analytics pricing applies at per gigabyte processing rates. Traffic analytics isn't offered with a free tier of pricing. For more information, see [Network Watcher pricing](https://azure.microsoft.com/pricing/details/network-watcher/).
 
 - Storage of logs is charged separately. For more information, see [Azure Blob Storage pricing](https://azure.microsoft.com/pricing/details/storage/blobs/).
+  
+- Virtual Network Flow Logs extend logging coverage beyond network security boundaries to include platform and application‑level traffic scenarios. This broader scope supports additional use cases and traffic patterns, which may result in higher log volumes compared to more narrowly scoped flow logging configurations.
 
 ## Supported scenarios