Remove data export line and remove extra includes

Author: bwren

articles/azure-monitor/best-practices-cost.md

@@ -1,5 +1,5 @@
 ---
-title: Optimize costs in Azure Monitor
+title: Cost optimization in Azure Monitor
 description: Recommendations for reducing costs in Azure Monitor.
 ms.topic: conceptual
 author: bwren
@@ -8,7 +8,7 @@ ms.date: 03/29/2023
 ms.reviewer: bwren
 ---
 
-# Optimize costs in Azure Monitor
+# Cost optimization in Azure Monitor
 You can significantly reduce your cost for Azure Monitor by understanding your different configuration options and opportunities to reduce the amount of data that it collects. Before you use this article, you should see [Azure Monitor cost and usage](usage-estimated-costs.md) to understand the different ways that Azure Monitor charges and how to view your monthly bill.
 
 > [!NOTE]
@@ -62,7 +62,7 @@ You may be able to significantly reduce your costs by optimizing the configurati
 
 | Recommendation | Description |
 |:---|:---|
-| Configure pricing tier or dedicated cluster for your Log Analytics workspaces. | By default, Log Analytics workspaces will use pay-as-you-go pricing with no minimum data volume. If you collect enough data, you can significantly decrease your cost by using a [commitment tier](logs/cost-logs.md#commitment-tiers) or [dedicated cluster](logs/logs-dedicated-clusters.md), which allows you to commit to a daily minimum of data collected in exchange for a lower rate.<br><br>See [Azure Monitor Logs cost calculations and options](logs/cost-logs.md) for details on commitment tiers and guidance on determining which is most appropriate for your level of usage. See [Usage and estimated costs](../usage-estimated-costs.md#usage-and-estimated-costs) to view estimated costs for your usage at different pricing tiers.
+| Configure pricing tier or dedicated cluster for your Log Analytics workspaces. | By default, Log Analytics workspaces will use pay-as-you-go pricing with no minimum data volume. If you collect enough data, you can significantly decrease your cost by using a [commitment tier](logs/cost-logs.md#commitment-tiers) or [dedicated cluster](logs/logs-dedicated-clusters.md), which allows you to commit to a daily minimum of data collected in exchange for a lower rate.<br><br>See [Azure Monitor Logs cost calculations and options](logs/cost-logs.md) for details on commitment tiers and guidance on determining which is most appropriate for your level of usage. See [Usage and estimated costs](usage-estimated-costs.md#usage-and-estimated-costs) to view estimated costs for your usage at different pricing tiers.
 | Configure tables used for debugging, troubleshooting, and auditing as Basic Logs. | Tables in a Log Analytics workspace configured for [Basic Logs](logs/basic-logs-configure.md) have a lower ingestion cost in exchange for limited features and a charge for log queries. If you query these tables infrequently, this query cost can be more than offset by the reduced ingestion cost. |
 | Configure data retention and archiving. | There is a charge for retaining data in a Log Analytics workspace beyond the default of 30 days (90 days in Sentinel if enabled on the workspace). If you need to retain data for compliance reasons or for occasional investigation or analysis of historical data, configure [Archived Logs](logs/data-retention-archive.md), which allows you to retain data for up to seven years at a reduced cost. |
 | Regularly analyze collected data to identify trends and anomalies.  | Use [Log Analytics workspace insights](logs/log-analytics-workspace-insights-overview.md) to periodically review the amount of data collected in your workspace. In addition to helping you understand the amount of data collected by different sources, it will identify anomalies and upward trends in data collection that could result in excess cost. Further analyze data collection using methods in [Analyze usage in Log Analytics workspace](logs/analyze-usage.md) to determine if there's additional configuration that can decrease your usage further. This is particularly important when you add a new set of data sources, such as a new set of virtual machines or onboard a new service. |

articles/azure-monitor/waf/waf-workspace.md renamed to articles/azure-monitor/best-practices-logs.md

@@ -1,5 +1,5 @@
 ---
-title: Azure Well-Architected Framework review for Log Analytics workspaces in Azure Monitor
+title: Best practices for Azure Monitor Logs
 description: Provides a template for a Well-Architected Framework (WAF) article specific to Log Analytics workspaces in Azure Monitor.
 ms.topic: conceptual
 author: bwren
@@ -8,26 +8,28 @@ ms.date: 03/29/2023
 ms.reviewer: bwren
 ---
 
-# Azure Well-Architected Framework - Azure Monitor - Log Analytics workspaces
-This article provides architectural best practices for Logs Analytics workspaces in Azure Monitor. The guidance is based on the five pillars of architecture excellence described in [Azure Well-Architected Framework](/azure/architecture/framework/):
+# Best practices for Azure Monitor Logs
+This article provides architectural best practices for Azure Monitor Logs. The guidance is based on the five pillars of architecture excellence described in [Azure Well-Architected Framework](/azure/architecture/framework/):
 
-- [Reliability](#reliability)
-- [Security](#security)
-- [Cost optimization](#cost-optimization)
-- [Operational excellence](#operational-excellence)
-- [Performance efficiency](#performance-efficiency)
+- [Best practices for Azure Monitor Logs](#best-practices-for-azure-monitor-logs)
+  - [Reliability](#reliability)
+  - [Security](#security)
+  - [Cost optimization](#cost-optimization)
+  - [Operational excellence](#operational-excellence)
+  - [Performance efficiency](#performance-efficiency)
+  - [Next step](#next-step)
 
 
 ## Reliability
 In the cloud, we acknowledge that failures happen. Instead of trying to prevent failures altogether, the goal is to minimize the effects of a single failing component. Use the following information to minimize failure of your Log Analytics workspaces and to protect the data they collect.
 
-[!INCLUDE [waf-workspace-reliability](../includes/waf-workspace-reliability.md)]
+[!INCLUDE [wag-logs-reliability](includes/wag-logs-reliability.md)]
 
 
 ## Security
 Security is one of the most important aspects of any architecture. Azure Monitor provides features to employ both the principle of least privilege and defense-in-depth. Use the following information to maximize the security of your Log Analytics workspaces and ensure that only authorized users access collected data.
 
-[!INCLUDE [waf-workspace-security](../includes/waf-workspace-security.md)]
+[!INCLUDE [wag-logs-security](includes/wag-logs-security.md)]
 
 
 ## Cost optimization
@@ -36,19 +38,19 @@ Cost optimization refers to ways to reduce unnecessary expenses and improve oper
 > [!NOTE]
 > See [Optimize costs in Azure Monitor](../best-practices-cost.md) for cost optimization recommendations across all features of Azure Monitor.
 
-[!INCLUDE [waf-workspace-cost](../includes/waf-workspace-cost.md)]
+[!INCLUDE [wag-logs-cost](includes/wag-logs-cost.md)]
 
 
 ## Operational excellence
 Operational excellence refers to operations processes required keep a service running reliably in production. Use the following information to minimize the operational requirements for supporting Log Analytics workspaces.
 
-[!INCLUDE [waf-workspace-operation](../includes/waf-workspace-operation.md)]
+[!INCLUDE [wag-logs-operation](includes/wag-logs-operation.md)]
 
 
 ## Performance efficiency
 Performance efficiency is the ability of your workload to scale to meet the demands placed on it by users in an efficient manner. Use the following information to ensure that your Log Analytics workspaces and log queries are configured for maximum performance.
 
-[!INCLUDE [waf-workspace-performance](../includes/waf-workspace-performance.md)]
+[!INCLUDE [wag-logs-performance](includes/wag-logs-performance.md)]
 
 ## Next step