The host pool documents the configuration of the hosts that will provide the desktops\/applications. Note that a Host Pool resource ID is required to create an Application Group.<\/p>\n Note, the VMs themselves are deployed using a linked template when you use the Azure Portal. My deployment used the “managed disks” template<\/a>. This template deploys the VMs, runs some DSC, joins the machines to your domain. There is also a task to update the host pool.<\/em><\/p>\n The result of running Microsoft.DesktopVirtualization\/hostpools does not create the VMs – it just manages any VMs added to the Host Pool.<\/p>\n The mandatory properties appear to be:<\/p>\n The full set of properties can be found in the REST API documentation<\/a>.<\/p>\n The Application Group documents the applications, user associations (the Desktop Virtualization User role is assigned to users\/groups), and is associated with a Host Pool; therefore you must deploy a Host Pool resource before<\/em> you deploy the planned Application Group.<\/p>\n The mandatory values appear to be:<\/p>\n We know that Windows 365 (AKA “Cloud PC”) is built on Azure Virtual Desktop. Proof of that is in ARM, with a true\/false property called cloudPcResource.<\/p>\n The REST API documentation<\/a> has complete documentation of the properties.<\/p>\n The Azure Virtual Desktop Workspace is the glue that holds everything together. The Workspace can be associated with no, 1, or many Application Groups via a non-mandatory array value called applicationGroupReferences. You can build a Workspace before your Application Groups and update this value later. Or you can build the (1) Host Pool(s), (2) Application Group(s), followed by the Workspace.<\/p>\n The mandatory values appear to be:<\/p>\n The Host Pool will require virtual machines; these are created as a separate deployment. There’s nothing special here; they are virtual machines created from the Marketplace or from your own generalised image (captured or Shared Image Gallery). Two actions must be done to the VMs:<\/p>\n<\/div>\n AAD, AADDS, or ADDS? I prefer ADDS. This is because:<\/p>\n In this post, I will document the resources used in Azure Virtual Desktop, what they do, and how they interconnect. This is a work-in-progress, so any updates I discover along the way will be added. You should also check out a similar post on Azure Image Builder. Host Pool – Microsoft.DesktopVirtualization\/hostpools The host pool documents … Continue reading “Understanding the Azure Virtual Desktop Resources”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":19045,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_wpcom_ai_launchpad_first_post":false,"footnotes":""},"categories":[5],"tags":[161,251,478],"class_list":["post-22398","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure","tag-arm","tag-azure-resource-manager","tag-azure-virtual-desktop"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t![\"\"](\"https:\/\/aidanfinn.com\/wp-content\/uploads\/2021\/07\/AzureVirtualDesktop.png\")
<\/a><\/p>\nHost Pool – Microsoft.DesktopVirtualization\/hostpools<\/h2>\n
\n
Application Group – Microsoft.DesktopVirtualization\/applicationgroups<\/h2>\n
\n
Workspace – Microsoft.DesktopVirtualization\/workspaces<\/h2>\n
\n
Virtual Machines<\/h2>\n<\/li>\n<\/ul>\n
\n
\n