Join our Newsletter — 33% off our NHI Course
Home› FAQ› Threats, Abuse & Incident Response› Why do password resets sometimes fail to stop…
Threats, Abuse & Incident Response

Why do password resets sometimes fail to stop Microsoft 365 compromise?

← Back to all FAQ
By NHI Mgmt Group Editorial Team Updated October 30, 2026 Domain: Threats, Abuse & Incident Response

Password resets can fail because the attacker may already hold valid refresh tokens. If those tokens are not explicitly revoked, the attacker can keep accessing mail, files, and identity-linked services even after the password changes. Containment has to address the session, not only the credential.

Why password resets do not always end the compromise

A password change only replaces one authentication secret. If the attacker already has a live session or token, access can continue until that session is explicitly revoked. In Microsoft 365 environments, this is why containment often has to include token invalidation, sign-out and session review, not just a reset of the user password.

The practical issue is that modern cloud sign-in is not a single event. Browser sessions, mobile clients, mail apps and connected services can each hold separate credentials or refresh artefacts, so the attacker may retain access through a path that the new password does not touch. That makes the reset incomplete as a containment step.

For a broader view of how Microsoft 365 exposure accumulates across mail, files, app consent and audit signals, Microsoft 365 Security Guide is the right backdrop for this failure mode.

What keeps the attacker inside after the reset

The core failure is session persistence. A refresh token or similar session artefact can remain valid after the password changes, especially if the tenant does not explicitly revoke sessions, invalidate tokens, or force reauthentication across all clients. That leaves the compromise alive in the identity plane even though the credential itself has been replaced.

This is why the same mailbox, file store or app access may still look legitimate after a reset. The sign-in surface has shifted from the password to the issued session, so the defender has to cut off the session lineage. If you want the failure pattern framed through real-world breach behaviour, the State of NHI & AI Agent Breach Report 2026 shows how stolen tokens and credentials are repeatedly used to preserve access.

In Microsoft 365 incident response, session revocation is the containment action that actually changes the attacker’s position. Without it, the password reset is often only a hygiene step, not a full eviction.

What responders should check before declaring the account clean

Confirm whether the attacker accessed Exchange, SharePoint, OneDrive, Entra-linked apps or third-party SaaS connected through the tenant before the reset. Then review whether active sessions, OAuth grants, app passwords, device sign-ins, or legacy clients still provide a path back in. A reset that does not address those artefacts can leave the same operator in place under a new authentication state.

Also verify whether the user account was used to create mailbox rules, add forwarding, consent to apps, or tamper with recovery settings. Those are often the persistence points that survive a simple password change. If the account participates in a privileged workflow, a wider review of adjacent accounts and admin approvals is warranted.

For a reset process that treats recovery and session invalidation as part of the same control, Secure Password Reset Flow Guide is directly relevant. When the problem becomes a broader tenant incident rather than a single user issue, the Help Desk Social Engineering Incident Playbook and Microsoft 365 Security Guide provide useful operational context.

Risk and Threat Considerations

The risk is that a password reset creates a false sense of containment while the attacker retains authenticated access through existing tokens or sessions. In Microsoft 365, that can preserve mail access, document access and downstream app access long enough for data theft, inbox manipulation or lateral movement to continue.

Failure mechanism: The password is changed, but the active session, refresh token or app grant remains valid, so the attacker does not need to reauthenticate.

Impact: The compromise persists after the visible fix, allowing continued access to mail, files, shared links and identity-linked services until sessions and related grants are revoked.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.

FrameworkControl / ReferenceRelevance
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementSession and credential lifecycle control is central to reset-driven containment.
IA-2 — Identification and Authentication (Organizational Users)The issue is continued user access after password change in Microsoft 365.
AC-2 — Account ManagementAccount disablement, review and revocation actions determine whether access persists.
Recommendation — Revoke stale authenticators and invalidate affected sessions after compromise. Require reauthentication when user compromise is suspected. Review and revoke affected account access paths during containment.
CIS Controls v8CIS-5 — Account ManagementAccount and session lifecycle control directly addresses password-reset containment gaps.
Recommendation — Disable or reset affected accounts and remove lingering access.

Practitioner Guidance

What to verify: Treat password reset as incomplete until you confirm token revocation, forced sign-out and reauthentication across all affected clients. If you cannot prove the sessions were invalidated, assume the attacker may still be present.

Decision rule: If the account touched mail, file sharing or app consent, prioritise session revocation and audit review before closing the incident. If privileged or high-value data is involved, widen the scope to adjacent accounts and recovery settings rather than stopping at the user password.

Practitioner takeaway: The real containment objective is to remove the attacker’s authenticated state, not merely to change the password that originally created it.

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 30, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org