Most of these customers are standing up the full XenApp and XenDesktop Service. However, our Citrix Cloud Services all have the same basic needs for any customer:
- Azure Subscription (for workers and infrastructure)
- App Registration (this is an Azure Tenant service account for our cloud based control plane to perform worker lifecycle events within a subscription)
- Virtual Network (the machines need IP addresses)
- Active Directory (there is a much larger discussion here, but either a read / write Domain Controller VM or the Azure Active Directory Domain Service will work)
- The DNS setting for the Virtual Network must be your Active Directory
- Cloud Connector machines (the connection between the machines in the subscription and the control plane)
- Some type of 'golden' image that is provisioned into the worker machines your end customers get their work done on.
Growing this conversation from the bottom up;
Each customer of Azure has at least one Azure Tenant.
This is your account in Azure. It is the highest level of connection between Azure and you the customer.
Within your Azure Tenant you have Subscriptions.
Subscriptions are billing boundaries and service boundaries (services within subscription cannot 'talk' to each other without extra work, as if they are in different buildings).
Isolating Citrix Cloud in your tenant;
Can you isolate Citrix Cloud to its own Subscription in your Azure Tenant? Yes! And that is actually the topology that I am going to describe here. How to isolate Citrix Cloud from your corporate infrastructure.
Common project slow down points that I have heard are: modifications to existing virtual networks and protecting Active Directory.
Focusing on the Virtual Network issue first;
You CAN create a virtual network dedicated to your Citrix Cloud deployment.
The important things to remember are:
- You need a route to your Active Directory
- You must update the DNS settings of the Citrix Cloud virtual network to be the AD
The DNS setting is the most common place where customers trip up. The DNS setting must be set. The Azure default results in the machines not being able to resolve the Active Directory.
The three models as pictures;It is often that pictures tell a story faster and easier, I wanted to provide those to get you started thinking about your individual topology as well.
If your Active Directory is on the same Virtual Network you are most likely golden.
If your Active Directory machine(s) is on a different Virtual Network in the same subscription, you can use peering between the two virtual networks.
If your Active Directory machine(s) is on a different Virtual Network in a different subscription, you must use a gateway between the two virtual networks.