Update data-retention-archive.md

1. Changed the title a bit to “Data retention and archive in Azure Monitor Logs”
2. Removed the word “policies” that has a specific meaning in Azure
3. Rewrote the intro paragraph to indicate coming 12 years archive

Author: MeirMen

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

@@ -1,25 +1,23 @@
 ---
-title: Configure data retention and archive in Azure Monitor Logs
+title: Data retention and archive in Azure Monitor Logs
 description: Configure archive settings for a table in a Log Analytics workspace in Azure Monitor.
 ms.reviewer: adi.biran
 ms.topic: conceptual
 ms.date: 6/28/2023
 # Customer intent: As an Azure account administrator, I want to set data retention and archive policies to save retention costs.
 ---
 
-# Configure data retention and archive policies in Azure Monitor Logs
+# Data retention and archive in Azure Monitor Logs
 
-Retention policies define when to remove or archive data in a [Log Analytics workspace](log-analytics-workspace-overview.md). Archiving lets you keep older, less used data in your workspace at a reduced cost.
+Data is retained in Azure Monitor Logs in two modes:
+* **Interactive Retention**: Allow you to retain Analytics logs for [interactive queries](../logs/get-started-queries.md) of up to 2 years.
+* **Archive**: Let you keep older, less used data in your workspace at a reduced cost. Data in archive can be accessed by [Search Jobs](../logs/search-jobs.md) and [Restore](../logs/restore.md). You can keep in Archive logs up to 7 years. In the coming months, it would be possible to extend archive to 12 years.
 
 This article describes how to configure data retention and archiving.
 
