# Microsoft (2024): what the sources say about the cloud incident

Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.

Microsoft disclosed the incident on 19 Jan 2024. What was exposed, as the sources state it: Microsoft stated that some emails and attached documents were exfiltrated from a very small percentage of corporate email accounts, including senior leadership and cybersecurity and legal staff; a March 2024 update says some source code repositories and internal systems were also accessed.

- **Disclosed:** 19 Jan 2024
- **Incident window:** Late November 2023 to January 12, 2024 (detection), as the company states
- **Cloud or provider:** Microsoft 365
- **What was exposed:** Microsoft stated that some emails and attached documents were exfiltrated from a very small percentage of corporate email accounts, including senior leadership and cybersecurity and legal staff; a March 2024 update says some source code repositories and internal systems were also accessed.
- **How access was gained:** Microsoft stated the threat actor used a password spray attack to compromise a legacy non-production test tenant account, then used that account's permissions to access corporate email accounts.
- **Access path:** [Stolen user credentials and session tokens](/access-paths/stolen-user-credentials/); also [Over-permissioned identities](/access-paths/over-permissioned-identity/)
- **Kind of control that addresses it:** Apply phishing-resistant MFA and lockout to every tenant account including legacy and test tenants, and scope application permissions so a test-tenant identity cannot reach production mailboxes

## In the words of the source

“Beginning in late November 2023, the threat actor used a password spray attack to compromise a legacy non-production test tenant account and gain a foothold” (provider post mortem, [Microsoft Actions Following Attack by Nation State Actor Midnight Blizzard](https://www.microsoft.com/en-us/msrc/blog/2024/01/microsoft-actions-following-attack-by-nation-state-actor-midnight-blizzard))

## Primary sources

- provider post mortem: [Microsoft Actions Following Attack by Nation State Actor Midnight Blizzard](https://www.microsoft.com/en-us/msrc/blog/2024/01/microsoft-actions-following-attack-by-nation-state-actor-midnight-blizzard), dated 19 Jan 2024
- provider post mortem: [Update on Microsoft Actions Following Attack by Nation State Actor Midnight Blizzard](https://www.microsoft.com/en-us/msrc/blog/2024/03/update-on-microsoft-actions-following-attack-by-nation-state-actor-midnight-blizzard), dated 8 Mar 2024
- regulator filing: [Microsoft Form 8-K, Item 1.05, filed 2024-01-19](https://www.sec.gov/Archives/edgar/data/789019/000119312524011295/d708866d8k.htm), dated 19 Jan 2024

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Microsoft%20(microsoft-midnight-blizzard-2024)) with the entry name in the subject.

## Related pages

- [A bank headquartered in San Francisco (not named in the U.](/incidents/sf-bank-cloud-engineer-retained-laptop-2020/)
- [Global Tel*Link Corp. 2023: ftc](/incidents/global-tel-link-ftc-2020/)
- [Sumo Logic 2023: aws credential](/incidents/sumo-logic-aws-credential-2023/)

## Sources

- Microsoft Actions Following Attack by Nation State Actor Midnight Blizzard: https://www.microsoft.com/en-us/msrc/blog/2024/01/microsoft-actions-following-attack-by-nation-state-actor-midnight-blizzard (read 16 Nov 2026)
- Update on Microsoft Actions Following Attack by Nation State Actor Midnight Blizzard: https://www.microsoft.com/en-us/msrc/blog/2024/03/update-on-microsoft-actions-following-attack-by-nation-state-actor-midnight-blizzard (read 16 Nov 2026)
- Microsoft Form 8-K, Item 1.05, filed 2024-01-19: https://www.sec.gov/Archives/edgar/data/789019/000119312524011295/d708866d8k.htm (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/microsoft-midnight-blizzard-2024/
