After the local virtual machine migration to Azure, you will not have problems remote connections. Of which there are two main problems, one is not assigned a public IP address mentioned in the previous article. Another problem is the inbound rule is not running RDP connection. By default, migrated from the local to the computer Azure, there is no public IP address assigned, nor associated with network security group and run RDP create inbound rules.
1. Create a network security group
If your local computer migrate resource groups to Azure, where there is no network security group, you must first create a network security group. Open the resource group is located, click Add.
Select the network in the network security group
Enter a name, select the region Click + Create
After verification by clicking New
2, associated with a network interface
After clicking association created in network interface
Select the network interface you want to associate
3, add inbound rules
VM - Network - Adding an inbound port rules
Source and destination, enter the destination port, click Add
At this point, you can locally remote computer, the Azure migration will also be able to remotely connected. However, even if there is no public IP, which can be managed remotely turn off the virtual machine by Azure service fort, later during this presentation.