Audit Logs / Microsoft Entra ID AuditLogs category

Audit Logs: Uncategorized

OperationNameDescriptionSampleRule
anyAny Microsoft Entra ID directory audit operation recorded in the AuditLogs table (no specific OperationName filter).NY

any: Entra ID audit event (any operation)

#
Source
Microsoft Entra ID audit log

Description

Any Microsoft Entra ID directory audit operation recorded in the AuditLogs table (no specific OperationName filter).

Common Indicators #

Field/value combinations most frequently checked by detection rules targeting this event, derived from cross-vendor predicate analysis.

FieldKindValueRulesVendors
Result (kusto rule field)eqsuccess12 ruleskusto
RoleName (kusto rule field)containsadmin7 ruleskusto
AADOperationType (kusto rule field)inAssign6 ruleskusto
AADOperationType (kusto rule field)inAssignEligibleRole5 ruleskusto
displayName (kusto rule field)contains@5 ruleskusto
displayName (kusto rule field)eqrole.displayname6 ruleskusto
displayName (kusto rule field)eqkeydescription4 ruleskusto
key (kusto rule field)equser-agent6 ruleskusto
type (kusto rule field)eqpolicy6 ruleskusto
type (kusto rule field)eqapplication4 ruleskusto
type (kusto rule field)inserviceprincipal4 ruleskusto
type (kusto rule field)inuser4 ruleskusto
Initiator (kusto rule field)neMS-PIM5 ruleskusto
Initiator (kusto rule field)neMS-PIM-Fairfax3 ruleskusto
userPrincipalName (kusto rule field)contains@5 ruleskusto

Detection Rules #

Full rule details for this event, including ATT&CK technique mappings and native queries →

Sigma #

Elastic #

  • Entra ID Sign-in BloodHound Suite User-Agent Detected source high: Identifies potential enumeration activity using AzureHound, SharpHound, or BloodHound across Microsoft cloud services. These tools are often used by red teamers and adversaries to map users, groups, roles, applications, and access relationships within Microsoft Entra ID (Azure AD) and Microsoft 365.T1069, T1069.003, T1082, T1087, T1087.004, T1201
  • Entra ID Actor Token User Impersonation Abuse source medium: Identifies potential abuse of actor tokens in Microsoft Entra ID audit logs. Actor tokens are undocumented backend mechanisms used by Microsoft for service-to-service (S2S) operations, allowing services to perform actions on behalf of users. These tokens appear in logs with the service's display name but the impersonated user's UPN. While some legitimate Microsoft operations use actor tokens, unexpected usage may indicate exploitation of CVE-2025-55241, which allowed unauthorized access to Azure AD Graph API across tenants before being patched by Microsoft.T1078, T1078.004, T1548, T1550, T1550.001
  • Entra ID Kali365 Default User-Agent Detected source high: Identifies the default user agent string associated with Kali365 (also referred to as Kali365 Live), a phishing-as-a-service (PhaaS) platform that automates OAuth 2.0 device code phishing and adversary-in-the-middle (AiTM) session capture against Microsoft 365 and Microsoft Entra ID. The Kali365 Electron desktop client identifies itself with the user agent kali365-live/1.0.0 when polling for and replaying captured OAuth tokens, so its appearance in Entra ID sign-in logs, Entra ID audit logs, or the Microsoft 365 unified audit log indicates that an attacker-controlled Kali365 client is interacting with the tenant using stolen tokens. Unlike dual-use offensive tooling, Kali365 is a criminal service with no legitimate enterprise use, making this user agent a high-fidelity indicator of active account compromise.T1078, T1078.004, T1528, T1550, T1550.001, T1566

Splunk #

  • Azure AD PIM Role Assigned source: The following analytic detects the assignment of an Azure AD Privileged Identity Management (PIM) role. It leverages Azure Active Directory events to identify when a user is added as an eligible member to a PIM role. This activity is…T1098, T1098.003
  • Azure AD Service Principal New Client Credentials source: The following analytic detects the addition of new credentials to Service Principals and Applications in Azure AD. It leverages Azure AD AuditLogs, specifically monitoring the "Update application*Certificates and secrets management"…T1098, T1098.001

Kusto #

YARA-L #

Panther #

  • Azure Authentication Methods Policy OIDC Discovery URL Changed source high: Detects modifications to the OIDC discovery URL in Azure Entra ID's Authentication Methods Policy. This technique enables attackers to federate the tenant with attacker-controlled identity providers, bypassing multi-factor authentication and enabling unauthorized access through bring-your-own IdP methods.T1556, T1556.009
  • Azure Domain Federation Settings Modified source medium: Detects modifications to domain federation settings in Microsoft Entra ID, including changes to federation trust configurations and OIDC discovery endpoints. Adversaries who compromise administrative accounts may modify these settings to federate the tenant with attacker-controlled identity providers, enabling unauthorized access and MFA bypass. This technique allows attackers to establish persistent access by redirecting authentication to malicious infrastructure.T1556, T1556.006
  • Azure User Elevated to User Access Administrator Role source high: Detects when a user elevates their permissions to the "User Access Administrator" role in Azure, which grants full control over access management for Azure resources. The User Access Administrator role is one of the most powerful privileged roles in Azure, allowing the holder to manage user access to all Azure resources, assign roles to other users including administrative roles, and effectively control the entire Azure subscription's permission structure.T1098, T1098.003

References #

Rules often query computed field names, not native AuditLogs columns #

Many Entra detection rules pivot on field names that are not columns in this table but KQL projections the rule author computes from two dynamic columns. Searching the field list for those names finds nothing; use the canonical paths instead.

  • InitiatingUserPrincipalName (and sibling Initiating* names) is not a column. Rules project it from InitiatedBy, for example extend InitiatingUserPrincipalName = tostring(InitiatedBy.user.userPrincipalName). The native paths are InitiatedBy.user.userPrincipalName, InitiatedBy.user.displayName, and InitiatedBy.user.id for user actors, and InitiatedBy.app.displayName / InitiatedBy.app.appId for application or service-principal actors.
  • What changed lives in TargetResources, a dynamic array. Expand it before filtering on the change: AuditLogs | mv-expand TargetResources | extend props = TargetResources.modifiedProperties, then read props[].displayName, props[].oldValue, and props[].newValue.

Column shapes per the AuditLogs table reference and the Graph directoryAudit resource.