# Define the supported post-quantum certificate scope in AD CS > Use Post-Quantum Cryptography in AD CS overview - Windows Server to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/define-supported-pqc-certificate-scope-in-ad-cs/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:14:14+00:00 - Modified: 2026-08-27T12:58:59+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, IT, Microsoft 365 & Identity - Reading time: 3 minutes ## What you need to know Use Post-Quantum Cryptography in AD CS overview - Windows Server to review this narrow operational decision without extending the source beyond its stated scope. ## Potentially affected Teams, systems, services, or facilities within the stated scope of Post-Quantum Cryptography in AD CS overview - Windows Server ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: Define the supported post-quantum certificate scope in AD CS. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Post-Quantum Cryptography in AD CS overview – Windows Server](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/post-quantum-cryptography-overview) from Microsoft supports the following bounded statements: - AD CS can issue and manage certificates using algorithms intended to resist quantum-capable attacks. The research record locates this support at Opening overview. - The current documented AD CS post-quantum algorithm is ML-DSA, with platform and certificate-format requirements. The research record locates this support at Opening overview; sections: PQC algorithms supported; Platform requirements. Only the traced statements above are asserted as source facts. Apply the review to certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles after confirming that the source and deployed context match. ## What the source does not establish Do not infer application or protocol support from CA support; validate every relying party. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at Opening overview, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Opening overview; sections: PQC algorithms supported; Platform requirements, which observable configuration, record, or test can confirm applicability here? - What inventory proves which parts of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles are in and out of scope? - Which condition in Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities must be healthy before evidence is trustworthy? - What result would disprove the working assumption and return the issue to the owner? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, observed and expected states, owner, and reason for deviation. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## Verification and evidence Keep the source locations Opening overview; Opening overview; sections: PQC algorithms supported; Platform requirements adjacent to the sanitized artifacts used for comparison. Prefer CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks, with enough identity and timing data for an independent recheck. Preserve both successful and failed observations, along with approval and rollback evidence. Avoid uncontrolled production experiments. Assign an expiry or event-driven recheck so the conclusion is not treated as permanent. ## Official references - [Post-Quantum Cryptography in AD CS overview – Windows Server](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/post-quantum-cryptography-overview) — Microsoft ## Primary reference - Name: Post-Quantum Cryptography in AD CS overview - Windows Server - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/post-quantum-cryptography-overview - Source publication date: 2026-05-12 ## Citation and use Preferred citation: “Define the supported post-quantum certificate scope in AD CS,” DSE Security, https://update.dsesecurity.com/updates/define-supported-pqc-certificate-scope-in-ad-cs/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.