Thank you for contacting Q&A Forum. To answer your question, the reason why the aggregate date/time shown in the Non-Interactive Sign-In Logs appears to be earlier than the individual events when expanded is due to how Microsoft Entra ID aggregates non-interactive sign-ins for readability and performance.
_ Non-interactive sign-ins (like token refreshes or background app authentications) often occur frequently and with identical metadata (same user, app, IP, resource, etc.).
- To reduce noise, Microsoft groups these sign-ins into a single row in the log view.
- The timestamp shown for the group is the earliest timestamp in that aggregation window (e.g., 1 hour, 6 hours, or 24 hours).
- When you expand the group, you see the individual sign-ins, each with their actual timestamps, which are often later than the group’s timestamp.
You can’t customize or configure the aggregation timestamps in the Entra portal. For more granular control, you can export logs to Azure Monitor, Log Analytics, or Microsoft Sentinel.
For official documentation, please visit this link: https://learn.microsoft.com/en-us/entra/identity/monitoring-health/concept-noninteractive-sign-ins#how-does-it-work.
Kindly let me know if you have any further question or anything that I can clarify.
If I have answered your question, please accept this as answer as a token of appreciation and don't forget to give a thumbs up for "Was it helpful"!
Best regards,
Megan.