How to check Microsoft 365 sign-in logs after a suspicious login
Did someone really get into the account? Where to find Microsoft 365 sign-in logs, how to read an entry and what to do when one looks wrong.
A staff member gets an "unusual sign-in" email, a client says they received a strange message from your address, or someone notices an authenticator prompt they did not ask for. The first question is always the same: did someone actually get into the account? In Microsoft 365, the place to answer that is the sign-in log. This guide explains where to find it, how to read an entry without being a security specialist, and what to do if one looks wrong.

Where the sign-in logs are
Sign-in logs live in the Microsoft Entra admin center (entra.microsoft.com), not in the main Microsoft 365 admin center. You need an administrator role that can read reports, such as Global Reader, Security Reader or Reports Reader. Go to Entra ID, then Monitoring & health, then Sign-in logs. To look at one person, open the user under Users and choose Sign-in logs there.
How far back you can see depends on your licenses. With Microsoft Entra ID Free, which comes with most Microsoft 365 business plans, the sign-in logs go back 7 days. With Entra ID P1 or P2, which is included in Microsoft 365 Business Premium, they go back 30 days. So if you suspect a problem, look the same day. The Microsoft Purview audit log also records sign-in events and can be useful for older activity.
The two tabs that matter
- User sign-ins (interactive): someone typed a password, approved a prompt or used a passkey.
- User sign-ins (non-interactive): apps and devices quietly renewing access in the background, such as Outlook on a phone. Attackers who steal a session token often show up here, because they reuse an existing sign-in instead of logging in again. Our article on token replay attacks explains why.
How to read an entry
Click any row to open its details. The fields that tell you most are:
- Status: Success, Failure or Interrupted. Interrupted often means the sign-in stopped to ask for multi-factor authentication. Hundreds of failures with an "invalid username or password" error (code 50126) usually mean someone is guessing passwords. Unpleasant, but not a break-in. A success you cannot explain is what matters.
- Location and IP address: where the sign-in appears to come from. Treat this with care: mobile networks, VPNs and Microsoft's own services can show a city far from the user. A country where nobody on your team has ever been is a stronger signal.
- Application: what was used, for example Office 365 Exchange Online, OneDrive or Microsoft Teams. Sign-ins to unfamiliar apps are worth a closer look.
- Client app and device information: browser, operating system and whether the device is known to your organization. A Windows browser sign-in for someone who only uses a Mac and an iPhone stands out.
- Authentication details: whether MFA was required and how it was satisfied.
- Conditional Access: on Business Premium, which of your access policies applied and whether they blocked the sign-in.
Compare against what the person was really doing. Ask them where they were, which devices they used and whether they approved any prompts. Look at the pattern over several days, not a single row.
Signs that deserve action
- A successful sign-in from a location or device the user does not recognize.
- Successful sign-ins from two distant places within a short time.
- An MFA prompt the user says they did not approve, followed by a success.
- Sign-ins at hours the person never works, especially to Exchange Online.
- New sign-ins straight after a user reports clicking a link or entering their password on a page.
If a sign-in looks wrong
- Revoke sessions for the user in the Entra admin center (or "Sign out of all sessions" in the Microsoft 365 admin center), so stolen sessions stop working.
- Reset the password, and tell the user by phone or in person, not by email.
- Check the user's sign-in methods for a phone number or authenticator app they did not add, and remove it.
- Check the mailbox for new inbox rules, forwarding to outside addresses and messages sent that the user does not recognize. Attackers often hide replies so they can carry on a conversation about invoices.
- Check app consents under Enterprise applications for anything the user recently granted access to.
- Warn the people who matter. If messages went out from the account, tell clients and suppliers by phone to ignore any recent payment change requests.
- Write down what you found with dates and times. If personal data may have been exposed, you may have notification duties: ask a lawyer.
Make the next check easier
Turn on multi-factor authentication for everyone, give admins separate accounts, and decide in advance who checks the logs when an alert arrives. If you rely on the logs often, the 30 days of history and Conditional Access in Business Premium are worth considering.
How we can help
If you think an account has been compromised, we can review the sign-in logs and mailbox with you and lock things down. Our cybersecurity page and our managed IT services explain how we monitor Microsoft 365 for businesses. Call (213) 986-4855.