Microsoft is drawing a line in the sand for quantum threats. On June 30, 2026, Azure CTO Mark Russinovich announced that the company is accelerating its Quantum Safe Program, setting a 2029 deadline to migrate all its products and services to post-quantum cryptography (PQC). The move, disclosed in a detailed blog post, folds every quantum-safe initiative under a unified, time-bound strategy—and sends a loud signal to enterprises, governments, and rivals that the era of quantum-vulnerable encryption is ending.

“Quantum computing is not a distant threat,” Russinovich wrote. “Adversaries are already stealing encrypted data to decrypt later. We must act now to protect our customers and the entire ecosystem. By 2029, Microsoft will be quantum-safe.”

The Quantum Threat Is Real—and It Has a Shelf Life

The peril is no longer theoretical. Shor’s algorithm, if run on a sufficiently powerful quantum computer, can crack RSA, ECDSA, and Diffie-Hellman in hours—protocols that underpin virtually all internet security, digital signatures, and VPNs today. Estimates vary, but a cryptographically relevant quantum computer may emerge in the next 10–15 years. The bigger danger, however, is “harvest now, decrypt later” attacks: adversaries intercept and store encrypted traffic now, intending to break it once quantum machines mature. That makes today’s secrets—government communications, financial records, intellectual property—subject to a retroactive breach.

Against this backdrop, the U.S. National Security Agency (NSA) and CISA have been urging organizations to begin the transition to post-quantum cryptography. NIST finalized its first batch of PQC standards in 2024, picking CRYSTALS-Kyber for key encapsulation and CRYSTALS-Dilithium plus SPHINCS+ for digital signatures. With standards in hand, the industry’s pace has quickened—but Microsoft’s 2029 target is among the most ambitious public commitments to date.

Microsoft’s Quantum Safe Program: What’s Changing

For years, Microsoft’s quantum-safe work was scattered across research labs, Azure Engineering, and the Windows cryptography team. The new program consolidates these efforts and gives them a hard deadline. Russinovich explained that the goal is to make every Microsoft product—Windows, Azure, Office 365, LinkedIn, Xbox, and even the IoT platforms—resistant to quantum attacks by 2029.

The plan rests on three pillars:
- Cryptographic agility: All services and clients must be able to swap cryptographic algorithms without a complete re-architecture. This means protocols like TLS 1.3 and SSH must support PQC ciphersuites gracefully.
- Hybrid-by-default transition: For the near term, Microsoft will deploy hybrid schemes that combine classical and PQC algorithms—for example, coupling X25519 with Kyber-768 in TLS key exchanges. This guards against flaws in new algorithms while ensuring backward compatibility.
- Full PQC enforcement: By 2029, new connections, code signatures, and data-at-rest encryption must rely solely on approved post-quantum algorithms. Older, quantum-vulnerable ciphers will be deprecated.

SymCrypt, the battle-tested cryptographic engine inside Windows and Azure, is the linchpin. Microsoft added PQC algorithm support to SymCrypt in 2023 and has been refining performance ever since. The 2029 timeline means that SymCrypt will ship with PQC as the default for all hash-based, symmetric, and asymmetric operations—a massive undertaking that touches everything from BitLocker to Windows Update signing.

Windows Users: What the 2029 Deadline Means

For the millions of Windows PCs powering homes and offices, the shift will be largely transparent—provided the hardware is capable. Future Windows releases (likely Windows 11 24H2 and beyond) will include quantum-safe TLS ciphersuites in the Secure Channel (Schannel) provider, which underpins HTTPS, RDP, and VPN connections. This means applications using the built-in Windows crypto stack will automatically negotiate quantum-resistant keys when connecting to Microsoft services or updated third-party servers.

Code signing will see the most visible change. Every Windows executable, driver, and script currently signed with RSA or ECDSA will need a PQC signature. Microsoft intends to dual-sign critical binaries with Dilithium by 2027, giving enterprises time to test validation logic. IT administrators should anticipate new Group Policy settings to enforce PQC for software installation and to block untrusted fallbacks.

On the developer front, the Windows Cryptography: Next Generation (CNG) API is gaining new algorithm identifiers—CRYPT_ALG_PQC_KYBER, CRYPT_ALG_PQC_DILITHIUM, etc.—enabling native, low-overhead access to PQC primitives. .NET’s System.Security.Cryptography namespace will similarly expand, and PowerShell will receive updated security cmdlets. Microsoft is also building tooling to scan local certificate stores and identify quantum-vulnerable credentials.

