Skip to content
Cloud Security Breaches

Microsoft (2020): what the sources say about the cloud incident

Microsoft disclosed the incident on 22 Jan 2020. The ledger reads the access path as public storage, databases and services. The cloud or provider involved: Microsoft Azure. Every field rests on the primary sources listed below. Fields no primary source states read not public.

Open the ledger · Report a correction

Disclosed
22 Jan 2020
Incident window
December 5, 2019 (network security group change) to December 31, 2019 (remediation)
Cloud or provider
Microsoft Azure
What was exposed
An internal customer support database used for support case analytics. The post says most customers did not have personally identifiable information exposed, that records are redacted with automated tools, and that some data may have remained unredacted, for example an email address written in a non-standard format. Counts: not public.
How access was gained
The post says a change made to the database's network security group on December 5, 2019 contained misconfigured security rules that enabled exposure of the data. It says the investigation found no malicious use, and that the issue was specific to an internal database and does not represent an exposure of the company's commercial cloud services.
Access path
Public storage, databases and services
Kind of control that addresses it
continuously check network security rules on data stores for rules that allow unrestricted inbound access, and alert on rule changes

In the words of the source

“Our investigation has determined that a change made to the database’s network security group on December 5, 2019 contained misconfigured security rules that enabled exposure of the data.” (provider post mortem, Access Misconfiguration for Customer Support Database (Microsoft Security Response Center))

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. Access Misconfiguration for Customer Support Database (Microsoft Security Response Center), read 16 Nov 2026

Last reviewed 16 Nov 2026.