# Map native Windows LAPS cmdlets before replacing legacy scripts > Use Windows LAPS PowerShell Cmdlets Overview to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/map-native-windows-laps-cmdlets-before-replacing-legacy-scripts/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T12:13:58+00:00 - Modified: 2026-08-27T12:58:59+00:00 - Last reviewed by DSE: 2026-08-26 - Resource type: Explainer - DSE priority: Advisory - Topics: Cybersecurity, IT, Microsoft 365 & Identity - Reading time: 3 minutes ## What you need to know Use Windows LAPS PowerShell Cmdlets Overview 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 Windows LAPS PowerShell Cmdlets Overview ## 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: Map native Windows LAPS cmdlets before replacing legacy scripts. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Windows LAPS PowerShell Cmdlets Overview](https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-powershell) from Microsoft supports the following bounded statements: - Get-LapsADPassword queries Active Directory, Reset-LapsPassword initiates immediate rotation, and Set-LapsADAuditing configures Windows LAPS auditing on Active Directory organizational units. The research record locates this support at Cmdlet descriptions and usage > cmdlet table. - Several native Windows LAPS cmdlets have no legacy counterpart, and the Active Directory cmdlets operate on a different set of schema extensions from legacy Microsoft LAPS. The research record locates this support at Comparing Windows LAPS and legacy Microsoft LAPS PowerShell > mapping table and following paragraph. Do not import neighboring assumptions into the source record. The supported task is a scoped comparison involving managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios and the conditions the source actually describes. ## What the source does not establish A cmdlet mapping does not prove script compatibility, authorization, or safe secret handling; protect returned passwords and test schema, permissions, and output before migration. A correct source interpretation can still be inapplicable to a particular design. Confirm Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations, ownership, and change authority instead of treating documented behavior as a deployment guarantee. ## Applicability questions - For source statement 1 at Cmdlet descriptions and usage > cmdlet table, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Comparing Windows LAPS and legacy Microsoft LAPS PowerShell > mapping table and following paragraph, which observable configuration, record, or test can confirm applicability here? - What inventory proves which parts of managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios are in and out of scope? - Which condition in Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations 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 managed accounts, policy assignment, password storage, directory permissions, retrieval roles, rotation, and recovery scenarios, observed and expected states, owner, and reason for deviation. If the review warrants change, use a bounded implementation with prerequisites, test population, monitoring, abort criteria, and a rehearsed reversal. Sequence checks for Active Directory or Entra ID, Windows DNS, policy processing, device identity, time, and protected administrative workstations and sanitize protected material before retention. ## Verification and evidence Evidence should let another reviewer reproduce this decision. Retain observations beside the traced locations Cmdlet descriptions and usage > cmdlet table; Comparing Windows LAPS and legacy Microsoft LAPS PowerShell > mapping table and following paragraph. Favor policy exports, directory access-control entries, sanitized client events, rotation tests, retrieval authorization, and exception records, linked to stable identifiers, time, and operator. Retain the starting state, authorization, execution record, outcome, deviation, and final state as one review package. Move disruptive checks to an approved test path. Reopen the decision when versions, design, dependencies, ownership, or official guidance changes. ## Official references - [Windows LAPS PowerShell Cmdlets Overview](https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-powershell) — Microsoft ## Primary reference - Name: Windows LAPS PowerShell Cmdlets Overview - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/windows-server/identity/laps/laps-management-powershell - Source publication date: 2025-05-06 ## Citation and use Preferred citation: “Map native Windows LAPS cmdlets before replacing legacy scripts,” DSE Security, https://update.dsesecurity.com/updates/map-native-windows-laps-cmdlets-before-replacing-legacy-scripts/ 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.