So you finally got your trial approved for RemoteApp and thought you’d connect your RemoteApp virtual network to the rest of your infrastructure in Azure? Well, I stepped in that pile too. But solved it in the usual way, with PowerShell and the new multi-vnet Configuration ability.
You need at least one existing virtual network, and you need to configure a virtual network in the RemoteApp part of the portal.
Click RemoteApp -> Virtual Networks -> Create
Enter a name for your network and select region.
Enter the address space you want for your RemoteApp server(s) and the address space for your local networks. With local networks I mean either your on-premises network or the other networks you have defined in Azure. In my case I’ll be connecting my RemoteApp network to my other networks in Azure.
Enter the DNS-servers you want your RemoteApp server to receive from DHCP. This is so your applications can resolve your local hostnames, for SQL connectivity or any other type of traffic. You also need to specify the address of the VPN device. I’ve entered the address to my gateway in Azure. If you’re connecting multiple virtual networks you MUST select “Dynamic” for VPN gateway type. Static routing only works between two networks in Azure.
Network created, now waiting for VPN Configuration.
Now we’ll click on “Manage key” and copy the address for the gateway. You might as well copy the key to a notepad file while you’re at it.
Add your RemoteApp network as a local network in the “Networks” part of the portal. Specify the gateway address you just copied.
When it’s saved, export the network configuration from the portal. Open the XML-file and edit the corresponding Virtual network, adding a connecction to your newly created “local” network. Mine is named RemoteAppVnet as you can see below.
Import your configuration to Azure. Networks -> New -> Network Services -> Import configuration
Once your information is imported you’ll see your new network as “Not connected” in the overview in the virtual network.
Open PowerShell (with the Azure cmdlets) and run the following two commands. Substituting the vnetname and local network name and key for your values of course.
Once those are run your networks should be connected and all green!