Microsoft (2022): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Microsoft disclosed the incident on 22 Mar 2022. What was exposed, as the sources state it: The company stated that the actor claimed to have exfiltrated portions of source code, that no customer code or data was involved, and that a single account had been compromised, granting limited access.
Open the ledger · Report a correction
- Disclosed
- 22 Mar 2022
- Incident window
- not public
- Cloud or provider
- not public
- What was exposed
- The company stated that the actor claimed to have exfiltrated portions of source code, that no customer code or data was involved, and that a single account had been compromised, granting limited access.
- How access was gained
- The company stated that a single account was compromised, granting limited access, and that the tactics used in this intrusion reflect those described in the same post (including stolen credentials and MFA prompt abuse).
- Access path
- Stolen user credentials and session tokens
- Kind of control that addresses it
- require phishing-resistant MFA, block MFA approval prompts and session-token replay, and limit what a single account can reach
In the words of the source
“Our investigation has found a single account had been compromised, granting limited access.” (provider post mortem, DEV-0537 criminal actor targeting organizations for data exfiltration and destruction)
Primary sources
- provider post mortem: DEV-0537 criminal actor targeting organizations for data exfiltration and destruction, dated 22 Mar 2022
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- DEV-0537 criminal actor targeting organizations for data exfiltration and destruction, read 16 Nov 2026
Last reviewed 16 Nov 2026.