Inside the Cloud Adoption Framework, the first migration pattern surrounds rehosting workloads. Since rehosting means workloads move out of the primary datacenter and into Azure without making too mu...
Updated Apr 22, 2020
Version 1.0
Blog Post
Hi MartinSca
In the blog, I discuss Availability Sets and my template takes into consideration an Availability Set to start. I also outline the difference between an Availability Zone and an Availability Set + what's required if you deploy 2 domain controllers as an Availability Zone (namely you'd need to factor in a load balancer).
As a role, Active Directory Domain Services replicates well so long as hybrid connectivity is configured correctly and environments can see one another. For example, you can power down a domain controller and so long as you have other domain controllers available, your users can authenticate. So as part of the role, it's already pretty resilient and an Availability Set may be all your company requires. Obviously applications that sit in Availability Zones would require ADDS living in an Availability Zone, but so many customers are still deploying VMs via the portal, by clicking next, next, next (and filling out fields). This is meant to be a quickstart and may not be the right design for everyone. 🙂