Microsoft 365 account security needs more than an MFA checkbox. MFA reduces risk, but compromised devices, stolen sessions, inappropriate app permissions and weak recovery processes can still give an attacker access. The answer is stronger layers, not switching MFA off.

Look beyond the MFA checkbox
- Review authentication methods and identity-verification procedures.
- Protect devices and sessions, not only the initial sign-in.
- Review mailbox forwarding, delegation and connected-app permissions.
- Keep an administrator-led response route ready for suspected compromise.
Different authentication methods resist different threats
A password plus a one-time code is better than a password alone, but not every MFA method offers the same resistance to phishing. Where supported, consider phishing-resistant sign-in using properly deployed passkeys or security keys. Verify compatibility before making changes for everyone.
Keep recovery procedures strong as well. A helpdesk process that accepts an unverified caller can undermine carefully configured authentication. Register spare methods securely, review changes to authentication methods and teach staff to report unexpected approval prompts rather than approving them.
Protect the session and the device after sign-in
A successful sign-in creates a session; protecting only the initial password exchange leaves other risks. Keep browsers and endpoints updated, use appropriate device protections and review sign-in risk and access policies. Conditional Access features depend on your Microsoft licences and configuration.
Separate administrative accounts from everyday email use. Limit privileges and avoid unnecessary permanent administrators. Investigate unusual access in context: an unfamiliar location alone is not proof of compromise, and a familiar location alone is not proof of safety.
A password reset is one action, not the whole response
Review suspected compromise with authorised responders using a known clean device. Preserve evidence and coordinate changes that could disrupt legitimate work.
Access review
- Examine sessions and recent authentication-method changes.
- Review privileges and relevant device or sign-in evidence.
- Contain access using the platform's supported procedures.
Persistence and impact
- Check forwarding, inbox rules, delegated access and app grants.
- Assess whether mail, documents or payment instructions were exposed or altered.
- Record findings and involve the responsible privacy or legal contact.
Check mailbox rules and connected applications
A mailbox can keep forwarding messages even after someone changes the user’s password. Review unexpected forwarding, inbox rules, delegated access and recent activity. Check applications with permission to read mail or files, especially requests that staff cannot explain.
Use an approval process for app consent and review existing grants. Removing an unfamiliar app without checking ownership can interrupt legitimate work, so coordinate the review. The aim is understood, justified access, not simply making a dashboard look green.
A suspected takeover needs more than a password reset
Use a known clean device and contact your administrator through a trusted channel. They should contain access, revoke sessions where appropriate, secure authentication methods and investigate rules, permissions and activity. A password reset alone may not remove every route back into the account.
Check whether messages, documents or payment instructions were exposed or altered. Preserve relevant evidence and assess notification obligations with the responsible privacy or legal contact. Microsoft provides a detailed compromised-account response guide; your actual response should fit the account, evidence and available tools.
Turn the checklist into a practical next step
ICT Shift connects identity controls with endpoint and operational reviews across hybrid environments. Read about our Cybersecurity & Business Continuity approach and Cloud & Infrastructure management management, or talk to an engineer to review your Microsoft 365 configuration.
Sources and further reading
Microsoft: compromised accounts; NCSC: small organisation security.



