Merge branch 'dcr' of https://github.com/bwren/azure-docs-pr into dcr

Author: bwren

articles/azure-monitor/logs/basic-logs-configure.md

@@ -99,11 +99,11 @@ To check the configuration of a table in the Azure portal:
 
     Basic Logs tables have a unique icon: 
 
-    ![Screenshot of the Basic Logs table icon in the table list.](./media/basic-logs-configure/table-icon.png)
+    ![Screenshot of the Basic Logs table icon in the table list.](./media/basic-logs-configure/table-icon.png#lightbox)
 
     You can also hover over a table name for the table information view. This will specify that the table is configured as Basic Logs:
 
-    ![Screenshot of the Basic Logs table indicator in the table details.](./media/basic-logs-configure/table-info.png)
+    ![Screenshot of the Basic Logs table indicator in the table details.](./media/basic-logs-configure/table-info.png#lightbox)
 
 # [API](#tab/api-2)
 

articles/azure-monitor/logs/data-retention-archive.md

@@ -153,7 +153,7 @@ Tables related to Application Insights resources also keep data for 90 days at n
 - `AppSystemEvents`
 - `AppTraces`
 
-## Pricing
+## Pricing model
 
 You'll be charged for each day you retain data. The cost of retaining data for part of a day is the same as for a full day.
 

articles/azure-monitor/logs/log-analytics-workspace-overview.md

@@ -34,7 +34,7 @@ By default, all tables in a workspace are **Analytics** tables, which are availa
 The following table gives a brief summary of the two plans. See [Configure Basic Logs in Azure Monitor (Preview)](basic-logs-configure.md) for more details on Basic Logs and how to configure them.
 
 > [!NOTE]
-> Basic Logs are currently in public preview.
+> Basic Logs are currently in public preview. You can currently work with Basic Logs tables in the Azure Portal and using a limited number of other components.
 
 The following table summarizes the differences between the plans.
 
@@ -44,8 +44,6 @@ The following table summarizes the differences between the plans.
 | Log queries | No additional cost. Full query language. | Additional cost. Subset of query language. |
 | Retention |  Configure retention from 30 days to 750 days. | Retention fixed at 8 days. |
 | Alerts | Supported. | Not supported. |
-| Integration into automated workflows | Supported. | Not supported. |
-| Data visualization | Supported. | Not supported. |
 
 ## Ingestion-time transformations
 [Data collection rules (DCRs)](../essentials/data-collection-rule-overview.md) that define data coming into Azure Monitor can include transformations that allow you to filter and transform data before it's ingested into the workspace. Since all workflows don't yet support DCRs, each workspace can define ingestion-time transformations. This allows you filter or transform data before it's stored. 

articles/azure-monitor/logs/restore.md

@@ -25,7 +25,7 @@ The restore operation creates the restore table and allocates additional compute
 The destination table provides a view of the underlying source data, but does not affect it in any way. The table has no retention setting, and you must explicitly [dismiss the restored data](#dismiss-restored-data) when you no longer need it. 
 
 ## Restore data using API
-Call the **Tables - Create or Update** API to restore data from a table:
+To restore data from a table, call the **Tables - Create or Update** API. The name of the destination table must end with *_RST*.
 
 ```http
 PUT https://management.azure.com/subscriptions/{subscriptionId}/resourcegroups/{resourceGroupName}/providers/Microsoft.OperationalInsights/workspaces/{workspaceName}/tables/{user defined name}_RST?api-version=2021-12-01-preview
@@ -95,7 +95,7 @@ You can:
 - Run up to two restore processes in a workspace concurrently.
 - Run only one active restore on a specific table at a given time. Executing a second restore on a table that already has an active restore will fail. 
 
-## Pricing
+## Pricing model
 The charge for the restore operation is based on the volume of data you restore and the number of days the data is available. The cost of retaining data for part of a day is the same as for a full day.
 
 For example, if your table holds 500 GB a day and you restore 10 days of data, you'll be charged for 5000 GB a day until you dismiss the restored data. 

articles/azure-monitor/logs/search-jobs.md

@@ -181,7 +181,7 @@ Log queries in a search job are intended to scan very large sets of data. To sup
 
 You can use all functions and binary operators within these operators.
 
-## Pricing
+## Pricing model
 The charge for a search job is based on: 
 
 - The amount of data the search job needs to scan.