Let’s see classic architecture, it uses a container called a Cloud service and this is ultimately what’s exposed to the public internet. The cloud services interact with the Azure load balancer. The cloud service is going to have a virtual IP address that’s public and again connectable, theoretically, from anywhere in the world. That connection is called an endpoint and you’re going to create endpoint rules to allow only the types of traffic into your cloud service that you need. By default, in Windows, that’s going to be 5986, the PowerShell remoting port, and you’ll also want 3389 for remote desktop protocol. Now, a big problem with Azure service management is that if you just go in and try to create a VM, you might get all hosed up because you realize, whoops, I must make sure to create a virtual network to attach the VM to.
You can look at binary large object, or blob storage, as Dropbox or OneDrive. It’s a Cloud-based storage service that’s simply going to be host to your virtual hard disk files or vhd files.
As a matter of fact, let me just say explicitly that the Azure virtual machines are, in fact, Hyper-V VMs and they’re running on an abstracted Hyper-V platform. So you see, ultimately, you create your VM within a Cloud service. It’s going to have a private IP address that’s associated with your subnet. Its virtual hard disk is going to be stored in a storage account and the Cloud service is what connects to the outside world via endpoints.
