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

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

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.

- **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](/access-paths/cross-tenant/)
- **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)](https://web.archive.org/web/2021/https://msrc-blog.microsoft.com/2021/08/27/update-on-vulnerability-in-the-azure-cosmos-db-jupyter-notebook-feature/))

## Primary sources

- provider post mortem: [Update on the vulnerability in the Azure Cosmos DB Jupyter Notebook Feature (archived copy)](https://web.archive.org/web/2021/https://msrc-blog.microsoft.com/2021/08/27/update-on-vulnerability-in-the-azure-cosmos-db-jupyter-notebook-feature/), dated 27 Aug 2021

If a field is wrong or a newer primary source exists, [write to the editor](mailto:editor@cloudsecuritybreaches.com?subject=Correction%3A%20Microsoft%20(Azure%20Cosmos%20DB)%20(azure-cosmosdb-chaosdb-2021)) with the entry name in the subject.

## Related pages

- [Codecov 2021: leaked access keys and secrets](/incidents/codecov-2021/)
- [Mimecast 2021: solarwinds certificate](/incidents/mimecast-solarwinds-certificate-2021/)
- [SkyMed International, Inc. 2020: ftc](/incidents/skymed-ftc-2020/)

## Sources

- Update on the vulnerability in the Azure Cosmos DB Jupyter Notebook Feature (archived copy): https://web.archive.org/web/2021/https://msrc-blog.microsoft.com/2021/08/27/update-on-vulnerability-in-the-azure-cosmos-db-jupyter-notebook-feature/ (read 16 Nov 2026)

Last reviewed 16 Nov 2026. Canonical: https://cloudsecuritybreaches.com/incidents/azure-cosmosdb-chaosdb-2021/
