Blog Post

Microsoft Security Community Blog
5 MIN READ

Preparing for a Post-Quantum Future with TLS in Windows

AabhaThipsay's avatar
AabhaThipsay
Icon for Microsoft rankMicrosoft
Nov 17, 2026

Begin protecting long-lived data and preparing your certificate ecosystem with new post-quantum TLS capabilities in Windows.

The post-quantum cryptography (PQC) transition has already begun. A sufficiently powerful quantum computer could eventually compromise the public-key cryptography widely used to secure data and communications today. But organizations do not need to wait for that future to arrive before the risk becomes relevant. Encrypted traffic can be collected now and potentially decrypted later, while replacing cryptography across applications, infrastructure, and identity will take years.  

Windows is helping organizations take a practical first step. Earlier this year, we introduced post-quantum hybrid key exchange in the Windows Transport Layer Security (TLS) stack. With the October 2026 security update, Windows expands that foundation with pure post-quantum key exchange and authentication. Support in Windows 11 24H2 and later, as well as Windows Server 2025 helps organizations begin addressing risks to long-lived data while preparing certificate infrastructure and applications for a broader post-quantum transition.  

The two parts of the TLS transition  

TLS is foundational to secure communications across websites, applications, and services. Its public-key cryptography serves two critical functions: key exchange, which helps protect the confidentiality of a connection, and authentication, which helps establish trust in the peer you're communicating with. Both need to evolve for a post-quantum future, but the transition is different for each. 

Start by protecting today's data from future decryption 

Key exchange is where the risk is more immediate. A threat actor doesn't need a quantum computer today to create a future problem. The collection of encrypted traffic today for potential decryption in the future is known as a harvest-now, decrypt-later (HNDL) attack. That makes post-quantum key exchange an important place to start for sensitive data that needs to remain confidential well into the future. 

Prepare the certificate ecosystem for post-quantum authentication 

Authentication requires a broader ecosystem transition. Certificates and digital signatures help establish that you're connecting to the peer you intended to reach. Today, that trust commonly depends on quantum-vulnerable public-key algorithms that will also need to transition over time. 

For authentication, the challenge is preparing the certificate and Public Key Infrastructure (PKI) ecosystem before post-quantum authentication is needed at scale. Organizations need to map certificate dependencies, modernize PKI and certificate lifecycle processes, and determine where post-quantum authentication fits in their environments. 

Different authentication scenarios may ultimately require different approaches. X.509 certificates using ML-DSA provide a path for organizations to begin evaluating post-quantum authentication in enterprise PKI and service-to-service environments. For the Web PKI, larger post-quantum signatures can create performance challenges at scale. The Internet Engineering Task Force (IETF) is developing Merkle Tree Certificates (MTC) as a new certificate construction intended to reduce this overhead while preserving security properties comparable to today's X.509 and Certificate Transparency model. Microsoft is exploring MTC support in Windows alongside X.509-based PQC capabilities as we prepare Windows for the evolving post-quantum authentication ecosystem. 

Together, post-quantum key exchange using ML-KEM and authentication using ML-DSA certificates allow organizations to begin the transition of both key exchange and authentication in Windows. 

Start your post-quantum TLS transition 

Begin with hybrid post-quantum key exchange 

We recommend starting with hybrid post-quantum key exchange, which combines classical and post-quantum cryptography. Where specific requirements call for pure PQC, organizations can also use pure ML-KEM key exchange. 

Assess your authentication readiness 

In parallel, assess readiness for post-quantum TLS authentication across the certificate ecosystem. Applications, PKI infrastructure, and systems that issue, validate, or depend on certificates may also need to adapt. 

To get started, see these Microsoft Learn resources

TLS is one step in a broader Windows transition 

Post-quantum TLS is an important milestone, and it’s where most organizations will start.  But TLS is one piece of a larger transition. The same cryptography protects data, identities, and device trust across Windows, and we're working on all of it together. 

That work starts with a crypto-agile foundation. We're adding additional post-quantum algorithms to Cryptography Next Generation (CNG) as global standards evolve and pairing them with hybrid and composite approaches designed to make it easier to adapt as algorithms evolve. And because not every application relies on TLS, Hybrid Public Key Encryption (HPKE) extends that protection to applications beyond it. 

On top of that foundation, we're working with standards bodies, silicon providers, and partners to bring Wi-Fi, and IPsec to post-quantum, with Wi-Fi already underway. We're also evolving identity and PKI end to end, across Active Directory Certificate Services (ADCS), Windows Hello, Kerberos, and smart cards. ADCS already supports ML-DSA and will add composite PQ certificates, so classical and post-quantum trust can run side by side during the transition. 

The same shift reaches the chain of trust beneath Windows. Signing for software, Windows Update, and servicing is moving toward post-quantum signatures, with firmware and Secure Boot advancing alongside UEFI, silicon, and OEM partners. Remote Desktop Protocol (RDP) already supports TLS 1.3 hybrid key exchange on supported configurations, and work continues across data protection, TPM, Pluton, measurement, and attestation.

Looking ahead 

The post-quantum transition will take time. The important step is to begin. Start by identifying data that must remain confidential over the long term, deploy hybrid post-quantum TLS key exchange, and map the applications and certificate infrastructure that will need to evolve. 

TLS is an important step, but it’s only the beginning. Windows is building a crypto-agile foundation across the platform and working with the industry to help organizations adopt post-quantum protection as standards and ecosystems mature. 

Learn More 

To learn more about Post-quantum readiness and Windows security at Ignite, check out these resources: 

  • Check out the new Windows Security Guide to better understand how we are thinking about security across the platform 

For more on post-quantum cryptography, visit our other resources:  

Updated Nov 11, 2026
Version 1.0
No CommentsBe the first to comment