Microsoft Azure Virtual Desktop
  • 18 Jan 2022
  • 4 Minutes to read
  • Dark
    Light
  • PDF

Microsoft Azure Virtual Desktop

  • Dark
    Light
  • PDF

This connector type allows you to setup a connection to Microsoft Azure Virtual Desktop (ARM or legancy) to consume the applications defined there.

To setup a connection to the Microsoft AVD environment you need to at least have the following information:

  • The URL of the web feed.
  • An username to connect to Microsoft AVD.
  • The password that corresponds with the username.
  • Credential template that can provide the username for the Remote Desktop application.

Credential Template

An template need to exists with verify password on disabled, and the username in the format that will be used for providing the username to the Remote Desktop application. A common format for the username is "${Identity.UserName}".

Details

The “details” screen will ask you to fill in basic information for the connector. The fields available are as follows:

Name Description Required
Name A friendly name for the connector (e.g. Microsoft AVD), the name will help you identify the connector. Yes
Server Satellite Server that hosts this connector No
Method Determines how the connector should be synchronized, the following options are available:
  • On-demand Allows you to choose which attached packages should be updated.
  • Synchronize This option will automatically synchronize your packages with new available information.
No
Direction Determins which direction the connector functions
  • Push Connector will create packages in the connected system.
  • Pull Packages can be created from resources.
No
Publish Determines the package stage will be used to publish the action sets in, by default the following options are available:
  • Development the action sets will be published in the stage “Development”
  • Test the action sets will be published in the stage “Test”
  • Acceptance the action sets will be published in the stage “Acceptance”
  • Production the action sets will be published in the stage “Production”
No
Enabled Determines whether or not a connector is available No
Package name prefix The default prefix for package names, this can be helpful to easily identify all packages originating from a certain connector No
Description A description for the connector No

On-demand

This page is only available on “On-demand” connectors.

Name Description Required
Default package type This option determines the way a package will be created, the following options are available:
  • Managed managed packages have an action set that is locked. You are still able to add new action sets to the package.
  • Unmanaged No locked action sets are added, but the package won’t be eligible for automatic updates.
No

Settings

Name Description Required
Scope The scope of what kind of resources should be synchronized. Yes
Username The username which will be used to import the applications, the identity needs have permissions to read out all the desired applications and desktops. The username should be an Azure AD User Principal Name. Yes
Password The password that should be used for the identity. Yes
Application ID The application ID that should be used for authenitcation (only applies to ARM resources). Yes
Client secret The application client secret that should be used for authenitcation (only applies to ARM resources). Yes
Network Credentials The credential template that will be used to form the username that will be used to start up the Remote Desktop application Yes
Install dependency Add a install dependency to the managed packages No
Use web client when no agent is present If the RDP file should be downloaded or that the web client should be opened in a webbrowser when no agent is present No

Azure Resource Manager

There must be a registered application within the Azure Active Directory with the correct permissions before AVD ARM resources can be synchronized. The registered application may be the Liquit Workspace application that is also used for an Azure identity source.

The registered application should have the "Windows Virtual Desktop" - "User.Access" API permissions in Azure Active Directory. Do not use the "Windows Virtual Desktop Client", as that is a different application. For adding the correct permission, navigate to the desired registered application within the Azure portal and go the tab "API permissions". Click on the button "Add a permission" and select "APIs my organization uses", search for "Windows Virtual Desktop" to find the select the correct API. Choice for "Delegated permissions" to see the "User.Access" permission.

image.png

An admin consent is required for this. When the legacy AVD was used, you could find two versions of "Windows Virtual Desktop", use the one with the Application ID "9cdead84-a844-4324-93f2-b2e6bb768d07".

Releases

This page allows you to define the way snapshots should be created on packages, the following fields are available to define the behavior:

Name Description Required
Publish How to publish the packages by default, the following options are available:
  • Catalog publishes the packages as requestable packages in the catalog.
  • Workspace publish the packages directly to the workspace.
  • Force the packages will be published in the workspace, the user won’t be able to remove them.
No
Enable snapshot retention Enables the more advanced options for snapshots creation No

Remove snapshots older than

Name Description Required
Enabled Enables automatic snapshot removal No
Days The number of days that should have gone by before automatic removal.

Keep number of snapshots

Name Description Required
Enabled Enables perseveration of a number of snapshots No
Count The number snapshots that should be preserved.

Managed Packages

This page shows a list of packages that are managed by this connector.


Was this article helpful?