Merge pull request #819 from MicrosoftDocs/main

12/17/2024 PM Publish

articles/azure-monitor/logs/cost-logs.md

@@ -107,10 +107,12 @@ For more information on how to create a dedicated cluster and specify its billin
 
 ## Basic and Auxiliary table plans
 
-You can configure certain tables in a Log Analytics workspace to use [Basic and Auxiliary table plans](logs-table-plans.md). Data in these tables has a significantly reduced ingestion charge. There's a charge to query data in these tables.
+You can configure certain tables in a Log Analytics workspace to use [Basic and Auxiliary table plans](logs-table-plans.md). Data in these tables has a significantly reduced ingestion charge. There's a charge to interactively query data in these tables (unlike tables which are in the Analytics table plan).
 
 The charge for querying data in Basic and Auxiliary tables is based on the GB of data scanned in performing the search.
 
+Charges for other features such as [long-term data retention](#log-data-retention) and [search jobs](#search-jobs) are the same for all table plans (Analytics, Basic and Auxiliary).  
+
 For more information about the Basic and Auxiliary table plans, see [Azure Monitor Logs overview: Table plans](data-platform-logs.md#table-plans).
 
 ## Log data retention

articles/azure-monitor/logs/private-link-configure.md

@@ -76,6 +76,8 @@ Once resources are connected to your AMPLS, you can create a private endpoint to
 
     > [!NOTE]
     > If you select **No** and prefer to manage DNS records manually, first finish setting up your private link. Include this private endpoint and the AMPLS configuration then configure your DNS according to the instructions in [Azure private endpoint DNS configuration](/azure/private-link/private-endpoint-dns). Make sure not to create empty records as preparation for your private link setup. The DNS records you create can override existing settings and affect your connectivity with Azure Monitor.
+    >
+    > Whether you select **Yes** or **No** and you're using your own custom DNS servers, you need to set up conditional forwarders for the Public DNS zone forwarders mentioned in [Azure private endpoint DNS configuration](/azure/private-link/private-endpoint-dns). The conditional forwarders need to forward the DNS queries to [Azure DNS](/azure/virtual-network/what-is-ip-address-168-63-129-16).
 
     :::image type="content" source="./media/private-link-security/create-private-endpoint-dns.png" alt-text="Screenshot that shows the Create a private endpoint page in the Azure portal with the DNS tab selected." lightbox="./media/private-link-security/create-private-endpoint-dns.png":::
 

articles/chaos-studio/chaos-studio-fault-library.md

@@ -274,6 +274,7 @@ The parameters **destinationFilters** and **inboundDestinationFilters** use the
 
 * The agent-based network faults currently only support IPv4 addresses.
 * This fault currently only affects new connections. Existing active connections are unaffected. You can restart the service or process to force connections to break.
+* This fault only affects **outbound** traffic at this time.
 
 ### Network Latency