Merge pull request #812 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 12/17

articles/azure-monitor/agents/azure-monitor-agent-migration.md

@@ -21,7 +21,7 @@ Migration is a complex task. Start planning your migration to Azure Monitor Agen
 > The Log Analytics agent was [retired on **August 31, 2024**](https://azure.microsoft.com/updates/were-retiring-the-log-analytics-agent-in-azure-monitor-on-31-august-2024/). This deprecation does not apply to MMA agent connected exclusively to an on-premises SCOM installation.
 > 
 > You can expect the following when you use the MMA or OMS agent after August 31, 2024.
-> - **Data upload:** Cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time.  Ingestion for MMA will be unchanged until February 1, 2025.
+> - **Data upload:** Ingestion for MMA will be unchanged until February 1, 2025. After this date, cloud ingestion services will gradually reduce support for MMA agents, which may result in decreased support and potential compatibility issues for MMA agents over time. 
 > - **Installation:** The ability to install the legacy agents will be removed from the Azure Portal and installation policies for legacy agents will be removed. You can still install the MMA agents extension as well as perform offline installations.
 > - **Customer Support:** You will not be able to get support for legacy agent issues.
 > - **OS Support:** Support for new Linux or Windows distros, including service packs, won't be added after the deprecation of the legacy agents.

articles/azure-monitor/logs/data-ingestion-time.md

@@ -52,13 +52,13 @@ Network conditions might negatively affect the latency of this data to reach a d
 
 ### Azure metrics, resource logs, activity log
 
-**30 seconds to 15 minutes**
+**30 seconds to 20 minutes**
 
 Azure data adds more time to become available at a data collection endpoint for processing:
 
 - **Azure platform metrics** are available in under a minute in the metrics database, but they take another 3 minutes to be exported to the data collection endpoint.
 - **Resource logs** typically add 30 to 90 seconds, depending on the Azure service. Some Azure services (specifically, Azure SQL Database and Azure Virtual Network) currently report their logs at 5-minute intervals. Work is in progress to improve this time further. To examine this latency in your environment, see the [query that follows](#check-ingestion-time).
-- **Activity logs** are available for analysis in 3 to 20 minutes.
+- **Activity logs** are available for analysis and alerting in 3 to 20 minutes.
 
 ### Management solutions collection
 

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

@@ -192,7 +192,7 @@ The request body includes the values in the following table.
 
 |Name | Type | Description |
 | --- | --- | --- |
-|properties.retentionInDays | integer  | The table's data retention in days. This value can be between 4 and 730. <br/>Setting this property to null applies the workspace retention period. For a Basic Logs table, the value is always 8. |
+|properties.retentionInDays | integer  | The table's data retention in days. This value can be between 4 and 730. <br/>Setting this property to null applies the workspace retention period. For a Basic and Auxiliary Logs table, the value is always 30. |
 |properties.totalRetentionInDays | integer  | The table's total data retention including long-term retention. This value can be between 4 and 730; or 1095, 1460, 1826, 2191, 2556, 2922, 3288, 3653, 4018, or 4383. Set this property to null if you don't want long-term retention.  |
 
 **Example**