# Validate Support policy and known issues for ADMT with AD/DNS evidence > Use Support policy and known issues for ADMT to review this narrow operational decision without extending the source beyond its stated scope. - Canonical URL: https://update.dsesecurity.com/updates/validate-support-policy-and-known-issues-for-admt-with-ad-dns-evidence/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-08-27T17:00:44+00:00 - Modified: 2026-08-27T17:37:18+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 Support policy and known issues for ADMT 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 Support policy and known issues for ADMT ## 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: Validate Support policy and known issues for ADMT with AD/DNS evidence. Only the official source and traced locations below supply facts. Confirm applicability before acting. ## Source fact: The official [Support policy and known issues for ADMT](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/support-policy-and-known-issues-for-admt) from Microsoft supports the following bounded statements: - At Introduction below H1, Microsoft states: “This article discusses information about the current level of support for Active Directory Migration Tool (ADMT) on current Windows Client and Windows Server operating systems.” The research record locates this support at Introduction below H1. - At Introduction below H1, Microsoft states: “This article also lists known issues that administrators might experience when they try to migrate user profiles, security principals, passwords, or security identifier history (sIDHistory) data between Active Directory domains and forests.” The research record locates this support at Introduction below H1. These statements are the factual basis for this document. Do not extend them into a broader assurance. Review Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services only where the source and recorded environment align. ## 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 Introduction below H1, which observable configuration, record, or test can confirm applicability here? - For source statement 2 at Introduction below H1, which observable configuration, record, or test can confirm applicability here? - Which owner can attest to the recorded state of Active Directory objects, search bases, domain controllers, delegated roles, cmdlet parameters, and the DNS paths used to locate directory services, including exceptions? - What baseline for Active Directory replication, Windows DNS, domain-controller location, time, network reachability, privileges, and protected credentials must accompany the source-specific observation? - Which success, stop, and escalation criteria are written before testing begins? ## DSE recommendation: DSE recommends using the cited source as the evidence anchor for this decision. Start with applicability, then compare the observed state with the cited source. 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 Introduction below H1; Introduction below H1 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-402 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 - [Support policy and known issues for ADMT](https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/support-policy-and-known-issues-for-admt) — Microsoft ## Primary reference - Name: Support policy and known issues for ADMT - Authority: Microsoft Learn - URL: https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/support-policy-and-known-issues-for-admt - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Validate Support policy and known issues for ADMT with AD/DNS evidence,” DSE Security, https://update.dsesecurity.com/updates/validate-support-policy-and-known-issues-for-admt-with-ad-dns-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.