In this post we will install the Mobility Service agent on our Classic VM and touch on the networking challenges we have with this design.
The Process Server is the most important component in a deployment like ours. It is the one responsible for handling all compute and IO intensive aspects of replication and maintaining replication policies, replication status and health reports.
About two weeks ago, Azure Site Recovery (ASR) V2 was released to preview. Using the “Unplanned Failover” we can perform ASM (Classic / V1) VM to Azure Resource Manager (ARM) VM conversion.
About a week ago Veeam introduced “Direct Restore to Azure”. In the last couple of days, I’ve been playing with it and I have to say I was surprised to see how easy it is to take a backup file and make an Azure VM out of it.
Lately I’ve been playing around with Azure DevTest labs. This is a great way for provisioning rapidly deployed policy-driven environments in Azure for developers, testing, QA, DevOps and other teams in the organization.
In the previous posts I showed you how to deploy Azure Active Directory Services as a Service. Rather you did this just for fun or for a PoC, there is always the possibility to undo and delete the domain.
Now that we have set the stage, let’s take an Azure virtual machine and make it a member in our new “onmicrosoft.com” domain.
I have to say, since joining Microsoft I talk “as-a-Service” almost every day. Among all of the cool PaaS capabilities you will find Azure Active Directory (AAD). Before diving in, let’s all be on the same page here – I’m not going to deploy any domain controller or run DCPROMO on a VM god forbidden, it is all about the PaaS ladies and gents 🙂 .