Active Directory Recycle Bin improves recovery from accidental object deletion by retaining information that a simple tombstone restore does not preserve in the same way. It can restore eligible deleted users, groups and other objects with their retained attributes and links. It does not replace system-state backups, protect against every form of directory corruption or reverse arbitrary changes made to a live object.
Enabling the feature is an irreversible forest-level decision. Plan and approve it before executing the command, confirm directory health and keep a tested recovery strategy. Objects deleted before enablement do not become newly recoverable through Recycle Bin merely because the feature is switched on afterward.
Understand the recovery boundary
Recycle Bin helps with deletion within the configured retention lifecycle. It is not an unlimited historical archive. Deleted objects eventually progress beyond the state from which this feature can restore them, based on directory configuration and garbage collection. Check the actual retention values and the organization's recovery expectations.
Restoration recovers the retained object rather than creating a new user with the same display name. This matters for identity and group relationships. Nevertheless, verify the restored object's current security and application state instead of assuming all connected systems automatically return to normal.
External services, synchronized directories, mail systems and applications can have their own deletion and recovery workflows. Restoring the on-premises AD object does not necessarily undo their actions. Coordinate with those owners before recovering an object whose deletion propagated elsewhere.
Check functional levels, permissions and directory health
Use the Active Directory tools from a suitable authorized management computer. Confirm the forest and domain functional levels meet the documented requirements, at least Windows Server 2008 R2 for this feature, and use an account authorized for the forest-wide optional-feature change. Do not raise functional levels casually as a hidden prerequisite.
Get-ADForest | Select-Object Name,ForestMode
Get-ADDomain | Select-Object DNSRoot,DomainMode
Get-ADOptionalFeature -Identity 'Recycle Bin Feature' |
Select-Object Name,EnabledScopes
repadmin /replsummary
Check all relevant domains and replication health, not only the domain returned by the management computer's default context. An existing EnabledScopes value can show that Recycle Bin is already active; do not reconfigure an established feature just because an old checklist begins with Enable.
Confirm current AD-aware backups and the forest recovery plan. Keep credentials, recovery procedures and required tools accessible outside the affected server. A successful feature configuration is not a substitute for proving that a broader recovery is possible.
Record retention and recovery ownership
Identify who can browse deleted objects and who can restore them. Restoration can reinstate access, so it should follow an authorization process rather than being treated as a harmless undo button. Preserve the deletion ticket, incident context and object identity.
Review the directory's deleted-object retention settings through the approved AD administration process. Do not change them simply to match an arbitrary example. Longer retention can change storage and operational requirements, while shorter retention can conflict with the organization's incident-detection window.
Document how a request will identify the correct object: object GUID, SID where applicable, previous distinguished name, deletion time and business owner. A display name is often insufficient because several objects can share similar names or an account may have been recreated after deletion.
Enable the feature once the forest change is approved
From the authorized management context, explicitly select the intended forest and enable its optional feature:
$forest = Get-ADForest
Enable-ADOptionalFeature -Identity 'Recycle Bin Feature' `
-Scope ForestOrConfigurationSet -Target $forest.Name
Review the target and confirmation prompt carefully. The operation cannot be reversed by disabling a checkbox. Do not suppress confirmation in an ad hoc script merely to speed up an irreversible administrative action.
Allow replication and query the feature again. Confirm the expected scope is listed and that relevant domain controllers have converged. If a management interface does not immediately show Deleted Objects, refresh or reconnect and investigate replication before repeating the enable command.
Validate with a dedicated test object
Use a clearly labelled test object in an approved test OU. Record its GUID and relevant attributes, then delete it through the normal supported tools. Avoid deleting a real employee, privileged account or application group to demonstrate the feature.
In Active Directory Administrative Center, open the domain's Deleted Objects container and locate the exact test object. Review its properties and original location. Restore it to the original container where appropriate, then confirm the object and expected relationships return.
The validation should include the directory state, not a claim that the feature works because the enable command returned without error. If a group-membership test is part of the plan, use a harmless test group and verify the retained relationship after restore. Keep the test evidence and remove the test objects through the agreed process afterward.
Restore a real object by reviewed identity
When an incident occurs, first determine whether the object was deleted after enablement and remains recoverable. Browse candidates without piping a broad search directly into Restore-ADObject. Review the GUID, previous parent, object class and deletion context before changing anything.
A PowerShell workflow can retrieve the specific reviewed object using its GUID:
$guid = Read-Host 'Enter the reviewed deleted object GUID'
$deleted = Get-ADObject -Identity $guid -IncludeDeletedObjects `
-Properties lastKnownParent,whenChanged,isDeleted
$deleted | Select-Object ObjectGUID,Name,ObjectClass,isDeleted,lastKnownParent,whenChanged
Only after confirming the selected deleted object should the authorized operator restore it:
Restore-ADObject -Identity $deleted.ObjectGUID
If the original parent was deleted, restore the necessary parent hierarchy first or use an explicitly reviewed supported target location. Do not restore an entire subtree blindly. A naming conflict with a newly created object requires a deliberate decision so the wrong identity is not overwritten or confused with the recovered one.
Verify security and dependent systems
Confirm the object's identity, location, retained attributes and group relationships. For a user, review enabled state, account restrictions and authentication through a controlled test. Restoring a compromised or intentionally disabled account should not automatically return it to unrestricted use.
Check application access and synchronization behavior with the relevant owners. Some systems may have already removed licenses, mailboxes, profiles or application records. Those recovery actions need their own supported procedures and may have different retention windows.
Allow replication and verify from the domain controllers relevant to the user's site or application. A successful read from one controller does not prove every dependent service has refreshed its view.
Diagnose missing objects and restoration errors
If the object is absent, confirm the domain, search context, permissions, enablement date and retention state. Check whether the incident was a rename, move or attribute change rather than deletion. Recycle Bin is not the appropriate tool for undoing a live object's incorrect attribute value.
If restoration fails, inspect the original parent, naming conflicts, permissions and replication health. Preserve the exact error and object GUID. Do not recreate a user with the same name as an automatic workaround when the application depends on the original identity.
Keep the irreversible feature distinct from reversible tests
You can clean up test objects and reverse a mistaken restoration through a reviewed directory change, but you cannot disable Recycle Bin after enablement. Deleting a restored object again is itself another security and retention event, not an invisible cancellation.
Keep backups, recovery exercises and access reviews in place. Microsoft's Recycle Bin guidance explains enablement and restore behavior; the Restore-ADObject reference describes targeted restoration.
Related procedures
How to Replace an Old Domain Controller with Windows Server 2025; How to Audit Active Directory Group Membership Changes; How to Transfer and Seize Active Directory FSMO Roles Safely.