The name of an Azure virtual machine resolves through global DNS to a virtual IP (VIP) under the cloudapp.net domain, e.g. vmname.cloudapp.net. The VIP connects a client through the internet to endpoints mapped for specific ports to internal ports on the VM. VIP addresses are dynamically-assigned to the global virtual machine name, but are constant as long as the virtual machine continues to run.
There is no automatic means to resolve an Azure VM's global name or internal hostname to its internal IP address; and while Azure virtual networks provide the ability to configure the IP of a custom DNS so VM clients can register their internal IPs via DDNS, SnapCLOUD does not currently support DDNS. To reliably resolve a SnapCLOUD hostname to its internal IP address for access through its virtual network, create static host records in your organization's DNS. Azure VM internal IPs are generally assigned by virtual network DHCP with a many-years-long lease so they don't change as long as the VM continues to run; otherwise there are other means to assign static IPs to Azure VMs including SnapCLOUD.