Entra ID Temporary Access Pass Created for User
Description
Identifies the creation of a Temporary Access Pass (TAP) for an Entra ID user account. A TAP is a time-limited passcode that allows passwordless authentication and bypasses existing MFA requirements, including phishing-resistant methods. An attacker with User Administrator or Authentication Administrator privileges can issue a TAP for a target account, sign in without the current password, and register new persistent authentication methods before the TAP expires.
Query · kuery
data_stream.dataset: "azure.auditlogs" and
(
(
azure.auditlogs.operation_name: "User registered security info" and
azure.auditlogs.properties.result_reason: "User registered temporary access pass method"
) or (
azure.auditlogs.operation_name: "Create Temporary Access Pass method for user"
) or (
azure.auditlogs.operation_name: "Admin registered security info" and
azure.auditlogs.properties.target_resources.*.modified_properties.*.display_name: *TemporaryAccessPass*
)
) and
event.outcome: ("Success" or "success")
Known false positives
- Help desk teams issuing TAPs for locked-out users or new employee onboarding workflows. Automated identity lifecycle systems that provision TAPs during device enrollment.
Analyst notes
Investigating Entra ID Temporary Access Pass Created for User
A Temporary Access Pass is a time-limited credential that bypasses all existing MFA factors for the target account. In a steady-state tenant, TAP creation is rare and should be correlated against help desk records or onboarding workflows.
Possible investigation steps
- Identify the administrator who created the TAP (
azure.auditlogs.properties.initiated_by) and verify whether the action was authorized by a help desk ticket or change management record. - Identify the target account and assess its privilege level -- TAPs issued for Global Administrators, Application Administrators, or accounts with high-value data access are highest risk.
- Check for sign-ins by the target account using the TAP credential: look for sign-ins where
azure.signinlogs.properties.authentication_detailscontains "Temporary Access Pass" shortly after the TAP creation event. - If the TAP was used to sign in, review what authentication methods were registered during or after the session -- an attacker will use the TAP window to add a persistent authenticator.
- Check whether the creating administrator's account shows anomalous activity in the preceding 24 hours.
False positive analysis
- TAP creation by your identity team for locked-out users is a legitimate workflow. Confirm via help desk ticket correlation.
- New employee onboarding that provisions TAPs as part of passwordless enrollment is expected behavior.
Response and remediation
- Revoke the TAP immediately if unauthorized: Entra ID > Users > Authentication methods.
- Audit all authentication methods registered by the target account after TAP creation and remove any that were not previously present.
- Reset the target account's password and revoke all active sessions.
- Review the creating administrator's recent actions for signs of compromise.