RESOURCE

Microsoft amorce le déploiement de l'échange de clés TLS hybride post-quantique (X25519MLKEM768) sur Azure App Service et Azure Functions

Le 9 novembre 2026, Microsoft a annoncé le déploiement progressif du groupe d'échange de clés hybride TLS 1.3 X25519MLKEM768 (X25519 classique et ML-KEM-768 normalisé par le NIST) pour les connexions entrantes vers Azure App Service et Azure Functions dans Azure public. Aucune modification d'application, de paramètre ou de certificat n'est requise; les clients qui ne prennent pas en charge le groupe reviennent à l'échange de clés classique.

Fabric Networks

PUBLISHED

November 9, 2026

SOURCE

Microsoft Azure App Service

OUR TAKE BY

Fabric Networks Inc., Calgary. Reviewed against the primary source linked below.

Want to go deeper?

Start with a conversation about your cryptographic posture.

On November 9, 2026 the Azure App Service team announced that Azure App Service and Azure Functions have begun a phased rollout of the TLS 1.3 hybrid key exchange group X25519MLKEM768. The group combines the classical X25519 elliptic curve exchange with ML-KEM-768, the post-quantum key encapsulation mechanism NIST standardized in FIPS 203, so the session key depends on both.

The rollout covers inbound TLS connections to Windows and Linux apps on App Service infrastructure in public Azure, across App Service and Functions hosting plans, and will expand region by region later this year. It is platform managed: no code change, no application setting, no change to minimum TLS version or cipher suites, and no post-quantum certificate. Clients that support the group negotiate it automatically; everyone else falls back to classical key exchange. Microsoft is explicit about the limits: Functions on Azure Container Apps are excluded, the internal front end to worker connection is out of scope, and only key exchange changes, not certificates or signatures.

For a Canadian operator the practical effect is that a growing share of the web traffic terminating in Azure is now protected against harvest now, decrypt later on the key exchange, whether or not the application owner did anything.

Our take

The hardware stays, the keys change. Microsoft just did that for every App Service customer at the front door, and most of them will never know. That is the pattern to copy on your own estate: hybrid key exchange first, where the traffic is, without waiting for a certificate ecosystem. The catch is the fine print, and it is the same fine print on your network: the hop behind the front end is still classical. A cryptographic inventory that shows which hops negotiate X25519MLKEM768 and which still do RSA is worth more than any vendor press release. Observed on the wire, not asserted on a data sheet.