AZ-100, AZ-101 and AZ-102 are all ceasing in favour of the AZ-103 single exam. See the link to the new exam syllabus – here
After a friend on Reddit posted the recent Ignite video for the AZ-100 exam, I went looking for the AZ-101. As before, it would be a good idea to start here and hear from the horses mouth before starting on your journey.
Evaluate and perform server migration to Azure (15-20%)
From an Azure service perspective, this module is three services;
Evaluate = Azure Migrate
Perform = Azure Site Recovery into an Azure Recovery Services Vault
Azure Migrate does the cost and technical analysis about how much your invoice for the workload will be once it’s in Azure and whether the chosen workloads are compatible with Azure.
Azure Site Recovery is the (source) which is used to protect the workload and facilitate the migration piece, which is a failover operation executed from the Recovery Services Vault (destination) blade which never fails back to the source site.
Evaluate migration scenarios by using Azure Migrate
Azure migrate is focused on analyzing workloads for migration into Azure and is currently constrained to VMware vSphere analysis. Azure Site Recovery Deployment Planner is used for other workloads.
As I write this, I cannot see any PowerShell that drives Azure Migrate using the AzureRM module. The new AZ module may include commands but for the exam in the early part of 2019, I don’t believe the AZ command set will be in scope, yet. See the AzureRM to AZ annoucement here.
May include but not limited to:
Discover and assess environment;
Azure Migrate projects are now available in Europe and Asia, rather than just the US. The Azure Migrate project isn’t “where your VMs go”, it’s just where the analysis of your assessment is done.
Identify workloads that can and cannot be deployed;
Recent changes to Azure Site Recovery allow Windows 2012R2 and later VMs that are using a UEFI boot type to be converted to BIOS as part of the migration. Sadly though, everything else is still unsupported if the VM boot type is UEFI, for now.
Identify ports to open;
This is very simple in that TCP/443 is your friend, unless you’ve configured custom ports on your on-premises vSphere vCenter server.
Identify changes to network;
This is tough to interpret and the only text that works for me is the work that you might do in the migration stage around changes to the VMs network interfaces or Windows Firewall. Can you imagine doing all the work and the Windows Firewall is blocking RDP requests from the Internet on the “Public” profile? It’ll all be there, it’s just there’s some local config rejecting your connection attempts. In addition, the previous link about opening ports should suffice.
Identify if target environment is supported;
This is really difficult to interpret, but my assumption is that this page best fits.
Setup domain accounts and credentials;
Migrate servers to Azure
Recovery Services Vaults provide data services for protection and recovery. Azure Site Recovery, which gets deployed in the environment where the workload resides, includes technology that was part of an acquisition by Microsoft in 2014.
May include but not limited to:
Migrate by using Azure Site Recovery (ASR);
There are many PowerShell commands for the Azure Site Recovery service. The current module for the AzureRM seems to be AzureRM.SiteRecovery.