# New-ADClaimType: create adclaim type with rollback checks > Use New-ADClaimType to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/new-adclaimtype-create-adclaim-type-with-rollback-checks/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:04:44+00:00 - Modified: 2026-08-27T17:18:33+00:00 - Last reviewed by DSE: 2026-08-27 - Resource type: Checklist - DSE priority: Advisory - Topics: Cybersecurity, Microsoft 365 & Identity, Networks & Infrastructure - Reading time: 3 minutes ## What you need to know Use New-ADClaimType 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 New-ADClaimType ## DSE recommendation Compare the observed state with the cited official source, document applicability and exceptions, and test any approved change with rollback safeguards. ## Article Treat this document as a focused evidence review: New-ADClaimType: create adclaim type with rollback checks. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [New-ADClaimType](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adclaimtype?view=windowsserver2025-ps) from Microsoft supports the following bounded statements: - At DESCRIPTION, Microsoft states: “The New-ADClaimType cmdlet creates a new claim type in Active Directory.” The research record locates this support at DESCRIPTION. - At Example 1: Create a new user claim type with a display name, Microsoft states: “This command creates a new user claim type with display name Title that is sourced from the Active Directory attribute Title.” The research record locates this support at Example 1: Create a new user claim type with a display name. Keep the evidence boundary at these traced claims. They support a review of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services; they do not support conclusions outside the source’s stated conditions. ## 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 Example 1: Create a new user claim type with a display name, 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. Anchor the review in the cited section and keep observation separate from interpretation. 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. An implementation decision needs an owner, approved window, prechecks, observable outcome, stop authority, and rollback path. Validate Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials before and after the test, and store only sanitized operational evidence. ## Verification and evidence A reviewer should be able to retrace the decision from DESCRIPTION; Example 1: Create a new user claim type with a display name through sanitized command transcripts, parameter records, directory exports, authorization records, DNS locator tests, and before-and-after state. Record what was collected, where, when, by whom, and which system or role it represents. Label this evidence set DSE-20260827-162 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 - [New-ADClaimType](https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adclaimtype?view=windowsserver2025-ps) — Microsoft ## Primary reference - Name: New-ADClaimType - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/powershell/module/activedirectory/new-adclaimtype?view=windowsserver2025-ps - Source publication date: Not stated by the source ## Citation and use Preferred citation: “New-ADClaimType: create adclaim type with rollback checks,” DSE Security, https://update.dsesecurity.com/updates/new-adclaimtype-create-adclaim-type-with-rollback-checks/ 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.