# Search-ADAccount: search adaccount under AD/DNS change control > Use Search-ADAccount to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/search-adaccount-search-adaccount-under-ad-dns-change-control/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:04:55+00:00 - Modified: 2026-08-27T17:18:33+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Briefing - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use Search-ADAccount 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 Search-ADAccount ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Use this document to resolve one bounded operational decision: Search-ADAccount: search adaccount under AD/DNS change control. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Search-ADAccount](https://learn.microsoft.com/en-us/powershell/module/activedirectory/search-adaccount?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The Search-ADAccount cmdlet retrieves one or more user, computer, or service accounts that meet the criteria specified by the parameters.” The research record locates this support at DESCRIPTION. - At DESCRIPTION, Microsoft states: “For example, you can search for all accounts that have expired by specifying the AccountExpired parameter.” The research record locates this support at DESCRIPTION. 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. ## What the source does not establish 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. No current deployment state or change approval follows from the source alone. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials, and treat examples or options as conditional inputs rather than defaults. ## Applicability questions - For source statement 1 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at DESCRIPTION, which observable configuration, record, or test can confirm applicability here? - 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? - 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? - 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. 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. 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. ## Verification and evidence Build 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. Label this evidence set DSE-20260827-151 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. 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 - [Search-ADAccount](https://learn.microsoft.com/en-us/powershell/module/activedirectory/search-adaccount?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: Search-ADAccount - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/activedirectory/search-adaccount?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Search-ADAccount: search adaccount under AD/DNS change control,” DSE Security, https://update.dsesecurity.com/updates/search-adaccount-search-adaccount-under-ad-dns-change-control/ 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.