Elastic Security Detection Rules

Azure Automation Account Created

Last updated 7 days ago on 2025-09-26
Created 5 years ago on 2020-08-18

About

Identifies when an Azure Automation account is created. Azure Automation accounts can be used to automate management tasks and orchestrate actions across systems. An adversary may create an Automation account in order to maintain persistence in their target's environment.
Tags
Domain: CloudData Source: AzureUse Case: Identity and Access AuditTactic: PersistenceLanguage: kuery
Severity
low
Risk Score
21
MITRE ATT&CK™

Persistence (TA0003)(opens in a new tab or window)

↳ Valid Accounts (T1078)(opens in a new tab or window)

Defense Evasion (TA0005)(opens in a new tab or window)

↳ Valid Accounts (T1078)(opens in a new tab or window)

License
Elastic License v2(opens in a new tab or window)

Definition

Rule Type
Query (Kibana Query Language)
Integration Pack
Prebuilt Security Detection Rules
Index Patterns
logs-azure.activitylogs-*filebeat-*
Related Integrations

azure(opens in a new tab or window)

Query
event.dataset:azure.activitylogs and azure.activitylogs.operation_name:"MICROSOFT.AUTOMATION/AUTOMATIONACCOUNTS/WRITE" and event.outcome:(Success or success)

Install detection rules in Elastic Security

Detect Azure Automation Account Created in the Elastic Security detection engine by installing this rule into your Elastic Stack.

To setup this rule, check out the installation guide for Prebuilt Security Detection Rules(opens in a new tab or window).