Users intermittently receive the message "We couldn't connect to the remote PC" when launching desktops from a pooled host pool. You need to quickly determine whether failures are due to no available session hosts or transport negotiation issues. Which two actions should you take first? (Choose two.)

To quickly diagnose intermittent connection issues, the most effective first steps are to leverage Azure Virtual Desktop's built-in diagnostic tools. Running "Connection troubleshooting" within the host pool's "Diagnose and solve problems" in the Azure portal provides an immediate, guided analysis of common connection failures, including those related to session host availability or network issues. Simultaneously, querying the Log Analytics workspace for "Connection" category entries offers detailed logs that can pinpoint specific failure reasons, such as "No healthy session hosts" or "Transport negotiation failed." Reviewing the Azure Activity log for create/update operations is less relevant for intermittent user connection failures, as it tracks management plane changes, not runtime connection issues. Re-creating the registration token is a troubleshooting step for hosts failing to register initially, not for intermittent user connection problems on an established host pool. Enabling boot diagnostics is for VM startup issues, not for user connection failures after the VM is running.