# Set-ADAccountExpiration: change adaccount expiration with bounded evidence

> Use Set-ADAccountExpiration to review this narrow operational decision without extending the source beyond its stated scope.

- Canonical URL: https://update.dsesecurity.com/updates/set-adaccountexpiration-change-adaccount-expiration-with-bounded-evidence/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-08-27T17:04:31+00:00
- Modified: 2026-08-27T17:18:34+00:00
- Last reviewed by DSE: 2026-08-27
- Resource type: Playbook
- DSE priority: Advisory
- Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure
- Reading time: 3 minutes

## What you need to know

Use Set-ADAccountExpiration 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 Set-ADAccountExpiration

## DSE recommendation

Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards.

## Article

Keep this document to one review outcome: Set-ADAccountExpiration: change adaccount expiration with bounded evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting.

## Source fact:

The official [Set-ADAccountExpiration](https://learn.microsoft.com/en-us/powershell/module/activedirectory/set-adaccountexpiration?view=windowsserver2025-ps) from Microsoft supports the following bounded statements:

- At DESCRIPTION, Microsoft states: “The Set-ADAccountExpiration cmdlet sets the expiration time for a user, computer, or service account.” The research record locates this support at DESCRIPTION.

- At DESCRIPTION, Microsoft states: “To specify a time period from the current time, use the TimeSpan parameter.” The research record locates this support at DESCRIPTION.

Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services and the conditions the source actually describes.

## 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. Use a two-person review for the source interpretation and the resulting operational decision. 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.

Do not move from citation to production in one step. Pilot the decision where practical, observe agreed signals, retain a reversal point, and verify Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials. Handle credentials, keys, recovery data, and personal information through approved secure channels.

## Verification and evidence

Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations DESCRIPTION; DESCRIPTION. Favor sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state, linked to stable identifiers, time, and operator.

Label this evidence set DSE-20260827-175 so observations, approvals, exceptions, and later rechecks cannot be substituted from another source review.

Keep before-state evidence, approval, test or change result, exceptions, and after-state evidence together. Use an approved lab, window, or nonproduction path for risky tests. Set a recheck trigger for version, architecture, dependency, vendor, incident, or ownership change. A check proves only what was observed.

## Official references

- [Set-ADAccountExpiration](https://learn.microsoft.com/en-us/powershell/module/activedirectory/set-adaccountexpiration?view=windowsserver2025-ps) — Microsoft

## Primary reference

- Name: Set-ADAccountExpiration
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/powershell/module/activedirectory/set-adaccountexpiration?view=windowsserver2025-ps
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Set-ADAccountExpiration: change adaccount expiration with bounded evidence,” DSE Security, https://update.dsesecurity.com/updates/set-adaccountexpiration-change-adaccount-expiration-with-bounded-evidence/
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.
