You have an AVD host pool (Pool1) with three session hosts and need to implement a private endpoint connection for the pool. Which two actions should you perform?

To implement a private endpoint for an Azure Virtual Desktop (AVD) host pool, two key actions are required. First, you must reregister the Microsoft.DesktopVirtualization resource provider for your Azure subscription. This ensures that the necessary features and configurations for private endpoint integration with AVD are enabled and up-to-date. Second, you create the private endpoint itself, specifically using the connection target sub-resource. This sub-resource is designed for establishing private connectivity to AVD services. Incorrect options: Creating a private endpoint with the global target sub-resource is incorrect because AVD private endpoints use specific sub-resources like connection. Reregistering Microsoft.VirtualMachineImages is irrelevant to AVD private endpoint connectivity; it pertains to image management. Creating a private endpoint with the feed target sub-resource is incorrect as feed is not the appropriate sub-resource for AVD host pool connections; connection is.