Entra ID Register Device with Unusual User Agent (Azure AD Join)
Description
Detects successful Microsoft Entra ID audit events for Register device where additional details indicate an Azure AD join and the recorded user agent is not one of the common native registration clients (Dsreg, DeviceRegistrationClient, or Dalvik-based Android enrollment). Legitimate Windows and standard mobile enrollment flows often present predictable user-agent strings; unexpected clients may reflect scripted registration, third-party tooling, or adversary-driven device registration used for persistence or token abuse. Baseline approved provisioning tools and MDM integrations before tuning.
Query · kuery
data_stream.dataset:"azure.auditlogs" and event.action:"Register device" and event.outcome:(success or Success) and azure.auditlogs.properties.userAgent:(* and not (Dsreg* or DeviceRegistrationClient or Dalvik*)) and azure.auditlogs.properties.additional_details.value:"Azure AD join"
Investigation fields
Pivot points the source recommends for triage.
@timestampevent.actionevent.outcomeazure.auditlogs.properties.userAgentazure.auditlogs.properties.additional_details.valueazure.auditlogs.properties.initiated_by.user.userPrincipalNameazure.auditlogs.properties.initiated_by.user.ipAddressazure.auditlogs.properties.target_resources.0.display_nameazure.auditlogs.properties.target_resources.0.idazure.correlation_id
Known false positives
- Custom device management agents, OEM enrollment clients, or updated Microsoft clients that use new user-agent strings may match. Add exclusions for known `azure.auditlogs.properties.userAgent` values or enrollment programs after review.
Analyst notes
Investigating Entra ID Register Device with Unusual User Agent (Azure AD Join)
Review azure.auditlogs.properties.initiated_by.user.userPrincipalName, source IP fields on the audit event,
azure.auditlogs.properties.target_resources.0.display_name for the device name, and
azure.correlation_id for related audit entries.
Compare azure.auditlogs.properties.userAgent to your organization's standard Autopilot, Intune, and Windows enrollment
clients.
Possible investigation steps
- Confirm whether the user intentionally joined a device and whether the user agent matches a known provisioning package.
- Pivot to
azure.signinlogsfor the same principal and timeframe for risky sign-ins or token broker activity. - Search for other
Register deviceevents from the same IP or user agent across the tenant.
Response and remediation
- If malicious, remove the device in Entra ID, revoke refresh and primary refresh tokens for the user, and reset credentials per policy.
- Tighten device registration and join controls via Conditional Access and device compliance policies.