What's Changing
Google's security team publicly warned in late 2024 that cryptographically relevant quantum computers (CRQCs) could break RSA-2048 and elliptic-curve cryptography within a realistic timeframe — estimates now range from 5 to 15 years, with some threat intelligence teams collapsing that window further. Simultaneously, NIST finalized its first set of post-quantum cryptography (PQC) standards in August 2024 — FIPS 203 (ML-KEM), FIPS 204 (ML-DSA), and FIPS 205 (SLH-DSA) — giving the industry an actual migration target for the first time.
Microsoft has acknowledged this shift and is actively updating its cryptographic posture across Microsoft 365, Azure, and the Intune management stack. The company's Post-Quantum Cryptography (PQC) migration strategy confirms that legacy TLS cipher suites and RSA-based key exchange are on the deprecation roadmap. This is not hypothetical planning — it directly affects how your managed endpoints negotiate connections with Intune, Exchange Online, SharePoint, and Entra ID today.
Who's Affected & When
Every Microsoft 365 tenant is in scope. License tier is irrelevant — this is a cryptographic infrastructure problem, not a feature tier problem. Here's the practical breakdown:
- All tenants immediately: The 'store now, decrypt later' (SNDL) threat is active right now. Adversaries — particularly nation-state actors — are harvesting encrypted traffic today with the intent to decrypt it once quantum capability matures. If your organization handles data with a sensitivity horizon longer than 5-10 years (healthcare records, legal, defense supply chain, financial), you are already in the threat window.
- TLS 1.0/1.1 deprecation (already enforced): Microsoft completed this across M365 services. If you still have legacy devices negotiating these protocols through Intune-managed conditional access, those sessions are either being blocked or falling back insecurely.
- TLS 1.3 with hybrid PQC: Microsoft began testing X25519Kyber768 hybrid key exchange in Edge and Windows in 2024. This is currently opt-in via preview but will become default on a rolling basis through 2025-2026.
- Intune MDM channel: The Intune management channel relies on HTTPS with RSA/ECDH. Microsoft has not published a hard cutover date for PQC on the MDM endpoint, but the expectation from the PQC strategy document is that Azure services — including Intune's backend — will be PQC-capable by 2026-2027.
What This Means for Your Environment
The practical risk splits into two categories: immediate operational gaps and strategic data exposure.
Immediate Operational Gaps
Run this against your Intune-managed Windows fleet right now. You need to know which cipher suites your endpoints are actually negotiating:
# Check enabled TLS cipher suites on a managed endpoint
Get-TlsCipherSuite | Select-Object Name, Exchange, Cipher, Hash | Format-Table -AutoSize
# Flag any suites using RSA key exchange (vulnerable to quantum harvest)
Get-TlsCipherSuite | Where-Object { $_.Exchange -eq 'RSA' } | Select-Object Name
If you see TLS_RSA_WITH_AES_256_CBC_SHA or similar RSA key exchange suites still enabled, those sessions provide zero forward secrecy and are prime SNDL candidates. Disable them via Intune Settings Catalog or Group Policy — don't wait.
To enforce a hardened cipher suite order via Intune Settings Catalog, push the following SSL Cipher Suite Order configuration. The Graph API payload looks like this:
{
"@odata.type": "#microsoft.graph.windows10CustomConfiguration",
"displayName": "PQC-Ready Cipher Suite Hardening",
"omaSettings": [
{
"@odata.type": "#microsoft.graph.omaSettingString",
"displayName": "SSL Cipher Suite Order",
"omaUri": "./Device/Vendor/MSFT/Policy/Config/Cryptography/TLSCipherSuites",
"value": "TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256"
}
]
}
This prioritizes TLS 1.3 suites (which mandate ephemeral key exchange and provide forward secrecy) and pushes ECDHE-based TLS 1.2 suites above any RSA key exchange fallbacks.
Strategic Data Exposure
S/MIME and Microsoft Purview Message Encryption (OME) configurations using RSA-2048 keys are your most exposed surface. Emails encrypted today with RSA keys and stored by a capable adversary are a future liability. Review your Purview encryption configuration and assess key lengths and rotation schedules. RSA-4096 buys time but is not a permanent solution — it's a bridge.
BitLocker recovery keys escrowed in Intune are protected in transit and at rest by Microsoft's infrastructure encryption. That's currently RSA-based at the service layer. This is on Microsoft's migration path, but you should still validate your key rotation cadence is active — stale recovery keys stored long-term increase exposure duration.
Action Items
- Audit cipher suites across your managed fleet using the PowerShell snippet above. Generate a report before your next security review.
- Deploy cipher suite hardening via Intune using the OMA-URI payload provided. Target a pilot ring first — some legacy line-of-business apps break when RSA key exchange is removed.
- Review S/MIME certificate infrastructure. If you're issuing internal certs with RSA-2048, start planning a migration to RSA-4096 or ECDSA P-384 as an interim step while PQC certificate standards mature.
- Enable TLS 1.3 enforcement on all Intune-managed browsers (Edge policy:
SSLVersionMin= TLS 1.2 minimum, but validate TLS 1.3 is negotiating by default). Check via Edge'sedge://versionandedge://net-internals/#security. - Classify data by sensitivity horizon. Work with your CISO or DPO to identify data types that must remain confidential beyond 2030. That data needs protection decisions made now, not when quantum capability arrives.
- Track Microsoft's PQC migration progress via the official PQC strategy page and subscribe to the Microsoft 365 Message Center for deprecation notices on legacy cryptographic algorithms.
- Do not wait for Intune to force this. The management plane will be updated by Microsoft, but your data plane — emails, files, VPN tunnels, API calls from managed devices — depends on configurations you control today.
The quantum threat is not a future IT problem that lands on someone else's watch. The 'store now, decrypt later' model means the attack surface is accumulating right now, in your mail flow logs, your SharePoint audit trails, and your Intune device telemetry. Hardening cipher suites and auditing your encryption posture this quarter is the minimum viable response.
