# Wait for KDS root-key convergence before creating gMSAs > Use Create a Key Distribution Service (KDS) Root Key to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/wait-for-kds-root-key-convergence-before-gmsa/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:14:38+00:00 - Modified: 2026-08-27T12:58:58+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Explainer - DSE priority: Advisory - Topics: IT, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Create a Key Distribution Service (KDS) Root Key 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 Create a Key Distribution Service (KDS) Root Key ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Frame this document as a source-led configuration and assurance check: Wait for KDS root-key convergence before creating gMSAs. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Create a Key Distribution Service (KDS) Root Key](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/create-the-key-distribution-services-kds-root-key) from Microsoft supports the following bounded statements: - Domain controllers require a KDS root key before they can generate gMSA passwords. The research record locates this support at Opening overview. - Controllers can wait up to 10 hours after key creation so AD replication can converge before gMSA use. The research record locates this support at Opening overview. Only the traced statements above are asserted as source facts. Apply the review to forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles after confirming that the source and deployed context match. ## What the source does not establish Do not bypass convergence timing in production; replication problems can cause password-retrieval failures. Do not read the source as proof of implementation or permission to change production. Its guidance remains conditional on Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity and the environment’s recorded constraints. ## 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, which observable configuration, record, or test can confirm applicability here? - What inventory proves which parts of forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated roles are in and out of scope? - Which condition in Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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 forests, domains, controllers, directory partitions, trusts, sites, replication links, service accounts, and delegated 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 Windows DNS, time synchronization, network reachability, PKI, backups, virtualization safeguards, and privileged identity 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 adjacent to the sanitized artifacts used for comparison. Prefer directory and policy exports, replication and locator tests, event logs, trust state, role ownership, and controlled authentication tests, 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 - [Create a Key Distribution Service (KDS) Root Key](https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/create-the-key-distribution-services-kds-root-key) — Microsoft ## Primary reference - Name: Create a Key Distribution Service (KDS) Root Key - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/group-managed-service-accounts/group-managed-service-accounts/create-the-key-distribution-services-kds-root-key - Source publication date: 2025-07-09 ## Citation and use Preferred citation: “Wait for KDS root-key convergence before creating gMSAs,” DSE Security, https://update.dsesecurity.com/updates/wait-for-kds-root-key-convergence-before-gmsa/ 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.