# Entra ID Sign-ins

AADSTS result codes and risk detections, read as investigative signals.

Microsoft's AADSTS reference is written for developers fixing an app. Reading a tenant's sign-in log after an incident is a different job. Thirty 50126 failures against thirty users is a password spray, not thirty typos.

## Before you read the table

- Successful sign-ins carry risk detections too. A success flagged atypical travel is more urgent than any failure on the page.
- The authentication requirement field proves MFA. A policy existing does not. singleFactorAuthentication means MFA was not satisfied.

## Related

- [M365 Audit Log](https://www.cyberkit.win/reference/m365-audit-log/)
- [Okta System Log](https://www.cyberkit.win/reference/okta-events/)
- [Cloud Identity Case: Identity](https://www.cyberkit.win/drills/cloud-identity/?stage=identity)

Canonical: https://www.cyberkit.win/reference/entra-signin/

This is a static reference page. It does not collect anything.