-## Permissions
-
-To configure set data retention and archiving, you must have at least [contributor rights](../logs/manage-access.md#azure-rbac).
-
 ## How retention and archiving work
 
-Each workspace has a default retention policy that's applied to all tables. You can set a different retention policy on individual tables.
+Each workspace has a default retention that's applied to all tables. You can set a different retention setting on individual tables.
 
 :::image type="content" source="media/data-retention-configure/retention-archive.png" alt-text="Diagram that shows an overview of data retention and archive periods.":::
 
@@ -32,19 +30,23 @@ You can access archived data by [running a search job](search-jobs.md) or [resto
 > [!NOTE]
 > The archive period can only be set at the table level, not at the workspace level.
 
+## Permissions
+
+To configure set data retention and archiving, you must have at least [contributor rights](../logs/manage-access.md#azure-rbac).
+
 ### Adjustments to retention and archive settings
 
-When you shorten an existing retention policy, Azure Monitor waits 30 days before removing the data, so you can revert the change and prevent data loss in the event of an error in configuration. You can [purge data](#purge-retained-data) immediately when required. 
+When you shorten an existing retention setting, Azure Monitor waits 30 days before removing the data, so you can revert the change and prevent data loss in the event of an error in configuration. You can [purge data](#purge-retained-data) immediately when required. 
 
-When you increase the retention policy, the new retention period applies to all data that's already been ingested into the table and hasn't yet been purged or removed.   
+When you increase the retention setting, the new retention period applies to all data that's already been ingested into the table and hasn't yet been purged or removed.   
 
-If you change the archive settings on a table with existing data, the relevant data in the table is also affected immediately. For example, you might have an existing table with 180 days of interactive retention and no archive period. You decide to change the retention policy to 90 days of interactive retention without changing the total retention period of 180 days. Log Analytics immediately archives any data that's older than 90 days and none of the data is deleted.
+If you change the archive settings on a table with existing data, the relevant data in the table is also affected immediately. For example, you might have an existing table with 180 days of interactive retention and no archive period. You decide to change the retention setting to 90 days of interactive retention without changing the total retention period of 180 days. Log Analytics immediately archives any data that's older than 90 days and none of the data is deleted.
 
-## Configure the default workspace retention policy
+## Configure the default workspace retention
 
-You can set the workspace default retention policy in the Azure portal to 30, 31, 60, 90, 120, 180, 270, 365, 550, and 730 days. You can set a different policy for specific tables by [configuring the retention and archive policy at the table level](#set-retention-and-archive-policy-by-table). If you're on the *free* tier, you'll need to upgrade to the paid tier to change the data retention period.
+You can set the workspace default retention in the Azure portal to 30, 31, 60, 90, 120, 180, 270, 365, 550, and 730 days. You can set a different for specific tables by [configuring the retention and archive policy at the table level](#set-retention-and-archive-policy-by-table). If you're on the *free* tier, you'll need to upgrade to the paid tier to change the data retention period.
 
-To set the default workspace retention policy:
+To set the default workspace retention:
 
 1. From the **Log Analytics workspaces** menu in the Azure portal, select your workspace.
 1. Select **Usage and estimated costs** in the left pane.
@@ -54,9 +56,9 @@ To set the default workspace retention policy:
 
 1. Move the slider to increase or decrease the number of days, and then select **OK**.
 
-## Set retention and archive policy by table
+## Set retention and archive by table
 
-By default, all tables in your workspace inherit the workspace's interactive retention setting and have no archive policy. You can modify the retention and archive policies of individual tables, except for workspaces in the legacy Free Trial pricing tier.
+By default, all tables in your workspace inherit the workspace's interactive retention setting and have no archive. You can modify the retention and archive settings of individual tables, except for workspaces in the legacy Free Trial pricing tier.
 
 The Analytics log data plan includes 30 days of interactive retention. You can increase the interactive retention period to up to 730 days at an [additional cost](https://azure.microsoft.com/pricing/details/monitor/). If needed, you can reduce the interactive retention period to as low as four days using the API or CLI, however, since 30 days are included in the ingestion price, lowering the retention period below 30 days does not reduce costs. You can set the archive period to a total retention time of up to 2,556 days (seven years).
 
@@ -101,6 +103,10 @@ The request body includes the values in the following table.
 |properties.retentionInDays | integer  | The table's data retention in days. This value can be between 4 and 730. <br/>Setting this property to null will default to the workspace retention. For a Basic Logs table, the value is always 8. |
 |properties.totalRetentionInDays | integer  | The table's total data retention including archive period. This value can be between 4 and 730; or 1095, 1460, 1826, 2191, or 2556. Set this property to null if you don't want to archive data.  |
 
+> [!NOTE]
+> In the coming months, additional settings will be available to allow retention of up to 12 years.
+
+
 **Example**
 
 This example sets the table's interactive retention to the workspace default of 30 days, and the total retention to two years, which means that the archive duration is 23 months.
@@ -174,7 +180,7 @@ Update-AzOperationalInsightsTable -ResourceGroupName ContosoRG -WorkspaceName Co
 
 ---
 
-## Get retention and archive policy by table
+## Get retention and archive settings by table
 
 # [Portal](#tab/portal-2)
 
@@ -187,13 +193,13 @@ The **Tables** screen shows the interactive retention and archive period for all
 
 # [API](#tab/api-2)
 
-To get the retention policy of a particular table (in this example, `SecurityEvent`), call the **Tables - Get** API:
+To get the retention setting of a particular table (in this example, `SecurityEvent`), call the **Tables - Get** API:
 
 ```JSON
 GET /subscriptions/00000000-0000-0000-0000-00000000000/resourceGroups/MyResourceGroupName/providers/Microsoft.OperationalInsights/workspaces/MyWorkspaceName/Tables/SecurityEvent?api-version=2021-12-01-preview
 ```
 
-To get all table-level retention policies in your workspace, don't set a table name. 
+To get all table-level retention settings in your workspace, don't set a table name. 
 
 For example:
 
@@ -203,7 +209,7 @@ GET /subscriptions/00000000-0000-0000-0000-00000000000/resourceGroups/MyResource
 
 # [CLI](#tab/cli-2)
 
-To get the retention policy of a particular table, run the [az monitor log-analytics workspace table show](/cli/azure/monitor/log-analytics/workspace/table#az-monitor-log-analytics-workspace-table-show) command.
+To get the retention setting of a particular table, run the [az monitor log-analytics workspace table show](/cli/azure/monitor/log-analytics/workspace/table#az-monitor-log-analytics-workspace-table-show) command.
 
 For example:
 
@@ -213,7 +219,7 @@ az monitor log-analytics workspace table show --subscription ContosoSID --resour
 
 # [PowerShell](#tab/PowerShell-2)
 
-To get the retention policy of a particular table, run the [Get-AzOperationalInsightsTable](/powershell/module/az.operationalinsights/get-azoperationalinsightstable) cmdlet.
+To get the retention setting of a particular table, run the [Get-AzOperationalInsightsTable](/powershell/module/az.operationalinsights/get-azoperationalinsightstable) cmdlet.
 
 For example:
 
@@ -225,19 +231,19 @@ Get-AzOperationalInsightsTable -ResourceGroupName ContosoRG -WorkspaceName Conto
 
 ## Purge retained data
 
-If you set the data retention policy to 30 days, you can purge older data immediately by using the `immediatePurgeDataOn30Days` parameter in Azure Resource Manager. The purge functionality is useful when you need to remove personal data immediately. The immediate purge functionality isn't available through the Azure portal.
+If you set the data retention to 30 days, you can purge older data immediately by using the `immediatePurgeDataOn30Days` parameter in Azure Resource Manager. The purge functionality is useful when you need to remove personal data immediately. The immediate purge functionality isn't available through the Azure portal.
 
-Workspaces with a 30-day retention policy might keep data for 31 days if you don't set the `immediatePurgeDataOn30Days` parameter.
+Workspaces with a 30-day retention might keep data for 31 days if you don't set the `immediatePurgeDataOn30Days` parameter.
 
 You can also purge data from a workspace by using the [purge feature](personal-data-mgmt.md#exporting-and-deleting-personal-data), which removes personal data. You can't purge data from archived logs.
 
 The Log Analytics [Purge API](/rest/api/loganalytics/workspacepurge/purge) doesn't affect retention billing. To lower retention costs, *decrease the retention period for the workspace or for specific tables*.
 
-## Tables with unique retention policies
+## Tables with unique retention periods
 
 By default, two data types, `Usage` and `AzureActivity`, keep data for at least 90 days at no charge. When you increase the workspace retention to more than 90 days, you also increase the retention of these data types. These tables are also free from data ingestion charges.
 
-Tables related to Application Insights resources also keep data for 90 days at no charge. You can adjust the retention policy of each of these tables individually:
+Tables related to Application Insights resources also keep data for 90 days at no charge. You can adjust the retention of each of these tables individually:
 
 - `AppAvailabilityResults`
 - `AppBrowserTimings`