Azure and Enterprise Impact

Azure Active Directory, Key Vault, and SQL Database are among the first cloud services being retrofitted. Russinovich confirmed that Azure’s TLS termination points will offer Kyber-based ciphersuites in preview by mid-2027, with general availability planned before 2028. By 2029, every Azure service endpoint will reject classical-only handshakes by default, though customers can opt out during a transition window.

Hybrid scenarios—on-premises AD synchronized with Azure AD—pose a particular challenge. Microsoft plans to ship an updated Azure AD Connect agent that can perform quantum-safe certificate enrollment, ensuring sync traffic is protected. Enterprise customers with legacy domain controllers will need to upgrade to Windows Server 2025 or later to support the new protocols.

For data at rest, Azure Storage already supports customer-managed keys; Microsoft intends to offer PQC-protected key wrapping and unwrapping using Kyber-1024. SQL Database transparent data encryption (TDE) will add a PQC option, and Azure Confidential Computing enclaves will embed PQC attestation tokens. These changes will roll out incrementally, but the 2029 date imposes a firm deadline.

The Standards: Kyber, Dilithium, and Beyond

NIST’s PQC finalists were the result of a six-year global competition. Microsoft contributed actively to the process, co-authoring the FrodoKEM proposal and partnering with academia on performance optimization. The chosen algorithms:
- CRYSTALS-Kyber (FIPS 204): A lattice-based key encapsulation mechanism (KEM) suitable for TLS, SSH, and encrypted messaging. Kyber offers small ciphertexts but larger public keys than ECDH—Microsoft is mitigating the overhead with caching and pre-computation in SymCrypt.
- CRYSTALS-Dilithium (FIPS 205): A lattice-based signature scheme with moderate signature sizes. It replaces RSA-4096 and ECDSA for most use cases, though SPHINCS+ (FIPS 206) is available for stateless, hash-based signatures in niche scenarios.

Microsoft’s implementation passes the NIST Known Answer Tests and is being hardened against side-channel attacks. The company also participates in the Open Quantum Safe (OQS) project, releasing open-source libraries to help the broader ecosystem adopt PQC.

The Competitive Landscape and Regulatory Push

Microsoft’s 2029 deadline puts it ahead of many peers. Google has been experimenting with PQC in Chrome and internal TLS, but hasn’t set a public, company-wide completion date. Apple integrated Kyber into iMessage’s key exchange (PQ3 protocol) in 2024, yet its broader services roadmap remains opaque. The U.S. government’s own National Security Memorandum requires federal agencies to migrate by 2035—Microsoft’s self-imposed deadline is six years earlier, potentially forcing its government customers to accelerate as well.

The EU’s Cyber Resilience Act and the UK’s National Cyber Strategy are also pushing for quantum-ready infrastructure. By moving early, Microsoft positions its cloud and software as the natural choice for regulated industries that must demonstrate proactive security.

Challenges on the Road Ahead

The transition is not without friction. PQC algorithms demand larger keys and ciphertexts, which can strain bandwidth-constrained IoT devices and increase latency. Kyber-768 public keys are roughly 1.2 KB, compared to 32 bytes for Curve25519. Microsoft’s solution is to compress keys at the protocol layer and to batch renegotiations where possible.

Hybrid schemes double the cryptographic workload. In benchmarks, a hybrid X25519+Kyber TLS handshake can be 30–50% slower than a classical one, though with hardware acceleration (AES-NI, AVX-512) the gap narrows. Microsoft is working with chipmakers to bake lattice-based operations into future CPUs—a boon that may arrive just in time for the 2029 cutoff.

Backward compatibility also looms. Older Windows devices (pre-Windows 11 24H2) won’t support PQC natively and may need software shims or retire entirely. Microsoft plans a “last mile” support policy, but ultimately, quantum-safe communications will require modern hardware.

What Comes Next

Russinovich’s announcement is the starting gun, not the finish line. Over the next three years, CIOs and security teams should expect a steady drumbeat of previews, compliance toolkits, and migration guides. The message is clear: quantum threats are no longer a hypothetical—they are a deadline. By setting 2029, Microsoft hasn’t just made a promise; it has given every customer a ticking clock.

For Windows users, the path is straightforward: keep devices updated, pay attention to new cryptography settings, and prepare to retire legacy systems that can’t keep up. The internet’s cryptographic backbone is about to be reforged—and Microsoft intends to lead the charge.