{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
        "slug": "unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state",
        "url": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/"
        },
        "title": "Unlock-ADAccount: unlock adaccount against recorded identity and DNS state",
        "summary": "Use Unlock-ADAccount 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": "identity-cloud",
            "label": "Identity & cloud",
            "alt": "Governed cloud identity system with connected service and lifecycle nodes.",
            "card_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-card.webp?v=1.8.20",
            "hero_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-hero.webp?v=1.8.20",
            "social_url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-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:04:28+00:00",
        "modified_at": "2026-08-27T17:18:34+00:00",
        "reviewed_on": "2026-08-27",
        "reading_minutes": 3,
        "word_count": 563,
        "potentially_affected": "Teams, systems, services, or facilities within the stated scope of Unlock-ADAccount",
        "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": "Unlock-ADAccount",
            "url": "https://learn.microsoft.com/en-us/powershell/module/activedirectory/unlock-adaccount?view=windowsserver2025-ps",
            "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: Unlock-ADAccount: unlock adaccount against recorded identity and DNS state. 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/powershell/module/activedirectory/unlock-adaccount?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">Unlock-ADAccount</a> from Microsoft supports the following bounded statements:</p>\n<ul>\n<li>At DESCRIPTION, Microsoft states: “The Unlock-ADAccount cmdlet restores Active Directory Domain Services (AD DS) access for an account that is locked.” The research record locates this support at <strong>DESCRIPTION</strong>.</li>\n<li>At DESCRIPTION, Microsoft states: “AD DS access is suspended or locked for an account when the number of incorrect password entries exceeds the maximum number allowed by the account password policy.” The research record locates this support at <strong>DESCRIPTION</strong>.</li>\n</ul>\n<p>These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.</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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.</p>\n<h2>Applicability questions</h2>\n<ul>\n<li>For source statement 1 at <strong>DESCRIPTION</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>For source statement 2 at <strong>DESCRIPTION</strong>, which observable configuration, record, or test can confirm applicability here?</li>\n<li>What inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?</li>\n<li>Which condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?</li>\n<li>What result would disprove the working assumption and return the issue to the owner?</li>\n</ul>\n<h2>DSE recommendation:</h2>\n<p>DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.</p>\n<p>If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.</p>\n<h2>Verification and evidence</h2>\n<p>Build a reproducible chain from <strong>DESCRIPTION</strong>; <strong>DESCRIPTION</strong> to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.</p>\n<p>Label this evidence set <strong>DSE-20260827-178</strong> so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.</p>\n<p>Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.</p>\n<h2>Official references</h2>\n<ul>\n<li><a href=\"https://learn.microsoft.com/en-us/powershell/module/activedirectory/unlock-adaccount?view=windowsserver2025-ps\" target=\"_blank\" rel=\"noopener noreferrer\">Unlock-ADAccount</a> — Microsoft</li>\n</ul>",
        "content_text": "Frame this document as a source-led configuration and assurance check: Unlock-ADAccount: unlock adaccount against recorded identity and DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Unlock-ADAccount from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The Unlock-ADAccount cmdlet restores Active Directory Domain Services (AD DS) access for an account that is locked.” The research record locates this support at DESCRIPTION.\nAt DESCRIPTION, Microsoft states: “AD DS access is suspended or locked for an account when the number of incorrect password entries exceeds the maximum number allowed by the account password policy.” The research record locates this support at DESCRIPTION.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?\nWhich condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from DESCRIPTION; DESCRIPTION to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-178 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nUnlock-ADAccount — Microsoft",
        "content_markdown": "Frame this document as a source-led configuration and assurance check: Unlock-ADAccount: unlock adaccount against recorded identity and DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\n\n## Source fact:\n\nThe official [Unlock-ADAccount](https://learn.microsoft.com/en-us/powershell/module/activedirectory/unlock-adaccount?view=windowsserver2025-ps) from Microsoft supports the following bounded statements:\n\n- At DESCRIPTION, Microsoft states: “The Unlock-ADAccount cmdlet restores Active Directory Domain Services (AD DS) access for an account that is locked.” The research record locates this support at DESCRIPTION.\n\n- At DESCRIPTION, Microsoft states: “AD DS access is suspended or locked for an account when the number of incorrect password entries exceeds the maximum number allowed by the account password policy.” The research record locates this support at DESCRIPTION.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\n\n## Applicability questions\n\n- For source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\n\n- For source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\n\n- What inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?\n\n- Which condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?\n\n- What result would disprove the working assumption and return the issue to the owner?\n\n## DSE recommendation:\n\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\n\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.\n\n## Verification and evidence\n\nBuild a reproducible chain from DESCRIPTION; DESCRIPTION to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.\n\nLabel this evidence set DSE-20260827-178 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\n\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\n\n## Official references\n\n- [Unlock-ADAccount](https://learn.microsoft.com/en-us/powershell/module/activedirectory/unlock-adaccount?view=windowsserver2025-ps) — 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/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
                "url": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-08-27"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Unlock-ADAccount: unlock adaccount against recorded identity and DNS state",
                        "item": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/#article",
                "identifier": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
                "url": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/",
                "headline": "Unlock-ADAccount: unlock adaccount against recorded identity and DNS state",
                "description": "Use Unlock-ADAccount to review this narrow operational decision without extending the source beyond its stated scope.",
                "abstract": "Use Unlock-ADAccount 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: Unlock-ADAccount: unlock adaccount against recorded identity and DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting.\nSource fact:\nThe official Unlock-ADAccount from Microsoft supports the following bounded statements:\n\nAt DESCRIPTION, Microsoft states: “The Unlock-ADAccount cmdlet restores Active Directory Domain Services (AD DS) access for an account that is locked.” The research record locates this support at DESCRIPTION.\nAt DESCRIPTION, Microsoft states: “AD DS access is suspended or locked for an account when the number of incorrect password entries exceeds the maximum number allowed by the account password policy.” The research record locates this support at DESCRIPTION.\n\nThese statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align.\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. The citation is not a substitute for observed state, authorization, compliance evidence, or dependency health. Examine Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before translating the source into an operational decision.\nApplicability questions\n\nFor source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nFor source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here?\nWhat inventory proves which parts of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services are in and out of scope?\nWhich condition in Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must be healthy before evidence is trustworthy?\nWhat result would disprove the working assumption and return the issue to the owner?\n\nDSE recommendation:\nDSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. Record the source location, examined part of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, observed and expected states, owner, and reason for deviation.\nIf the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials and sanitize protected material before retention.\nVerification and evidence\nBuild a reproducible chain from DESCRIPTION; DESCRIPTION to the observed environment. Useful domain evidence includes sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state; label every item with scope, timestamp, collector, and stable identifier.\nLabel this evidence set DSE-20260827-178 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.\nKeep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.\nOfficial references\n\nUnlock-ADAccount — Microsoft",
                "datePublished": "2026-08-27T17:04:28+00:00",
                "dateModified": "2026-08-27T17:18:34+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/"
                },
                "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/unlock-adaccount-unlock-adaccount-against-recorded-identity-and-dns-state/#primaryimage",
                    "url": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "contentUrl": "https://update.dsesecurity.com/assets/editorial/identity-cloud-social-v2.jpg?v=1.8.20",
                    "width": 1200,
                    "height": 630,
                    "caption": "Unlock-ADAccount: unlock adaccount against recorded identity and DNS state"
                },
                "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": 563,
                "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": "Unlock-ADAccount",
                    "url": "https://learn.microsoft.com/en-us/powershell/module/activedirectory/unlock-adaccount?view=windowsserver2025-ps"
                }
            }
        ]
    }
}