I've used this feature a few times now and find the additional built in VM scheduling features really useful, as these are the types of environment that really don't need to be up all the time (yes I know there are a bunch of ways to do that with regular VMs too!).
Anyway, for some reason, probably trying to multitask, I ended up adding a bunch of VMs to the Resource Group directly, rather than via the DevTest blade in the Azure Portal, which resulted in the VMs not really being associated with the DevTest group properly. I guess there might be a way to get them to show up but it didn't seem obvious, so I'll just re-deploy properly. Here is a diagram of where you should add a VM to a DevTest Lab:
0 comments :
Post a Comment