Microsoft Commits Core Platforms to Post-Quantum Cryptography by 2029

Microsoft's update integrates PQC into the Secure Future Initiative with measurable milestones for TLS 1.3 adoption, crypto-agile ciphertext formats, and trust chain upgrades including code signing and certificate issuance. The shift targets harvest-now-decrypt-later collection risks and responds to recent Google and Caltech research showing practical Shor's algorithm variants at 10,000 reconfigurable qubits. Contract records and procurement databases show parallel DoD and civilian agency RFPs now embedding PQC requirements, consistent with the Trump executive order's hard deadlines for high-value assets. Official statements emphasize engineering discipline while independent analysis of NIST SP 800-38 series updates reveals earlier algorithm deprecation schedules than public timelines admit. Google's March Chrome PQC experiment and Cloudflare's 2029 infrastructure commitment form a vendor pattern where the largest platforms force downstream enterprise roadmaps. Crypto-agility mandates remove hard-coded assumptions but require persistent metadata that many legacy systems lack, creating migration bottlenecks not addressed in the announcement. Operational impact centers on Windows Update pipelines and Azure Key Vault; enterprises must audit stored ciphertext within 18 months or face incompatibility during forced upgrades. Next indicators will appear in Microsoft job postings for PQC implementation engineers and revised FedRAMP baselines.