diff --git a/data-explorer/integrate-data-overview.md b/data-explorer/integrate-data-overview.md
index 357924bfd1..3f1adf13ab 100644
--- a/data-explorer/integrate-data-overview.md
+++ b/data-explorer/integrate-data-overview.md
@@ -3,7 +3,7 @@ title: Data integrations overview
 description: Learn about the available data integrations.
 ms.reviewer: aksdi
 ms.topic: conceptual
-ms.date: 01/30/2024
+ms.date: 01/06/2026
 # CustomerIntent: As a data ingestor, I want to know what data connectors and tools are available, so that I can choose the right one for my use case.
 ---
 # Data integrations overview
@@ -44,6 +44,7 @@ The following tables summarizes the available data connectors, tools, and integr
 | [Azure Event Hubs](integrate-overview.md#azure-event-hubs) | **Ingestion** | :heavy_check_mark: | | First party | Messaging |
 | [Azure Functions](integrate-overview.md#azure-functions) | **Export**<br /><br />**Ingestion** | | | First party | Workflow integrations |
 | [Azure IoT Hubs](integrate-overview.md#azure-iot-hubs) | **Ingestion** | :heavy_check_mark: | | First party | IoT data |
+| [Azure Monitor](integrate-overview.md#azure-monitor) | **Ingestion** | | | First party | 	Azure Monitor Agent can send the following virtual machine data to Azure Data Explorer using a data collection rule: Performance counters, IIS logs, Windows event logs, Linux system logs, Custom text logs, and Custom JSON logs |
 | [Azure Stream Analytics](integrate-overview.md#azure-stream-analytics) | **Ingestion** | :heavy_check_mark: | | First party | Event processing |
 | [Cribl Stream](integrate-overview.md#cribl-stream) | **Ingestion** | :heavy_check_mark: | | First party | Telemetry, Logs, Metrics, Machine data processing |
 | [Fluent Bit](integrate-overview.md#fluent-bit) | **Ingestion** | | | [Open source](https://github.com/fluent/fluent-bit) | Logs, Metrics, Traces |
diff --git a/data-explorer/integrate-overview.md b/data-explorer/integrate-overview.md
index 30f2036088..b9fdb39416 100644
--- a/data-explorer/integrate-overview.md
+++ b/data-explorer/integrate-overview.md
@@ -63,6 +63,7 @@ The following table summarizes the available connectors and their capabilities:
 | [Splunk](#splunk)                                                                     | :heavy_check_mark: |                    |                    |                    |
 | [Splunk Universal Forwarder](#splunk-universal-forwarder)                             | :heavy_check_mark: |                    |                    |                    |
 | [Telegraf](#telegraf)                                                                 | :heavy_check_mark: |                    |                    |                    |
+| [Azure Monitor](#azure-monitor)                                                       | :heavy_check_mark: |                    |                    |                    |
 
 ### [Tools and integrations](#tab/integrations)
 
@@ -371,6 +372,19 @@ Telegraf is an open source, lightweight, minimal memory foot print agent for col
 * **Documentation:** [Ingest data from Telegraf](ingest-data-telegraf.md)
 * **Community Blog:**  [New Azure Data Explorer output plugin for Telegraf enables SQL monitoring at huge scale](https://techcommunity.microsoft.com/t5/azure-data-explorer-blog/new-azure-data-explorer-output-plugin-for-telegraf-enables-sql/ba-p/2829444)
 
+### Azure Monitor
+	
+Azure Monitor Agent can send the following virtual machine data to Azure Data Explorer using a data collection rule:
+
+- Performance counters
+- IIS logs
+- Windows event logs
+- Linux system logs
+- Custom text logs
+- Custom JSON logs
+
+For more information, see [Collect data from virtual machines to Azure Data Explorer](/azure/azure-monitor/vm/send-fabric-destination).
+
 ### [Tools and integrations](#tab/integrations)
 
 ### Azure CLI