The MSA Key Leak: Why Your "Double Key" Wasn't a Deadbolt

Storm-0558 stole the stamp that signs identity tokens. Double Key Encryption releases its key to any valid token, so it protects files in Microsoft's storage, but not against the identity provider that issues the tokens.
We’ve all spent time dissecting the post-mortem of the Microsoft MSA signing key heist (Storm-0558). It’s one of those incidents that remains relevant for architectural teams because it didn’t just break a lock—it forged the master blueprint for the entire security desk.
Looking back at the impact assessments, I keep hearing one claim: even Double Key Encryption (DKE) was potentially compromised.
At first glance, that feels like a stretch. The whole point of DKE is that we hold one of the two keys. We have the second key on-premises, tucked away in our network, accessible only via our own non-Microsoft VPN. If Microsoft loses their half of the puzzle, the maths says our data should still be a brick.
But after digging into the mechanics of the “Identity Pivot,” the reality is a bit more sobering. Here is why DKE wasn’t the “get out of jail free” card many assumed.
The Identity Crisis at the Security Desk
Think of DKE as a high-security vault that requires two separate physical keys held by two different people.
To get your document open, you first have to visit the Security Desk (the Identity Provider). You show your ID, and the clerk hands you a “Permission Slip” (a signed JWT token). You then take that slip to the Key Master (our on-premises DKE service).
The Key Master doesn’t know you personally; his only job is to look at the Permission Slip, verify the Clerk’s signature, and—if it looks authentic—hand you the second key.
The encryption maths here is still perfect. The problem is that Storm-0558 stole a signature stamp from the consumer desk, and a validation flaw let enterprise services accept it as the Clerk’s.1
The attackers didn’t need to pick the lock on our vault. They could stamp their own Permission Slips for any user they wanted and walk up to our Key Master. If he trusted that stamp, he would look at the “valid” signature and, as designed, hand over the keys. Microsoft’s reference DKE service fetches its signing keys from the shared common endpoint, the list that also carried the stolen key.23
Why the Network Perimeter Didn’t Stop It
I’ve heard the argument: “But the attacker isn’t on our network. They can’t even see the Key Master!”
A non-Microsoft VPN and a hidden listener provide excellent network-level security, but they don’t solve for a total collapse of the Chain of Trust. If an attacker uses a forged token to access a user’s Exchange Online, they are already “authenticated” in the eyes of the M365 ecosystem. If they manage to compromise an endpoint that is already connected to the VPN—or leverage a persistent session on a hybrid-joined device—they are effectively standing at the Key Master’s window inside our house.
The Architect’s Takeaway
This incident highlights a critical distinction we have to maintain in our security models: Data Privacy is not the same as Identity Integrity.
DKE keeps files unreadable in Microsoft’s storage. It was never designed to protect against the Identity Provider (IdP) itself, whether compromised or compelled, and Microsoft runs that IdP.
If the foundation of your trust (the signing key) is gone, the walls you build on top of it—no matter how many keys you use—are standing on sand.
The Lesson: We can’t view encryption in a vacuum. A “Double Key” is only as secure as the “Single Identity” used to authorise its release. Two controls help. Validate tokens against your tenant’s own metadata endpoint, not the common one. And make the network path part of the check: Office doesn’t send a client certificate the Key Master could verify.4 Neither takes Microsoft out of the chain.
Microsoft Security Response Center, Microsoft mitigates China-based threat actor Storm-0558 targeting of customer email, updated 6 September 2023 with the investigation results. ↩︎
Wiz Research, Compromised Microsoft Key: More Impactful Than We Thought, July 2023. Microsoft called parts of it speculative. ↩︎
Azure-Samples, DoubleKeyEncryptionService, appsettings.json:
"Authority": "https://login.microsoftonline.com/common/v2.0"since the first version in 2019. The issuer check is a string comparison; nothing ties a signing key to the tenant. I know of no public evidence that a DKE service was attacked this way. ↩︎Microsoft Learn, Double Key Encryption FAQ, on mutual TLS with Office desktop apps. ↩︎