Citrix DaaS™ for Microsoft Azure

September 6, 2025

Contributed by:

C A

With Studio, you can deploy and manage virtual apps and desktops on Microsoft Azure. Detailed steps are as follows:

Sign in to Citrix Cloud.
Click on the DaaS tile to open Studio.
Deploy virtual apps and desktops using one of these workflows:
- Quick Deploy > Microsoft Azure (recommended for fast, guided deployment). For more information, see Quick Deploy for Microsoft Azure.
  
  Note:
  
  To perform advanced configurations or management options for your deployment, use the Studio related nodes. For more information see Studio.
- Studio (recommended for advanced configuration requirements). For more information, see Get started: Plan and build a deployment.

For more information about the difference between the Quick Deploy and the Studio workflows, see the following section.

Quick Deploy for Microsoft Azure

In Studio, the Quick Deploy > Microsoft Azure interface offers fast deployment of apps and desktops when you’re using Microsoft Azure to host your desktops and apps. This interface offers basic configuration, without advanced features.

With Quick Deploy, you can:

Provision virtual machines and catalogs that deliver desktops and apps hosted in Microsoft Azure.
Create Remote PC Access catalogs for existing machines.

For more information, see Citrix DaaS Standard for Azure.

Note:

With Quick Deploy, you can use a Citrix-Managed Azure subscription, or your own Azure subscription.

Differences between Quick Deploy and Studio workflows

As an alternative to Quick Deploy, the Studio workflow offers advanced configuration features. See the following table for details.

Feature	Quick Deploy	Studio
Deploy using Azure	Yes	Yes *
Citrix® prepared images available	Yes	No
Simplified user experience	Yes	No

* When using a Citrix Managed Azure subscription, you must use Quick Deploy when creating an image or catalog.

If you’re familiar with using the Studio workflow to create and manage catalogs, Quick Deploy has the following differences:

Different terminology.
- In Quick Deploy, you create a catalog.
- In Machine Catalogs, you create a machine catalog. In practice, it’s often referred to as simply catalog.
Resource location and Cloud Connectors.
- Quick Deploy automatically creates a resource location including two Cloud Connectors when you create your first catalog.
- In the Studio workflow, creating a resource location and adding Cloud Connectors are separate steps that you must complete in Citrix Cloud before creating a catalog.
Images used to create catalogs.
- Quick Deploy offers several Citrix prepared images of Windows and Linux machines. You can use these images to create catalogs.
  
  You can also use these images to create images and then customize the new images to suit your unique deployment needs. This feature is known as the image builder. You can also import images from your own Azure subscription.
- In the Studio workflow, you customize images from the supported host you’re using. Citrix prepared images are not available.
Catalog displays:
- Catalogs created in Quick Deploy are visible in the Quick Deploy and the Studio section displays.
- Catalogs created in the Studio workflow are not visible in the Quick Deploy display.
Delivery groups:
- You do not create delivery groups in Quick Deploy. In Quick Deploy, you specify the machines, applications, desktops, and users (subscribers) in the catalog.
  
  Citrix automatically creates a delivery group for each Quick Deploy catalog, using the same name as the catalog. That action occurs behind the scenes. You don’t need to do anything to create the delivery group. The delivery group appears only in the Delivery Groups node, not in Quick Deploy.
- In the Studio workflow, you create a delivery group and indicate which machines it contains. Optionally, you also specify applications, desktops, and users. You can also create application groups.
Layout and user interface.
- The Quick Deploy interface has a different layout and style from the Studio workflow. Quick Deploy contains more on-screen guidance.

The interfaces aren’t mutually exclusive. You can use Quick Deploy to create some catalogs, and then use the Machine Catalogs node to create other catalogs.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

Citrix DaaS™ for Microsoft Azure

September 6, 2025

Contributed by:

C A

September 6, 2025

Contributed by:

C A

Citrix DaaS™ for Microsoft Azure

Quick Deploy for Microsoft Azure

Differences between Quick Deploy and Studio workflows

In this article