Although the Horizon Cloud Service platform relies on Active Directory, you are not required to integrate Horizon Cloud Service with your existing Active Directory environment. You can integrate your Active Directory into Horizon Cloud Service any time you choose. You have the option of using a separate, isolated Active Directory domain that is local to the Horizon Cloud Service desktops and applications.
Choosing an isolated domain is advantageous for the following use cases:
|Technology proof of concept||For an organization to engage in a technology proof of concept without directly integrating your organization’s infrastructure. In a pilot domain, you can set up everything required to test and validate your use cases within a fully sandboxed environment.|
|Organizations with outsourced users||For a large organization that offloads development work to other countries and needs to provide employees with desktops without connecting directly into your organization’s infrastructure. In a pilot domain, you can set up everything those employees need within a fully sandboxed environment.|
|Organizations with seasonal users||For an organization that ramps up two or three times a year for a period of time without adding a large number of desktops in your organization’s Active Directory structure. You can use a separate pilot domain when you need it and discard it when the season is over.|
|Organizations with limited resources||For a smaller organization without much infrastructure, you can use a separate isolated domain to save the cost of building a primary directory services infrastructure.|
See license considerations in the Horizon Cloud Service Level Agreement when implementing an island account.