Hoxhunt Status

Resolved: This issue is now resolved.

Monitoring: We are still monitoring this issue. Some organization may still experience 500 errors when accessing the Data Inspector in the Insights portal. The issue should be resolved later today. We will provide an update when the issue is resolved.

Monitoring: There is an issue with the Data Inspector on the Insights portal. An error 500 will occur for some organizations. We have released a fix and the issue should be resolved within an hour.

Resolved: We are resolving this incident.

Microsoft has informed Hoxhunt that in order to fix this issue our customers need to start using the require app protection policy. Read about how to migrate from the approved client app Conditional Access grant to the application protection policy grant on Microsoft's article here: https://learn.microsoft.com/en-us/entra/identity/conditional-access/migrate-approved-client-app

If you have previously re-enabled the legacy Exchange Online access tokens, please turn those off again before performing the above migration.

See also our Knowledge Base article on this topic: https://support.hoxhunt.com/hc/en-us/articles/19723438472348--2025-04-Solution-for-the-AADSTS7000024-Inconsistent-broker-application-IDs-reporting-issue-on-Outlook-Mobile

Identified: We are currently investigating an issue with Microsoft where Hoxhunt button on mobile Outlook may not work for some users. After clicking Hoxhunt button, users are presented with a log in dialog. After proceeding through the log in process, the following error may occur:

"Sorry, but we're having trouble signing you in. AADSTS7000024: Inconsistent broker application IDs asserted by incoming credentials."

According to user reports, the issue is not limited to Hoxhunt Outlook add-in.

This incident is a continuation of a previous incident: https://status.hoxhunt.com/incidents/n9bc2z1l546d Unfortunately, the previous solution provided by us in that previous incident does not solve the issue (anymore). Hoxhunt has escalated the issue to Microsoft.

We will provide updates and possible remediatory steps as they become available.

Best regards Hoxhunt Support

Resolved: We have monitored the situation regarding this error and we can see the issue is now resolved. All users can now report emails again using the Hoxhunt add-in. If you are still experiencing issues with reporting emails, please contact [email protected] (the issue is then unrelated to this incident). Thank you for your understanding!

Identified: Our developers have identified the issue and have developed a fix. The changes will go into affect within one hour of now. We will inform via this incident when the issue should be completely resolved.

Investigating: We are investigating an issue where reporting emails using the Hoxhunt add-in currently results in the following error: Hoxhunt backend returned error with code 401 - We will provide updates on the incident as our investigation progresses

Resolved: We have monitored the situation regarding this error and we can see the issue is now resolved. All users can now report emails again using the Hoxhunt add-in. If you are still experiencing issues with reporting emails, please contact [email protected] (the issue is then unrelated to this incident). Thank you for your understanding!

Identified: Our developers have identified the issue and have developed a fix. The changes will go into affect within one hour of now. We will inform via this incident when the issue should be completely resolved.

Investigating: We are investigating an issue where reporting emails using the Hoxhunt add-in currently results in the following error: Hoxhunt backend returned error with code 401 - We will provide updates on the incident as our investigation progresses