Hybrid Azure Active Directory joined

This article describes the requirements to create Hybrid Azure Active Directory (HAAD) joined catalogs using Citrix DaaS in addition to the requirements outlined in the Citrix DaaS system requirements section.

Hybrid Azure AD joined machines use on-premises AD as the authentication provider. You can assign them to domain users or groups in on-premises AD. To enable Azure AD seamless SSO experience, you need to have the domain users synced to Azure AD.

Note:

Hybrid Azure AD joined VMs are supported in both federated and managed identity infrastructures.

Requirements

• Control plane: SeeSupported Configurations
• VDA type: Single-session (desktops only) or multi-session (apps and desktops)
• VDA version: 2212 or later
• Provisioning type: Machine Creation Services (MCS), Persistent and Non-persistent
• Assignment type: Dedicated and pooled
• Hosting platform: Any hypervisor or cloud service

Limitations

• If Citrix Federated Authentication Service (FAS) is used, single sign-on is directed to on-premises AD rather than Azure AD. In this case, it is recommended to configure Azure AD certificate-based authentication so that the primary refresh token (PRT) is generated upon user logon, which facilitates single sign-on to Azure AD resources within the session. Otherwise, the PRT will not be present and SSO to Azure AD resources will not work. For information on achieving Azure AD single sign-on (SSO) to hybrid joined VDAs using Citrix Federated Authentication Service (FAS), seeHybrid-joined VDAs.
• 不要跳过形象准备在创建或dating machine catalogs. If you want to skip image preparation, make sure the master VMs are not Azure AD or Hybrid Azure AD joined.

Considerations

• Creating hybrid Azure Active Directory joined machines requires theWrite userCertificatepermission in the target domain. Make sure that you enter credentials of an administrator with that permission during catalog creation.

• The hybrid Azure AD joining process is managed by Citrix. You need to disableautoWorkplaceJoincontrolled by Windows in the master VMs as follows. The task of manually disablingautoWorkplaceJoinis only required for VDA version 2212 or earlier.

  1. Rungpedit.msc.
  2. Navigate toComputer Configuration > Administrative Templates > Windows Components > Device Registration.
  3. SetRegister domain joined computers as devicestoDisabled.

• Select the Organizational Unit (OU) that is configured to be synced with Azure AD when you create the machine identities.

• For Windows 11 22H2 based master VM, create a scheduled task in the master VM that executes the following commands at system startup using SYSTEM account. This task of scheduling a task in the master VM is only required for VDA version 2212 or earlier.

  $VirtualDesktopKeyPath = 'HKLM:\Software\AzureAD\VirtualDesktop' $WorkplaceJoinKeyPath = 'HKLM:\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin' $MaxCount = 60 for ($count = 1; $count -le $MaxCount; $count++) { if ((Test-Path -Path $VirtualDesktopKeyPath) -eq $true) { $provider = (Get-Item -Path $VirtualDesktopKeyPath).GetValue("Provider", $null) if ($provider -eq 'Citrix') { break; } if ($provider -eq 1) { Set-ItemProperty -Path $VirtualDesktopKeyPath -Name "Provider" -Value "Citrix" -Force Set-ItemProperty -Path $WorkplaceJoinKeyPath -Name "autoWorkplaceJoin" -Value 1 -Force Start-Sleep 5 dsregcmd /join break } } Start-Sleep 1 } 

Where to go next

For more information on creating Hybrid Azure Active Directory joined catalogs, seeCreate Hybrid Azure Active Directory joined catalogs.