Merge pull request #53641 from Orin-Thomas/orthomas-27Feb26a

Removal of ADMT content

Author: ttorble

.openpublishing.redirection.json

@@ -64587,6 +64587,21 @@
       "source_path": "learn-pr/azure/stage-deploy-app-service-deployment-slots/6-summary.yml",
       "redirect_url": "https://learn.microsoft.com/en-us/azure/app-service/deploy-staging-slots?tabs=portal",
       "redirect_document_id": false
-    }                    
+    },                    
+    { 
+      "source_path": "learn-pr/wwl-azure/active-directory-domain-services-migration/5-explore-active-directory-migration-tool.yml",
+      "redirect_url": "https://learn.microsoft.com/en-us/training/paths/migrate-servers-workloads-premises-hybrid-environments?tabs=portal",
+      "redirect_document_id": false
+    },    
+    { 
+      "source_path": "learn-pr/wwl-azure/active-directory-domain-services-migration/6-knowledge-check.yml",
+      "redirect_url": "https://learn.microsoft.com/en-us/training/paths/migrate-servers-workloads-premises-hybrid-environments?tabs=portal",
+      "redirect_document_id": false
+    },
+        { 
+      "source_path": "learn-pr/wwl-azure/active-directory-domain-services-migration/7-summary-resources.yml",
+      "redirect_url": "https://learn.microsoft.com/en-us/training/paths/migrate-servers-workloads-premises-hybrid-environments?tabs=portal",
+      "redirect_document_id": false
+    }      
   ]
 }

learn-pr/wwl-azure/active-directory-domain-services-migration/1-introduction.yml

@@ -6,7 +6,7 @@ metadata:
   description: "Introduction"
   ms.date: 12/20/2024
   author: wwlpublish
-  ms.author: tonyj
+  ms.author: robbarefoot
   ms.topic: unit
 azureSandbox: false
 labModal: false

learn-pr/wwl-azure/active-directory-domain-services-migration/2-examine-upgrade-migration.yml

@@ -6,7 +6,7 @@ metadata:
   description: "Examine upgrade vs. migration"
   ms.date: 12/20/2024
   author: wwlpublish
-  ms.author: tonyj
+  ms.author: robbarefoot
   ms.topic: unit
 azureSandbox: false
 labModal: false

learn-pr/wwl-azure/active-directory-domain-services-migration/3-upgrade-previous-version-of-active-directory-domain-services.yml

@@ -6,7 +6,7 @@ metadata:
   description: "Upgrade a previous version of Active Directory Domain Services to Windows Server 2025"
   ms.date: 12/20/2024
   author: wwlpublish
-  ms.author: tonyj
+  ms.author: robbarefoot
   ms.topic: unit
 azureSandbox: false
 labModal: false

learn-pr/wwl-azure/active-directory-domain-services-migration/4-migrate-to-active-directory-domain-services.yml

@@ -6,7 +6,7 @@ metadata:
   description: "Migrate to Active Directory Domain Services in Windows Server 2025 from a previous version"
   ms.date: 12/20/2024
   author: wwlpublish
-  ms.author: tonyj
+  ms.author: robbarefoot
   ms.topic: unit
 azureSandbox: false
 labModal: false

learn-pr/wwl-azure/active-directory-domain-services-migration/5-explore-active-directory-migration-tool.yml

@@ -6,14 +6,14 @@ metadata:
   description: "Knowledge check"
   ms.date: 12/20/2024
   author: wwlpublish
-  ms.author: tonyj
+  ms.author: robbarefoot
   ms.topic: unit
   module_assessment: true
 azureSandbox: false
 labModal: false
 durationInMinutes: 3
 content: |
-  [!include[](includes/6-knowledge-check.md)]
+  [!include[](includes/5-knowledge-check.md)]
 quiz:
   title: "Check your knowledge"
   questions:

…services-migration/6-knowledge-check.yml …services-migration/5-knowledge-check.ymllearn-pr/wwl-azure/active-directory-domain-services-migration/6-knowledge-check.yml renamed to learn-pr/wwl-azure/active-directory-domain-services-migration/5-knowledge-check.yml learn-pr/wwl-azure/active-directory-domain-services-migration/6-knowledge-check.yml renamed to learn-pr/wwl-azure/active-directory-domain-services-migration/5-knowledge-check.yml

