Black Friday sale: an extra 40% off every course until Monday, November 30.New Year sale: an extra 30% off every course until Friday, January 1.Memorial Day sale: an extra 25% off every course until Monday, May 31.SysAdmin Day sale: an extra 25% off every course until Sunday, August 1.Back to School sale: an extra 25% off every course until Sunday, August 22.Labor Day sale: an extra 25% off every course until Monday, September 6.Black Friday sale: an extra 40% off every course until Monday, November 29.New Year sale: an extra 30% off every course until Saturday, January 1.Choose your certification →

Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.2.5. Investigating and Resolving Authentication Issues

💡 First Principle: Every sign-in leaves a record of every decision made about it — which method was used, which Conditional Access policies matched, and which control failed. Troubleshooting isn't guessing; it's reading the record, and simulating the sign-in when the record doesn't exist yet.

Sign-in logs (Microsoft Entra admin center, under Monitoring & health > Sign-in logs) are the first stop. They come in four categories: interactive user, non-interactive user (token refreshes and apps acting for a user), service principal and managed identity. Each entry shows the result, an error code and failure reason, the authentication details (which methods were attempted and satisfied), and a Conditional Access tab listing each policy as applied, not applied, or report-only. A result of "Report-only: Failure" means the policy's conditions matched and its control wasn't met — but the sign-in wasn't blocked, because the policy is only reporting.

Retention matters: sign-in logs are kept 7 days on Entra ID Free and 30 days on P1/P2. To keep them longer — or to query them alongside other data — route them to Azure Monitor (a storage account or a Log Analytics workspace). The Conditional Access insights and reporting workbook needs a Log Analytics workspace receiving sign-in logs.

Tools for "what would happen":
  • The Conditional Access What If tool simulates a sign-in for a chosen user, app and set of conditions and shows which policies would apply — without the user having to sign in. Use it before enabling a policy, or when a user reports a block you can't reproduce.
  • Report-only mode gives the same answer from real traffic over days.
Common causes and fixes:
SymptomLikely causeWhere to look
User blocked unexpectedlyA Conditional Access policy matched (location, device, risk)Sign-in log > Conditional Access tab; What If
Prompted for MFA repeatedlySign-in frequency session control, or MFA claims from a partner tenant not trustedPolicy session controls; cross-tenant trust settings
Can't complete MFANo usable method registered, or a method shown as non-usable (expired TAP, key failed attestation)User's authentication methods
Account lockedSmart lockout after repeated failuresSign-in log error code; lockout settings
Legacy app can't sign inLegacy authentication blocked by security defaults or Conditional AccessClient app shown in the sign-in log

⚠️ Exam Trap: If a user "can't sign in, but the sign-in log shows the policy as report-only failure," that policy didn't cause the block — look at the policies that were actually applied. And if the incident is older than your log retention (7 days on Free), the sign-in log can't answer the question at all.

Reflection Question: A user reports being blocked from Exchange Online last Tuesday, but you can't reproduce it today. Which two tools would you use, and why might one of them return nothing?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•26 professional certifications earned