HomeServicesManaged IT ServicesClaude DeploymentInsightsAnswersAboutContact
Security & compliance

What should we do when a Microsoft 365 account is compromised?

Short answer

Contain first: block sign-in, reset the password, revoke all sessions and remove any MFA methods the attacker added. Then check for persistence such as inbox rules, forwarding, mailbox delegates and OAuth app consents. Investigate with the audit and sign-in logs to learn what was accessed and sent, warn anyone who may have received fraudulent mail, and fix the gap that let it happen.

Key facts

  • A password reset alone does not end an attacker session; revoke sessions too.
  • Attackers often add their own MFA method or an inbox rule to stay in.
  • Malicious OAuth app consents survive password resets.
  • Preserve logs before cleanup; investigation depends on them.
  • Legal, insurance and notification duties may apply, so involve them early.

Contain the account in the first hour

Speed matters because a compromised mailbox is often used within hours to send invoice fraud or phishing to contacts. Work through containment in order, and note the time of each step for the incident record.

  • Block sign-in for the user in the Microsoft Entra admin center or Microsoft 365 admin center.
  • Reset the password; for synced accounts, reset in Active Directory and confirm it syncs, or use password writeback.
  • Revoke sessions in Entra ID, or run Revoke-MgUserSignInSession, so refresh tokens stop working.
  • Review authentication methods and delete any phone number, authenticator app or passkey the user does not recognize.
  • If you have Entra ID P2, mark the user as compromised in Identity Protection to raise their risk level.

Remove persistence

Attackers set traps so they can keep reading mail or get back in after a reset. Check each of these before you unblock the user.

CheckWhereWhat to look for
Inbox rulesOutlook or Get-InboxRuleRules that delete, move to RSS or Archive, or forward mail about invoices or payments
ForwardingExchange admin center, mailbox settingsSMTP forwarding to an external address
DelegatesMailbox permissionsFull Access or Send As granted to unknown accounts
App consentsEntra ID, Enterprise applicationsNew apps with mail or file permissions granted by the user
DevicesEntra ID and IntuneNewly registered or joined devices for the user
Sent itemsMailbox and message traceOutbound phishing or payment change requests

Investigate what happened

Before deleting anything, preserve evidence. Export the user's sign-in logs, the unified audit log for the account, inbox rules and message trace results. If Microsoft Defender XDR raised an incident, it often links the related alerts, sign-ins and emails in one place.

Answer four questions: how the attacker got in, when it started, what they accessed, and what they sent. The sign-in logs show IP addresses, locations, apps and whether MFA was satisfied. MailItemsAccessed and file access events in the audit log help show what data was viewed or downloaded.

Handle the business side

If the mailbox sent fraudulent payment instructions, call the recipients by phone using known numbers and tell finance to stop any pending changes to bank details. If sensitive or regulated data may have been exposed, bring in legal counsel and your cyber insurer early, because breach notification rules and policy terms can set deadlines.

If Microsoft restricted the account from sending because of outbound spam, release it in the Defender portal under restricted entities once the account is clean.

Close the gap

Most compromises trace back to a phished password and a weak or missing MFA method, legacy authentication, or a consent phishing app. Fix the root cause, not just the account.

  • Move the user, and their peers in finance and leadership, to phishing-resistant MFA.
  • Block legacy authentication and disable automatic external forwarding tenant-wide.
  • Restrict user consent to apps and turn on the admin consent workflow.
  • Add Conditional Access for compliant devices and risk-based policies where licensed.
  • Write the incident up and update the response runbook.

How Accred Consulting approaches it

Accred Consulting helps organizations prepare for and respond to account compromise. For response, US-based specialists work with your team to contain the account, remove persistence, preserve and review the logs, and recommend fixes. For preparation, discovery reviews logging, MFA and consent settings, then the proposal sets a clear scope, fixed price and timeline for hardening and a written response runbook. Accred does not replace your legal counsel or insurer. Handover includes documentation, the runbook and knowledge transfer, with optional support retainers.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions

No. A reset does not always end existing sessions, and it does nothing about inbox rules, forwarding, added MFA methods or malicious app consents. Revoke sessions, review authentication methods, and check every persistence point before the user is allowed back in.
Search the unified audit log for MailItemsAccessed events for the mailbox during the compromise window, and correlate them with the attacker's IP addresses from the sign-in logs. Coverage depends on your licensing and settings, so confirm mailbox auditing is on before you need it.
Open a support case if you see signs of wider tenant compromise, such as new admins, new app registrations or changes to federation settings. For deeper forensics, many organizations use an incident response firm, often arranged through their cyber insurer.

Want this scoped for your environment?

Book a free consultation. After discovery you get a written plan with scope, a fixed price and a timeline.

Book a free consultation