@@ -6,10 +6,10 @@ metadata:
   description: "Summary"
   ms.date: 12/20/2024
   author: wwlpublish
-  ms.author: tonyj
+  ms.author: robbarefoot
   ms.topic: unit
 azureSandbox: false
 labModal: false
 durationInMinutes: 3
 content: |
-  [!include[](includes/7-summary-resources.md)]
+  [!include[](includes/6-summary-resources.md)]

…rvices-migration/7-summary-resources.yml …rvices-migration/6-summary-resources.ymllearn-pr/wwl-azure/active-directory-domain-services-migration/7-summary-resources.yml renamed to learn-pr/wwl-azure/active-directory-domain-services-migration/6-summary-resources.yml learn-pr/wwl-azure/active-directory-domain-services-migration/7-summary-resources.yml renamed to learn-pr/wwl-azure/active-directory-domain-services-migration/6-summary-resources.yml

@@ -1,4 +1,4 @@
-The first step in moving your organization’s Active Directory Domain Services domain controllers to Windows Server 2025 is to determine whether you want to upgrade your existing domains and forest or migrate to a newly deployed forest. If you decide to upgrade your existing domains and forest, you need to know the steps required to introduce and then switch over to Windows Server 2025 domain controllers. If you’re going to migrate to a new forest, you need to know which steps to take to move between your existing AD DS environment and your new one.
+The first step in moving your organization’s Active Directory Domain Services domain controllers to Windows Server 2025 is to determine whether you want to upgrade your existing domains and forest or migrate to a newly deployed forest. If you decide to upgrade your existing domains and forest, you need to know the steps required to introduce and then switch over to Windows Server 2025 domain controllers. 
 
 ## Learning objectives
 
@@ -7,7 +7,6 @@ In this module, you will:
 - Compare upgrading an AD DS forest and migrating to a new AD DS forest.
 - Describe how to upgrade an existing AD DS forest.
 - Describe how to migrate to a new AD DS forest.
-- Describe Active Directory Migration Tool (ADMT).
 
 ## Prerequisites
 

learn-pr/wwl-azure/active-directory-domain-services-migration/includes/1-introduction.md

@@ -12,9 +12,11 @@ After planning is complete, you can create the new AD DS forest by using new dom
 
 To support a phased migration that allows users to access resources in the source and destination, you must configure a forest trust. This allows users in the source forest to access resources migrated to the target forest. It also allows users migrated to the target forest to access resources in the source forest.
 
-After a user is migrated to the target forest, the sIDHistory attribute is used to maintain access to resources in the source forest. The sIDHistory attribute on the migrated user is updated to include the security identifier (SID) of the source user. This allows the migrated user to access resources in the source forest to which the source user had been assigned access. Populating sIDHistory allows the new migrated user to impersonate the source user for security purposes.
+After a user is migrated to the target forest, the sIDHistory attribute is used to maintain access to resources in the source forest. The sIDHistory attribute on the migrated user is updated to include the security identifier (SID) of the source user. This allows the migrated user to access resources in the source forest to which the source user had been assigned access. Populating sIDHistory adds the source user's SID to the migrated user's security token, allowing the migrated user to retain access to resources previously granted to the source user.
 
-To use sIDHistory, you must disable SID filtering on the forest trust. SID filtering removes SIDs from the local domain that weren't issued by a domain controller in the local AD DS forest.
+To use sIDHistory, you must disable SID filtering on the forest trust. SID filtering is a security feature that removes SIDs from an incoming user's authentication token that don't originate from the trusted forest. Because the sIDHistory SIDs originate from the source forest but are carried in the migrated user's token from the target forest, SID filtering would strip them and prevent access to source forest resources.
 
 Password synchronization is another important part of migrating. To simplify the migration process for users, you should migrate passwords along with the user accounts.
 
+> [!NOTE]
+> Many organizations choose to engage a Microsoft Partner or third-party vendor to assist with complex forest migrations. These engagements can provide specialized expertise and tooling to help ensure a successful migration with minimal disruption to business operations.