Skip to content

Commit 6ef9f19

Browse files
committed
[AzureADDS] Clean and cross-link migration how-to
1 parent c8a47b5 commit 6ef9f19

File tree

1 file changed

+2
-16
lines changed

1 file changed

+2
-16
lines changed

articles/active-directory-domain-services/migrate-from-classic-vnet.md

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ ms.author: iainfou
1717

1818
Azure Active Directory Domain Services (AD DS) supports a one-time move for customers currently using the Classic virtual network model to the Resource Manager virtual network model. Azure AD DS managed domains that use the Resource Manager deployment model provide additional features such as fine-grained password policy, audit logs, and account lockout protection.
1919

20-
This article outlines the benefits and considerations for migration, then the required steps to successfully migrate an existing Azure AD DS instance.
20+
This article outlines considerations for migration, then the required steps to successfully migrate an existing Azure AD DS instance. For some of the benefits, see [Benefits of migration from the Classic to Resource Manager deployment model in Azure AD DS][migration-benefits].
2121

2222
> [!NOTE]
2323
> In 2017, Azure AD Domain Services became available to host in an Azure Resource Manager network. Since then, we have been able to build a more secure service using the Azure Resource Manager's modern capabilities. Because Azure Resource Manager deployments fully replace classic deployments, Azure AD DS classic virtual network deployments will be retired on March 1, 2023.
@@ -38,21 +38,6 @@ In the *migration* stage, the underlying virtual disks for the domain controller
3838

3939
![Migration of Azure AD DS](media/migrate-from-classic-vnet/migration-process.png)
4040

41-
## Migration benefits
42-
43-
When you move an Azure AD DS managed domain using this migration process, you avoid the need to rejoin machines to the managed domain or delete the Azure AD DS instance and create one from scratch. VMs continue to be joined to the Azure AD DS managed domain at the end of the migration process.
44-
45-
After migration, Azure AD DS provides many features that are only available for domains using Resource Manager virtual networks, such as:
46-
47-
* Fine-grained password policy support.
48-
* AD account lockout protection.
49-
* Email notifications of alerts on the Azure AD DS managed domain.
50-
* Audit logs using Azure Monitor.
51-
* Azure Files integration
52-
* HD Insights integration
53-
54-
Azure AD DS managed domains that use a Resource Manager virtual network help you stay up-to-date with the latest new features. Support for Azure AD DS using Classic virtual networks is to be deprecated in the future.
55-
5641
## Example scenarios for migration
5742

5843
Some common scenarios for migrating an Azure AD DS managed domain include the following examples.
@@ -364,6 +349,7 @@ With your Azure AD DS managed domain migrated to the Resource Manager deployment
364349
[troubleshoot-sign-in]: troubleshoot-sign-in.md
365350
[tshoot-ldaps]: tshoot-ldaps.md
366351
[get-credential]: /powershell/module/microsoft.powershell.security/get-credential
352+
[migration-benefits]: concepts-migration-benefits.md
367353

368354
<!-- EXTERNAL LINKS -->
369355
[powershell-script]: https://www.powershellgallery.com/packages/Migrate-Aadds/

0 commit comments

Comments
 (0)