A couple of months ago I published a blogpost describing a cloud-only Azure RemoteApp hybrid deployment. You can find this blogpost here. This blogpost describes a hybrid Azure RemoteApp deployment with the AD Domain Services hosted in Azure IaaS. Based on the recent announcement from Microsoft that Azure AD Domain Services is in preview I wanted to test if this functionality supports a cloud only hybrid Azure RemoteApp deployment without the need of AD domain controllers in Azure IaaS.
The first step is to activate the Microsoft Azure AD Domain Services. This can be done from the Azure Management Portal. Go to your Directory -> Configure and look for this section:
Before you can activate this setting you have to execute the following steps:
- Create a virtual network in Azure in a Region which supports Azure AD Domain Services
- Create a Domain Admin User with a Domain Admins User Group inside the Azure Active Directory
- The next step is to activate the Azure AD domain services:
- Click on Save. The provisioning process should start
- The Next step is to add both AD Domain Controllers to your Azure Virtual Network as a DNS server
The next step is to create a Master Image and prepare and upload the image to Azure RemoteApp. Since the Azure AD Domain Services is a ‘Managed Service’ we cannot configure this domain as we normally do with a hybrid Azure RemoteApp deployment. I only created an extra ‘service’ account which I will use to add the instances to the Azure AD domain. Execute the following steps to create the Azure RemoteApp hybrid collection:
- Create new hybrid collection
- Go into you newly created hybrid collection and configure the ‘Join Local Domain’ section
- Link your Azure RemoteApp image to this collection and afterwards the provisioning proces should start automatically
- When adding users to the collection the following error occurred:
The users created in Azure AD are automatically synced to the Azure AD Domain, but the users are not ‘synced’ users. The user remains a ‘Azure Active Directory’ user. There is a uservoice item in the Azure RemoteApp uservoice system. If you would like to see that Azure AD Domain Services will be supported in the future please vote on this uservoice item.
Update 5-11-2015: Note: In the above scenario I focused on a Cloud Only setup. When you are using an on premise Active Directory to sync users to the Azure AD and then use Azure AD Domain Services with Azure RemoteApp it will work. As Peter Ciszewski explained below Azure RemoteApp is checking if the user is ‘dir synced’, if not those users cannot be added to Azure RemoteApp. With this note I wanted to clarify that Azure RemoteApp can work with Azure AD Domain Services, but then you need another Active Directory.