feat: add AVD device filtering with optional name‑based override #9
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR introduces flexible Azure Virtual Desktop (AVD) device filtering to the Export-IntuneManagedDevices script.
What’s New
-AVDDevicesswitch to enable filtering for both AVD single-session and multi-session hosts.-AVDUniqueIdentifierparameter to support tenant-specific naming conventions.model = "Virtual Machine".-AVDUniqueIdentifieris provided, the script filters devices by matching the identifier withindeviceName.Why This Matters
Intune does not consistently expose
operatingSystemEditionfor AVD hosts, making OS-based filtering unreliable.This update provides a predictable and tenant-agnostic way to target AVD devices while still allowing precise overrides when naming conventions are available.
Backward Compatibility
-AVDDevicesis explicitly used.Testing