Description
The [Elastic Agent](https://www.elastic.co/security) data connector provides the capability to ingest Elastic Agent logs, metrics, and security data into Microsoft Sentinel.
- Declared status
- 1
- Declared author / publisher
- Elastic
Declared sources
Metadata from the source file. No dependencies inferred from KQL.
Data types
Declared permissions
read and write permissions are required.
Workspace
Workspace
read permissions to shared keys for the workspace are required. [See the documentation to learn more about workspace keys](https://docs.microsoft.com/azure/azure-monitor/platform/agent-windows#obtain-workspace-id-and-key).
Keys
Workspace
Include custom pre-requisites if the connectivity requires - else delete customs
Description for any custom pre-requisite
Connector instructions
Content published in the repository. Refer to the original file for all parameters.
>**NOTE:** This data connector depends on a parser based on a Kusto Function to work as expected [**ElasticAgentEvent**](https://aka.ms/sentinel-ElasticAgent-parser) which is deployed with the Microsoft Sentinel Solution.
>**NOTE:** This data connector has been developed using **Elastic Agent 7.14**.
1. Install and onboard the agent for Linux or Windows
Install the agent on the Server where the Elastic Agent logs are forwarded.
> Logs from Elastic Agents deployed on Linux or Windows servers are collected by **Linux** or **Windows** agents.
Choose where to install the Linux agent:
Install agent on Azure Linux Virtual Machine
Select the machine to install the agent on and then click **Connect**.
Install agent on a non-Azure Linux Machine
Download the agent on the relevant machine and follow the instructions.
Choose where to install the Windows agent:
Install agent on Azure Windows Virtual Machine
Select the machine to install the agent on and then click **Connect**.
Install agent on a non-Azure Windows Machine
Download the agent on the relevant machine and follow the instructions.
2. Configure Elastic Agent (Standalone)
[Follow the instructions](https://www.elastic.co/guide/en/fleet/current/elastic-agent-configuration.html) to configure Elastic Agent to output to Logstash
3. Configure Logstash to use Microsoft Logstash Output Plugin
Follow the steps to configure Logstash to use microsoft-logstash-output-azure-loganalytics plugin:
3.1) Check if the plugin is already installed:
> ./logstash-plugin list | grep 'azure-loganalytics'
**(if the plugin is installed go to step 3.3)**
3.2) Install plugin:
> ./logstash-plugin install microsoft-logstash-output-azure-loganalytics
3.3) [Configure Logstash](https://github.com/Azure/Azure-Sentinel/tree/master/DataConnectors/microsoft-logstash-output-azure-loganalytics) to use the plugin
4. Validate log ingestion
Follow the instructions to validate your connectivity:
Open Log Analytics to check if the logs are received using custom table specified in step 3.3 (e.g. ElasticAgentLogs_CL).
>It may take about 30 minutes until the connection streams data to your workspace.
Related content
Links established from declared identifiers and solution manifests.
Source provenance
GitHubDisplayed values come from files in Azure/Azure-Sentinel. They describe the published template, not your workspace configuration.
- Commit
629d1d3↗- Source identifier
ElasticAgent
GSTEP / CATALOG TRACKING
Added to catalog : 16 Sept 2026 · 05:49 UTC
Last change observed : 16 Sept 2026 · 05:49 UTC