Overview
Hoxhunt's Outlook add-in is not automatically updated. Only add-ins that are installed via Microsoft AppSource are automatically updated as add-in vendors release a new version, and Hoxhunt add-in can currently be deployed only as a private app.
Therefore, updating Hoxhunt add-in must be done manually by Microsoft 365 Admin via Microsoft 365 Admin Center or by Exchange Admin via Exchange Admin Center. Fortunately the update process is quite simple.
Frequently asked questions
Why should we update Hoxhunt add-in to a newer version?
Most new features in Hoxhunt can be enabled and disabled without updating the add-in itself. However, sometimes a new Hoxhunt feature may require Microsoft to extend their Office add-in framework first. For example, version 1.0.0.5 includes support for reporting emails from shared mailboxes. This feature was made technically possible by development effort from Microsoft side, and thus the new feature required a new "flag" to be added to the manifest.xml. This is a security measure from Microsoft that ensures that new significant features cannot be introduced to Office add-ins silently.
You can check our release notes for new features. If the feature needs Hoxhunt add-in version update, it is mentioned explicitly in the article.
How can we check the version number of currently installed Hoxhunt Outlook add-in?
Your Exchange Admins can check the deployed add-in version.
If you deployed Hoxhunt Outlook add-in via Exchange Admin Center, go to Exchange Admin Center > organization > add-ins. Locate Hoxhunt add-in from the list and open it's details to check its version number.
If you deployed Hoxhunt Outlook add-in via Centralized Deployment, go to M365 Admin Center > Settings > Add-ins. Locate Hoxhunt add-in from the list and open it's details to check its version number.
NOTE: It is not possible to see the version number via Services > Integrated apps. This is a limitation by Microsoft. Instead, try accessing the Services > Add-ins page direct via this link. It is also possible to check the add-in version via Powershell.
NOTE: Regular Hoxhunt user cannot check the add-in's version number.
Can we check the changes you have done? We may also have some security concerns over what type of permissions Hoxhunt add-in is asking for.
Yes. The manifest.xml used to install and update Hoxhunt add-in can be opened and examined in any text editor.
For more information about how to read Outlook add-in manifest.xml, security and privacy concerns, please refer to following articles form Microsoft:
Privacy, permissions and security for Outlook add-ins
Understanding Outlook add-in permissions
Updating add-in to new version
A) If Hoxhunt was deployed via Centralized Deployment
If you deployed Hoxhunt add-in via Centralized Deployment, you can use Update add-in command located in Settings > Add-ins > Hoxhunt Report > Update add-in.
Enter the manifest.xml URL: https://officejs.hoxhunt.com/api/v1/manifest/default/manifest.xml
NOTE: If your organization has deployed a customised Hoxhunt add-in (e.g. custom logo), please see section C) below.
If you haven’t given consent to Graph API permissions before, a view with permissions and capabilities may be shown. Review them and proceed.
If adding from URL fails, please download the manifest.xml to Desktop and use Add from file... option instead. You may still receive an error but the update works this time.
NOTE: It may take several hours for desktop Outlook clients to detect the updated add-in. You can verify update process worked more quickly via Web Outlook.
B) If Hoxhunt was deployed via Exchange Admin Center
If you deployed Hoxhunt add-in via Exchange Admin Center (organization > apps/add-ins) or via New Exchange Admin Center (Organization > Add-ins), there is no Update option available. You first need to remove Hoxhunt add-in and then re-deploy it. Please note this will temporarily remove the add-in from end users and create some service disruption.
C) My organization deployed a customised Hoxhunt button
If your organization has deployed a customised Hoxhunt add-in (e.g. custom logo), replace the manifest URL with your custom manifest URL, and then proceed with either option A) or B) depending on your original deployment method.
<%= heading %>