Security

Storm-2949 Cloud Breach: Entra ID to Azure Attack

3 min read

Summary

Microsoft detailed how Storm-2949 turned a socially engineered Microsoft Entra ID compromise into broad data theft across Microsoft 365 and Azure. The case highlights how identity attacks can escalate quickly through legitimate cloud management features, making stronger MFA controls, monitoring, and cross-platform detections critical for defenders.

Need help with Security?Talk to an Expert

Introduction

Microsoft has published a deep dive into Storm-2949, a threat actor that transformed a single compromised identity into a cloud-wide breach spanning Microsoft 365 and Azure. For IT and security teams, this is an important reminder that identity is now the primary attack surface in cloud environments.

Rather than relying on traditional malware, the attacker abused legitimate administrative features, blended into normal cloud activity, and focused on large-scale data exfiltration.

What happened

Microsoft says the campaign unfolded in two major phases:

  • Targeted identity compromise through social engineering and abuse of the Self-Service Password Reset (SSPR) process
  • Cloud infrastructure compromise across Microsoft 365, Microsoft Entra ID, and Azure resources

Key attack steps

  • Attackers reportedly impersonated IT support and convinced users to approve MFA prompts during fraudulent password reset activity.
  • After resetting passwords, they removed existing authentication methods and enrolled Microsoft Authenticator on attacker-controlled devices for persistence.
  • They used Microsoft Graph API to enumerate users, roles, applications, and service principals.
  • In Microsoft 365, they accessed and exfiltrated files from OneDrive and SharePoint, including sensitive IT documentation.
  • In Azure, they leveraged compromised identities with privileged RBAC assignments to expand access into production environments.
  • Microsoft also observed attempts to access App Service, Key Vault, Storage, SQL, and Virtual Machines, enabling broader data theft and lateral movement.

Why this matters for administrators

This incident shows how quickly a compromised Entra ID account can become a full cloud control-plane problem. If attackers gain access to privileged identities, they can use native tools and APIs to move across SaaS, PaaS, and IaaS resources with fewer obvious indicators of compromise.

For Microsoft 365 and Azure admins, the biggest takeaway is that identity security, privilege management, and cross-environment visibility must be treated as one defense problem—not separate silos.

Organizations should review Microsoft’s mitigation guidance and take immediate action in a few areas:

  • Harden SSPR and MFA processes to reduce social engineering exposure
  • Review privileged role assignments in Entra ID and Azure RBAC
  • Audit authentication method changes and suspicious password reset activity
  • Monitor Graph API, OneDrive, and SharePoint activity for unusual discovery or bulk downloads
  • Protect service principals, Key Vault, storage accounts, and VMs with least privilege and stronger monitoring
  • Use behavior-based detection tools such as Microsoft Defender XDR to correlate identity, cloud, and endpoint signals

Bottom line

Storm-2949 demonstrates that modern cloud breaches often begin with identity manipulation, not malware. Security teams should use this case as a prompt to strengthen identity protections, validate privileged access paths, and improve detection coverage across Microsoft 365, Entra ID, and Azure.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Storm-2949Microsoft Entra IDAzure securityMicrosoft 365identity attack

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.