Integrations

We enabled SSO with Microsoft Entra. It still requires us to manually create the user within Huntress before they can login. Many other applications that we integrated have an "auto provision" setting. When enabled this will automatically create the user in Huntress as long as they're part of security group on the Entra Enterprise Application. Some of the better ones even have mapping logic where you can map specific Entra Groups to specific permissions on the application (huntress) side.

An additional integration option for event updates that initiates a HTTPS callback and posts detailed JSON data about the event. It will allow faster response and wider range of integration options and much more preferable then having to parse an email.

Rather than email the admins, open a ticket in our PSA so that it will be resolved faster

Ability to create email integrations at the organization level so incident reports for certain organizations will be sent to them and not the account level emails.

If we're syncing once per month, but want to add a new customer and sync now the current integration will sync all customers which with automated installs and new device installs will create pro-rated updates to customer billing. To avoid the above it would be ideal if there was the ability to select which customers to sync.

Currently the Halo integration can create tickets/alerts but we cannot respond or close from Halo, Can this be expanded to a 2-way communication so our agents can work / close items in Halo instead of needing to close the Halo ticket and the huntress ticket separately.

Being able to synchronize with Active Directory computer objects would allow us to easily determine which computers are missing Huntress. Also, computers in the Huntress dashboard could automatically be removed, allowing for easy dashboard management and license control.

You now close tickets for incidents, but please can you also close automatically tickets for escalations and unwanted access when resolved.

When configuring the billing integration and hitting sync it syncs based on the time the sync occurs. It would be great to be able to define the start date for billing when first setting up the sync.

Great to have this integration built. We have one request. Can Huntress add the mapping of priorities? We would like to match the Huntress "Critical, High and Low" with ticket priorities in HaloPSA. This would help flag critical and high events more quickly. Thanks!