Connecting to a VM

Connecting to VM

1. By default, only RDP and Remote Powershell is enabled.

2. To connect to anything else, you must enable EndPoints. When you are creating an endpoint, you are actually creating a mapping in Azure Loadbalancer to your VM on a port.

3. Your virtual machine is provisioned with a virtual ip address for external communication (via the internet) and another ip address for internal communication (via the load balancer)

a. A public-facing Virtual IP

• Internet Visible so that you can point a DNS record to
• Available to you as long as you do not shut down the machine
• Reserved IP Address
• Permanently associated with your subscription
• 5 reserved IP addresses per subscription
• Only way to do through is powesrshell

b. A private IP for communication internal to Azure

• Used by load balancer to route requests in load balancing scenario
• Used by VMs in a Virtual Network to communicate with each other
• Static IP Address
• Private IPs that are permanently associated with your subscription
• Only available for VMs inside of Virtual Networks

c. Problem: Not sticky to your subscription