Microsoft (2023): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Microsoft disclosed the incident on 18 Sep 2023. What was exposed, as the sources state it: Microsoft stated that data in an internal storage account included backups of two former employees' workstation profiles and internal Microsoft Teams messages of those employees; it stated no customer data was exposed.
Open the ledger · Report a correction
- Disclosed
- 18 Sep 2023
- Incident window
- not public
- Cloud or provider
- Microsoft Azure
- What was exposed
- Microsoft stated that data in an internal storage account included backups of two former employees' workstation profiles and internal Microsoft Teams messages of those employees; it stated no customer data was exposed.
- How access was gained
- Microsoft stated an employee shared a URL for a blob store in a public GitHub repository, and the URL included an overly-permissive Shared Access Signature token for an internal storage account.
- Access path
- Leaked access keys and secrets; also Over-permissioned identities
- Kind of control that addresses it
- Issue storage access tokens with narrow scope and short expiry, and scan public code repositories for them before and after publication
In the words of the source
“This URL included an overly-permissive Shared Access Signature (SAS) token for an internal storage account.” (provider post mortem, Microsoft mitigated exposure of internal information in a storage account due to overly-permissive SAS token)
Primary sources
- provider post mortem: Microsoft mitigated exposure of internal information in a storage account due to overly-permissive SAS token, dated 18 Sep 2023
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
- Microsoft mitigated exposure of internal information in a storage account due to overly-permissive SAS token, read 16 Nov 2026
Last reviewed 16 Nov 2026.