Sign-In Logs in Microsoft 365: A Five-Minute Weekly Look

Friday afternoon, the administrator has five minutes before the weekly huddle. She opens one screen in Microsoft 365, scans down a list of recent sign-ins, and notices that her director of nursing signed in from a city two states away at 3 a.m. The director of nursing was asleep in Edmond. That five-minute habit just found a problem a week or a month sooner than it would have been found otherwise.

You do not need to be technical to do this. You need to know where to look and what unusual looks like.

What the sign-in log is

Microsoft 365 keeps a record of who signed in, when, from where and to what. In the Entra admin center (the part of Microsoft 365 that manages accounts), this appears as sign-in logs. Each entry typically shows the user, the application, a time, an approximate location, the device or browser type, and whether the attempt succeeded or failed.

How far back the history goes depends on your license, so a weekly look matters. Old entries eventually fall away.

Location is approximate. It is based on internet addresses, which can be wrong, especially for phones and some corporate networks. Treat an odd location as a reason to ask a question, not as proof.

Who should look

Ideally one person owns it: the administrator, the business office manager or your IT contact. If you work with an outside IT provider, ask who reviews the logs, how often and how you will hear about anything found. You may do the weekly look yourself as a second pair of eyes. Account access to this screen is limited to certain administrative roles, so ask your provider to give you the right level of access, ideally view-only.

What to scan for

Set a timer and sort or filter by the last week. Look for:

Unfamiliar places. Sign-ins from countries or cities where you have no staff, residents' families or travelers.

Impossible travel. The same person signing in from far-apart places within a short time.

Repeated failures. Many failed attempts against one account, or one failure after another across many accounts, which can mean someone is guessing passwords.

Odd hours. Activity at times that do not match that person's shift, remembering that some staff do work nights.

Unusual applications. An account signing in to something the person never uses.

Failures that suddenly succeed. A string of failures followed by a success is worth a second look.

Accounts that should be quiet. A former employee, a shared mailbox or a seasonal worker whose account still shows activity.

A single failure is normal. People mistype passwords, and phones forget saved ones. What matters is the pattern.

What to do when something looks wrong

Do not guess. Write down the user, the time and what you saw, and contact your IT provider the same day. They can confirm whether it is real and, if so, reset the password, end open sessions, check for forwarding rules and review what the account touched. Contact the staff member, too, by phone or in person, rather than by email, in case the mailbox itself is in question.

If the account is one that handles resident information, tell your compliance or privacy contact. Whether an incident needs formal reporting depends on the facts and the law, so confirm with your counsel or compliance advisor.

Keep it short and repeatable

The point is consistency, not depth. A few habits make it stick:

Same day and time each week, tied to something you already do.

A simple note: date, who looked, anything found, anything escalated.

A list of known exceptions, such as the nurse who travels or the administrator who checks email from a vacation spot.

A yearly reminder to confirm with IT how long logs are kept and whether you can export them.

Over a few weeks you will learn what normal looks like for your building, and the odd entries will stand out faster.

If you work with an outside provider, it is fair to ask them what they watch between your weekly looks. Your five minutes is a second set of eyes, not a replacement for ongoing monitoring, and the two together catch more than either alone.

How we can help

UnityCare IT can set up view-only access for your leadership, show your team what a normal week looks like, and watch for suspicious sign-ins as part of our managed service. When something does look wrong, our help desk, including after hours, can help you respond.

Related service

Microsoft 365, cloud storage and tested backups with access controls built in.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support