Skip to content
Cloud Security Breaches

Microsoft (Azure Cosmos DB) (2021): what the sources say about the cloud incident

Microsoft (Azure Cosmos DB) disclosed the incident on 27 Aug 2021. What was exposed, as the sources state it: The post-mortem says primary read-write keys of a subset of Azure Cosmos DB customers could be reached, customers were notified to regenerate keys, and no customer data was accessed by third parties or security researchers.

Open the ledger · Report a correction

Disclosed
27 Aug 2021
Incident window
Researcher activity between 2021-08-07 and 2021-08-13
Cloud or provider
Microsoft Azure
What was exposed
The post-mortem says primary read-write keys of a subset of Azure Cosmos DB customers could be reached, customers were notified to regenerate keys, and no customer data was accessed by third parties or security researchers.
How access was gained
The post-mortem says a vulnerability in the Azure Cosmos DB Jupyter Notebook feature could allow a user to gain access to another customer's resources by using the account's primary read-write key.
Access path
Cross-tenant access
Kind of control that addresses it
use role-based access control and network restrictions instead of account-wide keys, and rotate account keys on a schedule

In the words of the source

“a vulnerability in the Azure Cosmos DB Jupyter Notebook feature that could potentially allow a user to gain access to another customer’s resources by using the account’s primary read-write key.” (provider post mortem, Update on the vulnerability in the Azure Cosmos DB Jupyter Notebook Feature (archived copy))

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. Update on the vulnerability in the Azure Cosmos DB Jupyter Notebook Feature (archived copy), read 16 Nov 2026

Last reviewed 16 Nov 2026.