Article Complete
AIM
Microsoft under Scrutiny after 38TB Data Leaked via Azure Storage
Microsoft under Scrutiny after 38TB Data Leaked via Azure Storage

Microsoft under Scrutiny after 38TB Data Leaked via Azure Storage

In July 2020, a misconfigured link led to a leak of 38TB of sensitive Microsoft data

Published Updated

Key takeaways

  • 38TB of sensitive Microsoft data was leaked due to a misconfigured Azure storage link.
  • The breach was discovered by cloud security firm Wiz, nearly three years after the incident.
  • A Microsoft employee inadvertently shared a URL exposing sensitive data on GitHub.
  • The leak included personal employee information, passwords, and internal messages from Microsoft Teams.
  • Microsoft emphasized that no customer data was compromised during the incident.
5 min

Cloud security provider Wiz has discovered an incident that occurred in July 2020, where a misconfigured link inadvertently exposed approximately 38TB of sensitive Microsoft data. After nearly three years of this data being accessible, the security firm uncovered this issue while scanning the internet for exposed storage accounts.

The breach originated from a software repository hosted on Microsoft-owned GitHub, which provides open-source code and AI models. It was determined that a Microsoft employee had unintentionally shared the URL to a misconfigured Azure Blob storage bucket, which contained this vast amount of leaked information.

https://twitter.com/hillai/status/1703771673411871227

Wiz's report highlighted a concern related to the security of Shared Access Signature (SAS) tokens, emphasizing the need to limit their usage due to their inherent security risks. The report noted that these tokens are challenging to track, as Microsoft lacks a centralized method within the Azure portal for their management.

The exposed data included backups of personal information belonging to Microsoft employees, including passwords for various Microsoft services, secret keys, and an archive containing over 30,000 internal messages from 359 Microsoft employees, exchanged on the Microsoft Teams platform.

In response to the incident, the Microsoft Security Response Center (MSRC) issued an advisory on Monday, reassuring that no customer data had been exposed, and no other internal services were compromised as a result of this breach.

The exposure of this data was attributed to the use of an excessively permissive Shared Access Signature (SAS) token, which granted full control over the shared files. Wiz researchers described this Azure feature as posing challenges in terms of monitoring and revoking access, highlighting the need for enhanced security measures in this regard.

Membership

Stay ahead with AI insights.

Unlimited access to premium articles, exclusive analysis, and the stories shaping India's AI economy.

Subscribe now

AIM Americas

1190 Miraloma Way Suite P, Sunnyvale, CA 94085

AIM India

1st Floor, Sakti Statesman, Bellandur, Bengaluru – 560103

© 2026 AIM. All rights reserved.