Theory · 9 min · Identity and sign-in logs
Reading a sign-in record
Read an Entra ID sign-in row and pick out the fields that matter.
Microsoft Entra ID writes interactive sign-ins to SigninLogs (non-interactive ones, such as token refreshes, go to AADNonInteractiveUserSignInLogs). Each row has who, from where, to what, and how it went.
Who: UserPrincipalName. From where: IPAddress and Location, and the device and client in DeviceDetail and UserAgent. To what: AppDisplayName and ResourceDisplayName.
How it went: ResultType ("0" is success), AuthenticationRequirement (single or multi-factor), the MFA detail, and ConditionalAccessStatus. A success where MFA was "satisfied by claim in the token" means no fresh MFA prompt happened in this sign-in.
Location comes from an IP database and can be wrong, especially for VPNs and mobile networks. The ASN (who owns the IP) is often more telling: a hosting provider is not where your staff sit.
- UPN
- User principal name: the sign-in name of an account, written like an email address (j.miller@contoso.com).
- ASN
- Autonomous system number: the network an IP address belongs to, and so who owns it (an ISP, a mobile operator, a hosting provider).
- Conditional Access
- Entra ID policies that decide, per sign-in, whether to allow it, ask for MFA or block it, based on user, app, device and location.
Your turn: select the field that proves it. This sign-in succeeded. Select the two fields that make it most suspicious for a sales user who works from Columbus, Ohio on a company laptop.
Do the interactive check Free, in the browser.
Sources
- SigninLogs table reference Microsoft Learn
- Microsoft Entra authentication and authorization error codes Microsoft Learn