Opselith
POWERSHELL / ACTIVEDIRECTORY
FreeIntermediateRead-onlylow

Find AD users in an OU

Export Active Directory users below a chosen OU or search base to CSV with PowerShell, including account state, department and job title.

Open in PowerShell Builder →Browse all scripts

Generated locally in your browser · Review before running · Opselith does not connect to your tenant

What this PowerShell script does

Finds users below a supplied organizational unit.

Requirements

  • Search base DN - e.g. OU=Users,DC=contoso,DC=com
  • CSV output path - Example: C:\Temp\report.csv

Environment

  • Module: ActiveDirectory
  • Permissions: Directory read access
  • Output: CSV report
  • Context: Windows host with RSAT
  • Risk: Low
Review before you run The script is generated locally. Test outside production first.
NEXT STEP

Ready to generate

Configure Find AD users in an OU in the Builder, review the generated PowerShell and run it yourself in your own PowerShell session.

Configure this script →Open Builder
More about this script

Why use this template?

Use this PowerShell template when you need to find users below a supplied organizational unit. It is generated locally and can be reviewed before you run it yourself in your own PowerShell session.

The template uses ActiveDirectory and requires Directory read access. Output: CSV report. Level: Intermediate. Action: Read-only. Risk: Low.

Review before running

The script is generated in your browser. Read it before you run it, and test it outside production first. “Read-only” describes the script itself; anything you add around it can still change data.

Generate the script

  1. Open the template in the PowerShell Builder.
  2. Enter the requested values and review the module, permissions, output and risk.
  3. Generate the script, read it carefully, and test it outside production before use.

The script is generated locally in your browser. Nothing needs to be uploaded to Opselith.

Generate Find AD users in an OU →

How to use this result

Use this template when you need a user export limited to one Active Directory organizational unit and the OUs below it.

When this helps

  • Create a targeted user inventory for one business unit, migration wave or delegated administration area.
  • Export users below a known OU without querying the whole directory.
  • Review account state, department and title for users in a specific directory branch.

How to read the result

  • The search base must be an Active Directory distinguished name such as OU=Users,DC=contoso,DC=com.
  • The script uses subtree scope, so users in child OUs below the search base are included as well as users directly in the selected OU.

Things to check

  • If you need only users directly in one OU and not child OUs, this template is broader than that requirement.
  • An incorrect distinguished name causes the query to fail rather than silently falling back to the whole directory.

What to do next: Review the CSV for the expected OU population, then compare it with the full user export or your migration scope when you need to confirm coverage.

Related tasks

Official references

Before you runModule, permissions, inputs, compatibility and script checks
OPS / SCRIPT DETAILS

Script details

Finds users below a supplied organizational unit. Review these details before generating or running the script.

active-directoryfinduserspermissions
Generated here. Run by you.Opselith does not connect to your tenant or run PowerShell. After generating, review the script and run it in your own PowerShell session.

What it works with

Module: ActiveDirectory

ActiveDirectory lets PowerShell work with on-premises Active Directory and is normally installed through Windows RSAT.

Context: Windows host with RSAT

Compatibility: Windows PowerShell 5.1 / ISE is supported for this Windows administration template.

Permissions and changes

Permissions: Directory read access

Risk: Low

Read-only: designed to collect information without intentionally changing the target environment.

Changes: Read-only. The script reads data and does not intentionally change the target environment.

Inputs

  • Search base DN - e.g. OU=Users,DC=contoso,DC=com (Required)
  • CSV output path - Example: C:\Temp\report.csv (Required)

What to expect

Output: CSV report

Expect a CSV file at the path you choose. Open it in Excel or another CSV viewer and review the rows.

Example: C:\Temp\report.csv

This template is in the Free library and is generated locally in your browser. Opselith does not run it; you review and run the script in your own PowerShell session.

Example use

Finds users below a supplied organizational unit.

Enter the required values in the Builder, review the generated script and confirm the output before running it.

Before you run: Make sure your account has Directory read access. Check that the ActiveDirectory PowerShell module is available and that you are using the supported PowerShell version. Review the generated script and output path, then test outside production first.
Script checksWhat has been verifiedQA reviewed
Static checksPassed
PSScriptAnalyzerPending
Real-world run testNot yet recorded
Last checkedNot yet recorded

Real-world run results are shown only after Opselith reviews and accepts a tester report.

Tester: report a result →
TEST STATUSWhat Opselith has checked

Last reviewed: 10 Sept 2026

PSScriptAnalyzer: Awaiting a release PSScriptAnalyzer gate that includes this script. No analyzer pass is claimed yet.

Pending or Not yet recorded means there is no accepted result on file yet. A passed analyzer check does not mean the script has been run in a real tenant.

NEXT IN THE LIBRARY

Scripts for similar admin tasks and Microsoft services.

Browse Active Directory PowerShell scripts →
POWERSHELLExport AD organizational unitsreporting · export · permissionsPOWERSHELLFind AD users by departmentactive-directory · find · usersPOWERSHELLExport AD group membersactive-directory · export · users