How to: Azure RemoteApp QuickBooks Domain Configuration 

In this step-by-step, I will demonstrate how to configure Azure RemoteApp with a backend infrastructure in Azure in a domain environment. Azure RemoteApp can also be configured for a workgroup environment on Azure see Step-by-Step or you can use your existing on-premise environment. For this article I will be using QuickBooks as the line of business (LOB) application. The database will reside on the backend server (LOB-BE) and the client application will be on the frontend server (LOB-FE). The backend server is Server 2012 R2 VM hosted in Azure. My domain is CanITlob.com. I have installed Azure Active Directory Connect on LOB-BE.

As of January 2016, Azure Remote App is only available via the Classic portal, therefore this step-by-step has been completed in the Classic portal. I will update this as the Azure Remote App functionality is available in the New portal.  You can do this with any application that is supported. For more details about App requirements see https://azure.microsoft.com/en-us/documentation/articles/remoteapp-appreqs/. Detailed information for Azure RemoteApp can be found on the Azure RemoteApp documentation page.

This step-by-step is long and detailed, but please do not let that deter you, as Azure RemoteApp is a great alternative to Remote Desktop Services and is not that difficult to implement. I have broken down the article into 3 sections:

Section 1 – Creating the front and backend infrastructure

Section 2 – Creating the RemoteApp Collection

Section 3 – Configuring and Publishing the Frontend

Let’s get started!

Section 1 – Creating the front and backend infrastructure

As with any infrastructure project (whether it’s on-premise, in the cloud, or a hybrid deployment) planning is the key to success. Azure RemoteApp will require several steps and planning is critical. 

Our process for creating backend infrastructure for Azure RemoteApp will be:

Step 1. Create the virtual network

Step 2. Create and configure the virtual machines

Step 3. Prep the frontend virtual machine

Please note that some best practices, such as only opening specific ports on firewalls, closing endpoints, etc. have not been put into practice for this demo. As always, please follow all best practices regarding security, hardening, and configuration.

To see the full step-by-step guide, please go here.