Security

Quantum-Safe Security: Microsoft Targets 2029

3 min read

Summary

Microsoft is accelerating its quantum-safe security roadmap and now aims to transition critical products and services to post-quantum cryptography by 2029. The update matters because IT teams need to start cryptographic inventory, crypto-agility planning, and TLS 1.3 modernization sooner as the risk timeline for quantum attacks moves closer.

Need help with Security?Talk to an Expert

Introduction

Microsoft has moved up its quantum-safe security timeline, signaling that post-quantum cryptography (PQC) is no longer a distant planning exercise. For IT and security leaders, this is an important shift: preparation now needs to start as a multi-year modernization effort, not as a future compliance project.

Microsoft says it is accelerating the Quantum Safe Program (QSP) with a goal of transitioning critical products and services to PQC by 2029. The company is also adding PQC requirements into its Secure Future Initiative, giving the work clearer ownership, milestones, and engineering accountability.

What’s new

Microsoft is bringing the timeline forward

  • Microsoft now believes cryptographically relevant quantum computers may arrive sooner than previously expected.
  • The company is targeting 2029 for critical product and service transition to PQC.
  • This aligns with growing government pressure to adopt quantum-safe cryptography earlier, especially for high-risk systems.

Three priority areas

  • Network cryptography: Microsoft highlights TLS 1.3 as the baseline for future hybrid and post-quantum key exchange.
  • Crypto-agility for data at rest: Organizations should make cryptographic settings configurable, standardize key management, and remove hard-coded algorithms.
  • Trust chain modernization: Code signing, certificate issuance, key protection, and update pipelines need to be updated for future PQC adoption.

Inventory-first approach

Microsoft emphasizes that the biggest challenge is not choosing algorithms. It is discovering where cryptography already exists across apps, identities, certificates, hardware, and legacy infrastructure.

Why this matters for IT administrators

For most organizations, the immediate impact is operational. Security and infrastructure teams need visibility into cryptographic dependencies before they can plan a safe migration path.

This also reinforces several near-term priorities:

  • Reduce legacy protocol use where possible
  • Standardize on TLS 1.3 across client and server systems
  • Review certificate and signing processes
  • Identify long-lived sensitive data at risk from “harvest now, decrypt later” attacks

Even before PQC standards are fully implemented everywhere, this work can uncover existing security gaps and improve lifecycle management today.

  • Assign ownership: Define who leads the post-quantum transition across security, identity, app, and infrastructure teams.
  • Build a cryptographic inventory: Track where algorithms, certificates, keys, and protocols are used.
  • Design for crypto-agility: Ensure new systems can swap cryptographic methods without major redesign.
  • Modernize protocols now: Make TLS 1.3 the default baseline where supported.
  • Prioritize high-value data: Focus first on sensitive data that must remain confidential for many years.

Microsoft is expected to share more technical guidance as this work progresses. For administrators, the message is clear: start discovery and modernization now to avoid a rushed and costly transition later.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

post-quantum cryptographyquantum-safe securityTLS 1.3crypto-agilityMicrosoft Security

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.