Musings on Azure VM setups

notes.txt

 
- portal.azure.com has that latest features compared to manage.windowsazure.com
- in portal.azure.com, you got two (2) deployment models: classic and resource-manager.
- resources deployed in classic won't be compatible with those deployed in resource-manager, same thing vice-versa.

on vm's, on opening ports:
- opening ports on manage.windowsazure.com is MANUAL, one-by-one, through your vm's endpoints.
- opening ports on portal.azure.com ALLOWS PORT RANGES, through your vm's network adapter's network security group.
- you can manage both inbound and outbound in your network security group.
- @ https://docs.microsoft.com/en-us/azure/virtual-machines/virtual-machines-windows-nsg-quickstart-portal

on vm's, on subdomain address:
- on manage.windowsazure.com, you get a yourdomain.cloudapp.net, attached to a classic cloud service.
- on portal.azure.com, you won't need cloud services anymore..
- instead, just open "Public IP address/DNS name label", click the link below it..
- redirects you to your ip configuration, which is a page where you can set the following..
- dynamic or static, idle timeout (in minutes), and your preferred dns name label.
- typically, setting "myserver" as your dns name label for a vm in Central US..
- will give you "myserver.centralus.cloudapp.azure.com"
- that means your vm can be accessed on "myserver.centralus.cloudapp.azure.com".