[Feature]: Expose AVD Registration Status in Get-AzVM or Related Cmdlets

[VuHoang-IT]

Description of the new feature

Summary
In Azure Virtual Desktop (AVD) environments, there is currently no native property exposed via Get-AzVM or related cmdlets that indicates whether a VM is registered to a host pool. This creates a visibility and automation gap for administrators managing large-scale deployments.

Problem

• VMs may exist in a subscription but not be registered to any host pool.
• Detecting unregistered VMs requires manual correlation between Get-AzVM and Get-AzWvdSessionHost, which is brittle and error-prone.
• Tagging strategies are inconsistent and unreliable for this purpose.

Proposed implementation details (optional)

Proposed Solution
Expose a property in Get-AzVM or a related cmdlet that reflects AVD registration status. For example:
"AVDRegistrationStatus": "Registered" | "Unregistered" | "Failed"

Or include metadata such as:

• HostPoolName
• SessionHostStatus
• LastRegistrationTimestamp

Benefits

• Enables native filtering and reporting
• Improves automation and governance
• Reduces operational overhead
• Enhances security posture by identifying unmanaged VMs

Real-World Impact
As an IT professional managing AVD deployments, I’ve repeatedly encountered challenges in identifying which VMs are properly registered. This feature would significantly streamline operations and improve clarity across environments.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT, @ramankumarlive, @ushnaarshadkhan.

[microsoft-github-policy-service]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @Drewm3, @TravisCragg-MSFT, @nikhilpatel909, @sandeepraichura, @hilaryw29, @GabstaMSFT, @ramankumarlive, @ushnaarshadkhan.