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 much of a change the first iteration, most customers decide to build out replica domain controllers in Azure after hybrid connectivity is set up. Microsoft even provides an excellent reference architecture surrounding extending your ADDS infrastructure into Azure. The big takeaways are covered in the recommendations section (and we covered some of these pre-requisites during the last blog post). I want to call out a few of the design considerations within this blog post to bring awareness to what winds up deploying if you use my ARM Template:
In working with customers surrounding Azure adoption, there have only been a handful of times when customers chose to build out a cloud island (where nothing talks to on-premises) or built out a brand-new forest in Azure that trusted production (but production did not trust the Azure forest). I would say 85-90% of the time, customers decide to extend their ADDS environment into Azure, as it matches up to where most enterprises land (and where we will be for a bit): hybrid.
Tune in next week as we start exploring the code I have developed so you can start to feel more comfortable with what an automated replica domain controller build looks like using an ARM Template.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.