Nice and simple, right? I like to call this a “Ned-proof” feature in my specs ;). WAC is calling actual Azure REST provisioning APIs here, just like the portal itself would. But WAC can also add its own business logic, making these workload-based deployments richer. And of course, you always stay in the consistent WAC experience, which reduces your training and procedure burdens.
The requirements for using WAC and SR to create Azure VMs are straightforward:
- An Azure subscription
- A Windows Admin Center gateway registered with Azure
- An existing Azure resource group where you have Create permissions.
- An existing Azure Virtual Network and subnet.
- An Azure Express Route or Azure VPN solution tied to the virtual network and subnet that allows connectivity from Azure VMs to your on-premises machines.
Remember, this isn’t a preview – it’s shipped!
I hope you’ve enjoyed learning about this new feature, it’s going to save some of your organizations someday. If you have questions, hit me up on twitter or DM me on TechCommunity.
- Ned Pyle