Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into us543898-nat-ip-v2-preview-remove

merge
.

Author: asudbring

articles/application-gateway/private-link.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: mbender-ms
 ms.service: azure-application-gateway
 ms.topic: concept-article
-ms.date: 06/06/2023
+ms.date: 01/21/2026
 ms.author: mbender
 
 # Customer intent: "As a network administrator, I want to implement Private Link for Application Gateway, so that I can securely connect my workloads over a private network while maintaining the benefits of Layer 7 load balancing."
@@ -53,6 +53,16 @@ Four components are required to implement Private Link with Application Gateway:
 
    A connection on Application Gateway originated by Private Endpoints. You can autoapprove, manually approve, or reject connections to grant or deny access.
 
+## Pricing
+
+| Component | Service Provider/Private Link (Application Gateway resource owner)  | Consumer/Private Endpoint | 
+| ---------- | ---------- | ---------- |
+| **Private link service** | No charges | Not applicable | 
+| **Private endpoint** | Not applicable | [Billed as per Private Link](https://azure.microsoft.com/pricing/details/private-link/#pricing) | 
+| **Data processing (Bi-directional)** | No charges | [Billed as per Private Link](https://azure.microsoft.com/pricing/details/private-link/#pricing) | 
+| **Data transfers** | [Billed as per Bandwidth](https://azure.microsoft.com/pricing/details/bandwidth/#pricing) | [Billed as per Bandwidth](https://azure.microsoft.com/pricing/details/bandwidth/#pricing) | 
+
+
 ## Limitations
 - API version 2020-03-01 or later should be used to configure Private Link configurations.
 - Static IP allocation method in the Private Link Configuration object isn't supported.

articles/network-watcher/frequently-asked-questions.yml

@@ -389,7 +389,12 @@ sections:
         answer: |
           Traffic analytics is metered. The metering is based on processing of raw flow log data by the service. For more information, see [Network Watcher pricing](https://azure.microsoft.com/pricing/details/network-watcher/).          
           Enhanced logs ingested in Log Analytics workspace can be retained at no charge for up to first 31 days (or 90 days if Microsoft Sentinel is enabled on the workspace). For more information, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/).
-          
+
+      - question: |
+          Why do I see additional storage transactions when NSG flow logs and Traffic Analytics are enabled?
+        answer: |
+          When NSG flow logs are enabled, flow log records are written to the configured Azure Storage account. To generate Traffic Analytics insights, Azure Network Watcher performs backend read operations on this stored data to process, aggregate, and enrich flow log records. These backend storage interactions are required for analytics functionality and occur even if you do not actively query the data. You can control the overall cost impact by adjusting flow log scope, retention, and whether Traffic Analytics is enabled.
+      
       - question: |
           How frequently does traffic analytics process data?
         answer: |