If a Microsoft 365 work account is hacked, notify an authorized administrator immediately. From a trusted device, the administrator can block unauthorized access, reset affected credentials, review active sessions and investigate mailbox rules and connected apps.
How to Recover a Hacked Microsoft 365 Business Account

Jump to a section
A work account is managed by the organization and may have different recovery options from a personal Outlook.com account. A sign-in problem or service outage alone does not prove compromise. If money may have been diverted, call the bank promptly while the account investigation proceeds.
Choose the recovery route that fits
| Your situation | First route |
|---|---|
| A staff member can no longer sign in | Contact an authorized administrator or IT provider. Use the organization's permitted password or sign-in recovery flow if available. |
| An administrator account is compromised | Use another trusted administrator account if available to contain the affected account and investigate changes. |
| No administrator can sign in | Contact Microsoft through its official business support channels or the authorized reseller. Explain that the organization has lost administrator access. |
| You only see a broad service outage | Check Microsoft service status through an independently opened official channel; do not assume a hack without evidence. |
Secure an affected account
From a trusted administrator account and device, block unauthorized sign-in, reset affected passwords and revoke active sessions where supported. Review registered authentication methods and remove unauthorized changes. Permissions and exact menus vary; if the account is privileged, a sufficiently authorized administrator may be needed.
Inspect mailbox forwarding, inbox rules, delegates, unusual sent messages and connected applications. Check whether other accounts or administrator roles were changed. A password reset alone may not remove every route back in. Microsoft's compromised email account guidance provides the provider's current response sequence.
Preserve relevant alerts, messages and audit logs when safe, but do not delay urgent containment. The administrator compromise playbook covers a wider Microsoft 365 or Google Workspace investigation.
Check when access actually ends. Blocking sign-in and revoking sessions are important, but the effect may not be immediate. Some applications manage their own sessions and may need separate action. Microsoft's emergency access guidance explains why the timing varies and why applications may need their own access removed.
If no administrator can sign in
Check whether another authorized administrator or your organization's Microsoft partner can assist. If not, use Microsoft's business support guidance to find the official support route for your region and explain that administrator access is unavailable. If the admin center cannot be opened, use Microsoft's official customer support page to find the available contact options or ask the authorized reseller for help. Support options and verification requirements vary by subscription and region.
Prepare the business domain, organization and subscription details, the affected account name, and relevant billing or ownership records. Submit documents only through a verified Microsoft support process. Do not disclose passwords or authentication codes to an unsolicited caller, a search-result advertisement or someone claiming they can bypass Microsoft's checks.
Do not create a new tenant or change domain records as an improvised recovery step unless Microsoft or your authorized administrator directs you to do so after assessing the consequences. Microsoft controls its verification and recovery decisions; recovery is not guaranteed.
Check for payment and contact abuse
Look for changed supplier details, messages sent without authorization and unexpected rules that hide replies. If a transfer may be fraudulent, contact the bank immediately and verify the recipient through a previously trusted channel. The business email compromise playbook explains how to coordinate the bank, contacts and mailbox review.
Keep a safe route back in
Once access is restored, review administrator roles, registered sign-in methods, application permissions and audit visibility. Plan a separately protected emergency administrator route appropriate to the organization and test the recovery procedure. Reduce privileges where possible and document the responsible people without sharing credentials.
Our Outlook and Microsoft 365 security guide covers ongoing account hardening. Restored sign-in is a starting point: the organization also needs confidence that unwanted forwarding, applications and privileged access have been addressed.