Security checks / Check reference / Users & accounts
User Last Password Change
Info Severity Microsoft 365 security check in the Users & accounts domain.
User's last password change timestamp Password age is always informational by default. Siemserva runs this check automatically across your tenant and maps every finding to the compliance frameworks below.
Check summary
What this check verifies
User's last password change timestamp
Why it matters
Password age is always informational by default. NIST SP 800-63B does not recommend mandatory periodic rotation, forcing users to change strong passwords increases risk by encouraging weaker substitutes. This finding records age for visibility only. Organizations with a strict compliance mandate for periodic rotation can enable enforcement by setting Password Age Reporting to Medium or High in Settings.
How to fix it
No action required by default, password age is informational only. If your compliance policy mandates periodic rotation, set Password Age Reporting to Medium or High in Settings (under Scan behavior), then ensure users rotate passwords before the 90-day threshold or migrate to passwordless authentication.
Siemserva flags every tenant where this check fails and, with Senserva Trustworthy AI remediation, can propose a validated fix you approve before it applies.
Ask your own AI about this check
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Compliance framework mappings
Findings from this check serve as evidence for:
References
Related Users & accounts checks
Related Entra ID guides
This is an Entra ID and identity check. See the broader guidance and the exact checks Siemserva runs in this area:
Common questions
What does the User Last Password Change check verify?
User's last password change timestamp It is a Info Severity check in the Users & accounts domain, one of the 650+ checks Siemserva runs across Microsoft 365, Intune, Defender, and Entra ID.
How do I fix a User Last Password Change finding?
No action required by default, password age is informational only. If your compliance policy mandates periodic rotation, set Password Age Reporting to Medium or High in Settings (under Scan behavior), then ensure users rotate passwords before the 90-day threshold or migrate to passwordless authentication. Siemserva ranks the finding by Severity and, with Senserva Trustworthy AI, can propose a validated, approve-before-apply configuration fix.
Which compliance frameworks does this check evidence?
Findings from this check map to SCuBA, MCSB, NIST, SOC2, CIS, HIPAA, including SCuBA policy MS.AAD.6.1v1, and MCSB controls AM-1, IM-1. That mapping is what turns a scan finding into audit evidence.
Can I ask my own AI about this check?
Yes. This page includes a free copy-paste AI prompt carrying the check's facts: what it verifies, the risk, the remediation, and the framework mappings. Paste it into Claude, ChatGPT, or Copilot; cite-worthy detail without giving an AI access to your tenant.
All 672 checks with severities and mappings: the Microsoft 365 security checks catalog.