There are two kinds of Azure RemoteApp collections: Cloud Collections and Hybrid Collections. Each has its own different network and authentication options and advantages and disadvantages. In this movie I'll compare and contrast them to help you decide which is best for you.
- [Voiceover] There are two kinds of Azure RemoteApp collections, Cloud collections and Hybrid collections. Each has its own different network and authentication options and advantages and disadvantages. So let me review these now. First, you have Cloud collections. These reside completely in Azure in the cloud. Users access apps by logging in with their Microsoft account or corporate credentials, synchronized or federated with Azure Active Directory. You can choose to save all the data in the cloud or to connect to your collection to a VNET and save data there.
The other option is a Hybrid collection. These are hosted in and stored data in the Azure cloud but also let users access data and resources stored on a local network. Users can access apps by logging with their corporate credentials, synchronized or federated with Azure Active Directory, just as you could with Cloud. In these collections you create and upload a custom Windows server already a session host with your own set of client applications. You want to choose a Cloud collection when the applications you wanna share do not require connection to any resource on your company's private network, for example, through a VPN device.
Now if the application uses resources on the internet, OneDrive or Azure, a Cloud collection will work well for you. It's also the quickest to create. Cloud collections are ideal for small businesses that only need access to Office365 Pro Plus or perhaps Office 2013 applications, but don't want to support the operating system or any of the applications. Other advantages of a Cloud collection are Microsoft will make all the updates of the software, this includes the operating system and the apps.
Microsoft will protect you against malware. And these are simple to set up and very simple to use. There's no need to domain join the RDS servers to an Active Directory. And this option leverages Azure infrastructure. The disadvantages to using a Cloud collection include limited application support. You cannot install additional applications as you want. This is for public internet access only, and RemoteApp client is not supported in Windows 7.
A Hybrid collection is useful if you require connection to resources such as a file server or database behind a firewall on your company's private network. Hybrid collections are also great when you need to publish a custom set of applications that run in a domain joined environment and have access to on-premises resources over a site-to-site VPN. These collections are more useful for large companies with lots of resources on their private networks that can't be moved to the cloud.
Other advantages of Hybrid collections include, you can use custom applications, you can domain join the RDS servers, these will leverage also Azure's infrastructure, and it also supports connecting site VPNs to Azure cloud. Disadvantages of a Hybrid collection, there's many requirements for creating them, updating the template image can be painful, you cannot use virtual instances in Azure to build template images, template images must be on a VHD file and it does not support VHDX, the VHD for the template image must not be a generation 2 vertual machine, and there are very many, many requirements that you can look on the Microsoft documentation area to see.
And again the RemoteApp is not supported in Windows 7. As your RemoteApp supports both Microsoft accounts and Azure Active Directory accounts, but not all collections support all methods. With Cloud collections, you can use Microsoft accounts as your AD accounts or a mix of the two, use the accounts that work best for your users. There are also no specific requirements for using Microsoft accounts. If you do want to use an Azure AD account, you'll need to make sure that your Azure AD tenant matches the one associated with your subscription.
You can also use Azure AD plus on-premise Active Directory, and this is actually a prerequisite for a Hybrid collection, another advantage of maybe going with a Cloud collection is you do not have this requirement. You will need to use AD Connect to integrate the two directories. Lots of information here, so if you need additional information for determining what kind of collection you need for Azure RemoteApp, you can access this document on the Microsoft website. It goes over quick references between the collection types, which I've summarized here.
Reviews Cloud collections, Hybrid collections, authentication options, Cloud and Cloud + VNET, more about Hybrid and combining cloud with Azure AD + AD. Notice there's lots of links here for getting more information about each of these topics.
Note: This course maps to the "Manage apps" domain of the Configure Windows Devices exam 70-697.
- Deploying via Azure RemoteApp
- Setting up cloud, cloud + VNet and hybrid collections
- Publishing RemoteApp apps
- Understanding real-world uses for RemoteApp
- Deploying and managing mobile apps with Intune
- Deploying virtual machines with Hyper-V