{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
        "slug": "stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks",
        "url": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/"
        },
        "title": "Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks",
        "summary": "Use Configure certificate templates for ML-DSA in Windows Server to review this narrow operational decision without extending the source beyond its stated scope.",
        "format": {
            "slug": "explainer",
            "name": "Explainer"
        },
        "priority": {
            "slug": "advisory",
            "name": "Advisory"
        },
        "featured": false,
        "image": {
            "theme": "network-infrastructure",
            "label": "Networks & infrastructure",
            "alt": "Resilient network core with engineered blue and gold data paths.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
            "width": 2400,
            "height": 1350
        },
        "topics": [
            {
                "slug": "cybersecurity",
                "name": "Cybersecurity",
                "url": "https://update.dsesecurity.com/topic/cybersecurity/"
            },
            {
                "slug": "microsoft-365-identity",
                "name": "Microsoft 365 & Identity",
                "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
            },
            {
                "slug": "networks-infrastructure",
                "name": "Networks & Infrastructure",
                "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
            }
        ],
        "author": {
            "name": "DSE Security Editorial Team",
            "url": "https://update.dsesecurity.com/#editorial-team",
            "type": "Organization"
        },
        "publisher": {
            "name": "Detection Systems & Engineering",
            "url": "https://dsesecurity.com/"
        },
        "published_at": "2026-08-27T17:06:03+00:00",
        "modified_at": "2026-08-27T17:11:10+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 569,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Configure certificate templates for ML-DSA in 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.",
        "primary_source": {
            "name": "Configure certificate templates for ML-DSA in Windows Server",
            "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-ml-dsa-certificate-templates",
            "published_on": null,
            "authority": "Microsoft Learn"
        },
        "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
        "usage_info": "https://update.dsesecurity.com/usage/",
        "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
        "content_html": "<p>Frame this document as a source-led configuration and assurance check: Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.</p>\n<h2>Source fact:</h2>\n<p>The official <a href=\"https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-ml-dsa-certificate-templates\" target=\"_blank\" rel=\"noopener noreferrer\">Configure certificate templates for ML-DSA in Windows Server</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At Introduction below H1, Microsoft states: “This article describes how to configure Active Directory Certificate Services (AD CS) certificate templates to use Module-Lattice-Based Digital Signature Algorithm (ML-DSA) as the public key algorithm.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n<li>At Introduction below H1, Microsoft states: “After configuring certificate templates, users and computers with appropriate permissions can enroll for ML-DSA certificates.” The research record locates this support at <strong>Introduction below H1</strong>.</li>\n</ul>\n<p>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.</p>\n<h2>What the source does not establish</h2>\n<p>The cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities and the environment&#8217;s recorded constraints.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>Introduction below H1</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>Within certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, which versions, roles, and configuration states define the review population?</li>\n<li>Could Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities invalidate the test, hide a failure, or change applicability?</li>\n<li>Who owns the decision, and which observation requires stopping, escalation, or rollback?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>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.</p>\n<p>Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, while excluding secrets and sensitive personal or topology data from ordinary tickets.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>Introduction below H1</strong>; <strong>Introduction below H1</strong> to the observed environment. Useful domain evidence includes CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks; label every item with scope, timestamp, collector, and stable identifier.</p>\n<p>Label this evidence set <strong>DSE-20260827-083</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-ml-dsa-certificate-templates\" target=\"_blank\" rel=\"noopener noreferrer\">Configure certificate templates for ML-DSA in Windows Server</a> — Microsoft</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Configure certificate templates for ML-DSA in Windows Server from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article describes how to configure Active Directory Certificate Services (AD CS) certificate templates to use Module-Lattice-Based Digital Signature Algorithm (ML-DSA) as the public key algorithm.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “After configuring certificate templates, users and computers with appropriate permissions can enroll for ML-DSA certificates.” The research record locates this support at Introduction below H1.\n\nOnly 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.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWithin certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, which versions, roles, and configuration states define the review population?\nCould Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE 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.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nBuild a reproducible chain from Introduction below H1; Introduction below H1 to the observed environment. Useful domain evidence includes CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-083 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nConfigure certificate templates for ML-DSA in Windows Server — Microsoft",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Configure certificate templates for ML-DSA in Windows Server](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-ml-dsa-certificate-templates) from Microsoft supports the following bounded statements:\n\n- At Introduction below H1, Microsoft states: “This article describes how to configure Active Directory Certificate Services (AD CS) certificate templates to use Module-Lattice-Based Digital Signature Algorithm (ML-DSA) as the public key algorithm.” The research record locates this support at Introduction below H1.\n\n- At Introduction below H1, Microsoft states: “After configuring certificate templates, users and computers with appropriate permissions can enroll for ML-DSA certificates.” The research record locates this support at Introduction below H1.\n\nOnly 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.\n\n## What the source does not establish\n\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities and the environment’s recorded constraints.\n\n## Applicability questions\n\n- For source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\n\n- Within certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, which versions, roles, and configuration states define the review population?\n\n- Could Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities invalidate the test, hide a failure, or change applicability?\n\n- Who owns the decision, and which observation requires stopping, escalation, or rollback?\n\n## DSE recommendation:\n\nDSE 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.\n\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, while excluding secrets and sensitive personal or topology data from ordinary tickets.\n\n## Verification and evidence\n\nBuild a reproducible chain from Introduction below H1; Introduction below H1 to the observed environment. Useful domain evidence includes CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks; label every item with scope, timestamp, collector, and stable identifier.\n\nLabel this evidence set DSE-20260827-083 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\n\n## Official references\n\n- [Configure certificate templates for ML-DSA in Windows Server](https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-ml-dsa-certificate-templates) — Microsoft"
    },
    "json_ld": {
        "@context": "https://schema.org",
        "@graph": [
            {
                "@type": "Organization",
                "@id": "https://dsesecurity.com/#organization",
                "name": "Detection Systems & Engineering",
                "alternateName": "DSE Security",
                "url": "https://dsesecurity.com/",
                "logo": {
                    "@type": "ImageObject",
                    "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20"
                }
            },
            {
                "@type": "Organization",
                "@id": "https://update.dsesecurity.com/#editorial-team",
                "name": "DSE Security Editorial Team",
                "url": "https://update.dsesecurity.com/",
                "parentOrganization": {
                    "@id": "https://dsesecurity.com/#organization"
                }
            },
            {
                "@type": "WebSite",
                "@id": "https://update.dsesecurity.com/#website",
                "name": "DSE Updates",
                "alternateName": "DSE Security Knowledge Hub",
                "url": "https://update.dsesecurity.com/",
                "inLanguage": "en-US",
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "potentialAction": {
                    "@type": "SearchAction",
                    "target": {
                        "@type": "EntryPoint",
                        "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}"
                    },
                    "query-input": "required name=search_term_string"
                }
            },
            {
                "@type": "WebPage",
                "@id": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks",
                        "item": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/#article",
                "identifier": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
                "url": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/",
                "headline": "Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks",
                "description": "Use Configure certificate templates for ML-DSA in Windows Server to review this narrow operational decision without extending the source beyond its…",
                "abstract": "Use Configure certificate templates for ML-DSA in Windows Server to review this narrow operational decision without extending the source beyond its stated scope.",
                "articleBody": "Frame this document as a source-led configuration and assurance check: Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Configure certificate templates for ML-DSA in Windows Server from Microsoft supports the following bounded statements:\n\nAt Introduction below H1, Microsoft states: “This article describes how to configure Active Directory Certificate Services (AD CS) certificate templates to use Module-Lattice-Based Digital Signature Algorithm (ML-DSA) as the public key algorithm.” The research record locates this support at Introduction below H1.\nAt Introduction below H1, Microsoft states: “After configuring certificate templates, users and computers with appropriate permissions can enroll for ML-DSA certificates.” The research record locates this support at Introduction below H1.\n\nOnly 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.\nWhat the source does not establish\nThe cited page and retained statements do not establish the current state of any DSE or customer environment, prove that the documented configuration is applicable, or authorize a production change. Confirm supported versions, dependencies, and the current live source before use. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities and the environment’s recorded constraints.\nApplicability questions\n\nFor source statement 1 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here?\nWithin certification authorities, templates, enrollment paths, certificate subjects, private-key handling, and delegated PKI roles, which versions, roles, and configuration states define the review population?\nCould Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities invalidate the test, hide a failure, or change applicability?\nWho owns the decision, and which observation requires stopping, escalation, or rollback?\n\nDSE recommendation:\nDSE 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.\nTranslate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include Active Directory, Windows DNS, time, domain-controller reachability, HTTP or LDAP publication, and protected administrative identities, while excluding secrets and sensitive personal or topology data from ordinary tickets.\nVerification and evidence\nBuild a reproducible chain from Introduction below H1; Introduction below H1 to the observed environment. Useful domain evidence includes CA and template exports, enrollment tests, certificate chains, access-control entries, event logs, and revocation-path checks; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-083 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nRetain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes.\nOfficial references\n\nConfigure certificate templates for ML-DSA in Windows Server — Microsoft",
                "datePublished": "2026-08-27T17:06:03+00:00",
                "dateModified": "2026-08-27T17:11:10+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/"
                },
                "inLanguage": "en-US",
                "isAccessibleForFree": true,
                "author": {
                    "@type": "Organization",
                    "name": "DSE Security Editorial Team",
                    "url": "https://update.dsesecurity.com/#editorial-team"
                },
                "publisher": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "image": {
                    "@type": "ImageObject",
                    "@id": "https://update.dsesecurity.com/updates/stage-configure-certificate-templates-for-ml-dsa-in-windows-server-with-ad-dns-rollback-checks/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/network-infrastructure-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Stage Configure certificate templates for ML-DSA in Windows Server with AD/DNS rollback checks"
                },
                "articleSection": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure"
                ],
                "keywords": [
                    "Cybersecurity",
                    "Microsoft 365 & Identity",
                    "Networks & Infrastructure",
                    "Explainer",
                    "Advisory priority"
                ],
                "genre": "Explainer",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Cybersecurity",
                        "url": "https://update.dsesecurity.com/topic/cybersecurity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Microsoft 365 & Identity",
                        "url": "https://update.dsesecurity.com/topic/microsoft-365-identity/"
                    },
                    {
                        "@type": "Thing",
                        "name": "Networks & Infrastructure",
                        "url": "https://update.dsesecurity.com/topic/networks-infrastructure/"
                    }
                ],
                "wordCount": 569,
                "timeRequired": "PT3M",
                "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/",
                "usageInfo": "https://update.dsesecurity.com/usage/",
                "copyrightHolder": {
                    "@id": "https://dsesecurity.com/#organization"
                },
                "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.",
                "citation": {
                    "@type": "CreativeWork",
                    "name": "Configure certificate templates for ML-DSA in Windows Server",
                    "url": "https://learn.microsoft.com/en-us/windows-server/identity/ad-cs/configure-ml-dsa-certificate-templates"
                }
            }
        ]
    }
}