Azure VM Remote Desktop Can't Connect
<p>Following a how-to book's guide on setting up a VM through the Azure Portal and getting the error when trying to connect </p>

<blockquote>
  <p>Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the service is not enabled 2) The remote computer is turned off [Verified through the Azure Portal it is turned on because Start is faded, while Restart and Stop are not] 3) The remote computer is not available on the network.</p>
</blockquote>

<p>The error occurs before I'm able to enter any credentials - it doesn't find the IP at all.  The RDP file details (IP removed of course):</p>

<pre><code>full address:s:[IPAddress]:3389
prompt for credentials:i:1
administrative session:i:1
</code></pre>

<p>What I've tried:</p>

<ol>
<li>Even though the How-To book doesn't show where/how to specify a port, when I download the RDP file from the <code>Connect</code> option, it specifies the port 3389.  The book seems to imply that simply downloading this file and connecting will work and there's no need to specify the port.  I get the above error.</li>
<li>Flushed DNS on my computer, <code>ipconfig /flushdns</code></li>
<li>In the Network Security Group option for the VM, I verified that port 3389 allowed any source and wasn't specific.</li>
<li><a href="https://azure.microsoft.com/en-us/documentation/articles/virtual-machines-windows-nsg-quickstart-portal/" rel="noreferrer">I did miss associating the subnet part of the Network Security Group to a virtual network</a>, so I did associate my NSG with the default subnet set up for my Virtual Network.</li>
<li>From the <code>Quick start</code> option, I don't see how to connect to this either; I'm guessing, I need to specify a different port, but don't see where to do it here either => <strong>Update: this appears to be in the Network Security Group</strong>'s <em>Inbound security rules</em> in the Azure portal.  </li>
<li><code>Boot Diagnostics</code> option shows the login screen.  A ping to the IP address fails four times with "Request timed out."</li>
</ol>

<p>Note: this is not a <code>Virtual Machine (classic)</code>.</p>