Merge pull request #270735 from guywi-ms/patch-100

Update agents-overview.md

Author: prmerger-automator[bot]

articles/azure-monitor/agents/agents-overview.md

@@ -283,36 +283,16 @@ This section provides answers to common questions.
 
 An agent is only required to collect data from the operating system and workloads in virtual machines. The virtual machines can be located in Azure, another cloud environment, or on-premises. See [Azure Monitor Agent overview](./agents-overview.md).
 
-### How can I be notified when data collection from the Log Analytics agent stops?
+### Does Azure Monitor Agent support data collection for the various Log Analytics solutions and Azure services like Microsoft Defender for Cloud and Microsoft Sentinel?
 
-Use the steps described in [Create a new log search alert](../alerts/alerts-metric.md) to be notified when data collection stops. Use the following settings for the alert rule:
-
-- **Define alert condition**: Specify your Log Analytics workspace as the resource target.
-- **Alert criteria**:
-   - **Signal Name**: *Custom log search*.
-   - **Search query**: `Heartbeat | summarize LastCall = max(TimeGenerated) by Computer | where LastCall < ago(15m)`.
-   - **Alert logic**: **Based on** *number of results*, **Condition** *Greater than*, **Threshold value** *0*.
-   - **Evaluated based on**: **Period (in minutes)** *30*, **Frequency (in minutes)** *10*.
-- **Define alert details**:
-   - **Name**: *Data collection stopped*.
-   - **Severity**: *Warning*.
-
-Specify an existing or new [action group](../alerts/action-groups.md) so that when the log search alert matches criteria, you're notified if you have a heartbeat missing for more than 15 minutes.
-
-### Will Azure Monitor Agent support data collection for the various Log Analytics solutions and Azure services like Microsoft Defender for Cloud and Microsoft Sentinel?
-
-Review the list of [Azure Monitor Agent extensions currently available in preview](#supported-services-and-features). These extensions are the same solutions and services now available by using the new Azure Monitor Agent instead.
+For a list of features and services that use Azure Monitor Agent for data collection, see [Migrate to Azure Monitor Agent from Log Analytics agent](../agents/azure-monitor-agent-migration.md#migrate-additional-services-and-features).
 
-You might see more extensions getting installed for the solution or service to collect extra data or perform transformation or processing as required for the solution or service. Then use Azure Monitor Agent to route the final data to Azure Monitor.
+Some services might install other extensions to collect more data or to transforms or process data, and then use Azure Monitor Agent to route the final data to Azure Monitor.
 
 The following diagram explains the new extensibility architecture.
 
 :::image type="content" source="./media/azure-monitor-agent/extensibility-arch-new.png" lightbox="./media/azure-monitor-agent/extensibility-arch-new.png" alt-text="Diagram that shows extensions architecture.":::
 
-### Is Azure Monitor Agent at parity with the Log Analytics agents?
-
-Review the [current limitations](./azure-monitor-agent-overview.md#current-limitations) of Azure Monitor Agent when compared with Log Analytics agents.
-
 ### Does Azure Monitor Agent support non-Azure environments like other clouds or on-premises?
 
 Both on-premises machines and machines connected to other clouds are supported for servers today, after you have the Azure Arc agent installed. For purposes of running Azure Monitor Agent and data collection rules, the Azure Arc requirement comes at *no extra cost or resource consumption*. The Azure Arc agent is only used as an installation mechanism. You don't need to enable the paid management features if you don't want to use them.