A session host shows Unavailable and NotRegistered in the host pool. The last heartbeat was 45 minutes ago. You need to restore registration without redeploying the VM. What are two appropriate first actions? (Choose two.)

When a session host shows as Unavailable and NotRegistered, it indicates a communication issue with the Azure Virtual Desktop service. The first step is to check network connectivity. Verifying outbound connectivity to Azure Virtual Desktop service endpoints over TCP 443 ensures the session host can reach the necessary Azure services. If connectivity is confirmed, the next logical step is to restart the core Azure Virtual Desktop agent services (RDAgent and RDAgentBootLoader) on the VM. This often resolves transient issues with the agent's registration process. Generating a new registration token and reinstalling the agent is a more drastic step, usually reserved for when simpler troubleshooting fails, as it's more disruptive. Redeploying the network interface is unlikely to resolve an agent registration issue unless there's a fundamental network configuration problem, which isn't indicated. Disabling the firewall is a security risk and should only be done as a temporary diagnostic step, not a primary solution, and often connectivity issues are due to outbound blocks, not inbound.