# New-ADOrganizationalUnit: create adorganizational unit against recorded identity and DNS state > Use New-ADOrganizationalUnit to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/new-adorganizationalunit-create-adorganizational-unit-against-recorded-identity-and-dns-state/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:04:53+00:00 - Modified: 2026-08-27T17:18:33+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Explainer - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use New-ADOrganizationalUnit 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 New-ADOrganizationalUnit ## 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: New-ADOrganizationalUnit: create adorganizational unit against recorded identity and DNS state. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [New-ADOrganizationalUnit](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adorganizationalunit?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The New-ADOrganizationalUnit cmdlet creates an Active Directory organizational unit (OU).” The research record locates this support at DESCRIPTION. - At DESCRIPTION, Microsoft states: “You can set commonly used OU property values by using the cmdlet parameters.” 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. For an approved change, define prerequisites, a limited test path, success and stop conditions, monitoring, and rollback. Check Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials in design order. Protect credentials, keys, recovery material, personal data, and sensitive topology in evidence. ## 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-153 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review. Record the decision even when no change is made, including uncertainty and the next trigger. Use safe testing conditions for disruptive work, preserve rollback proof, and revisit the conclusion after relevant platform, dependency, vendor, or ownership changes. ## Official references - [New-ADOrganizationalUnit](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adorganizationalunit?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: New-ADOrganizationalUnit - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adorganizationalunit?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “New-ADOrganizationalUnit: create adorganizational unit against recorded identity and DNS state,” DSE Security, https://update.dsesecurity.com/updates/new-adorganizationalunit-create-adorganizational-unit-against-recorded-identity-and-dns-state/ 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.