Opselith
POWERSHELL / ACTIVEDIRECTORY
FreeBeginnerRead-onlylow

Export disabled AD users

Export disabled Active Directory users to CSV with PowerShell, including account name, UPN, email, object change date and last logon date.

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

Exports disabled users.

Requirements

  • 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 Export disabled AD users 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 free PowerShell script when you need to export disabled users. 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: Beginner. 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 Export disabled AD users →

How to use this result

Use this report to create a CSV inventory of Active Directory user accounts whose Enabled property is currently false.

When this helps

  • Review disabled accounts before a cleanup, migration or retention decision.
  • Compare disabled accounts with HR, ownership or ticket records.
  • Capture account identity, email, object change date and last logon date in one repeatable report.

How to read the result

  • Each row is a user whose Enabled property is false at query time.
  • WhenChanged is the directory object modification timestamp and is not a reliable record of when the account was disabled. LastLogonDate is also approximate because it is based on replicated logon data.

Things to check

  • Do not calculate account-disable age from WhenChanged alone because other attribute changes can update that timestamp.
  • Disabled accounts can still be intentionally retained for legal, recovery, shared-resource or operational reasons. Confirm ownership and retention requirements before deletion.

What to do next: Compare the disabled-user CSV with your authoritative ownership or HR source and review the oldest or unexplained accounts first.

Related tasks

Official references

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

Script details

Exports disabled users. Review these details before generating or running the script.

reportingexportuserspermissionsdisabled
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 recommended for ActiveDirectory templates.

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

  • 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

Exports disabled users.

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 inactive AD usersreporting · export · findPOWERSHELLExport users with managerreporting · export · usersPOWERSHELLFind users without managerreporting · find · users