Nick Gusto
A partner managing Huntress Managed Microsoft Defender exclusions ran into significant usability issues while trying to add 2 endpoints to roughly 12 existing exclusions in a single org. In its current form, this workflow is highly manual and does not scale well for real-world administration.
--
Current pain points:
  • Managed Exclusions are currently scoped only at the account, organization, or endpoint level; there is no way to target exclusions by machine type, tag, or group.
  • The partner wants to apply exclusions to a subset of systems within an org, such as a logical grouping like FSLogix hosts, without having to manage each endpoint individually.
  • Editing exclusions appears to be effectively one-at-a-time for this workflow, making repetitive changes across many exclusions slow and frustrating.
  • After each edit, the UI resets filters, forcing the admin to re-find their place and repeat the same navigation over and over.
  • The partner explicitly described this as one of the worst UX experiences they have had in a long time, which suggests this is more than a minor inconvenience and is likely to create friction for larger or more mature environments.
--
Public API support for Managed Exclusions
Expose Managed Exclusions management through the Huntress API so partners can automate:
  • Listing exclusions
  • Creating exclusions
  • Updating exclusion scope
  • Bulk assigning endpoints
  • Removing endpoints from exclusions
This would allow partners to automate repetitive changes that are currently manual in the UI.