This article describes some of the most common error situations our customer have encountered when deploying Hoxhunt button for the first time or when trying to update it.
Known issues for Outlook add-ins
Microsoft occasionally has issues related to add-in deployment in M365. The following Microsoft article provides information about currently known issues with Office Add-ins and their deployment.
https://learn.microsoft.com/en-us/office/dev/add-ins/resources/resources-office-add-in-known-issues
App ID doesn't match
Cannot update the add-in as the ID of the new add-in differs from that of the existing add-in.
This error is usually encountered by customers who are switching from the generic Hoxhunt add-in to a customized Hoxhunt add-in.
Solution:
Deploy your custom Hoxhunt add-in as a new add-in and un-deploy the generic Hoxhunt add-in
Same version number
Update failed
No apps were successfully updated. Please try to update them later.
Failed. Please update the version number in the manifest file and try again.
You are trying to update Hoxhunt add-in to a newer version but your manifest has the same version as the currently deployed Hoxhunt add-in.
Solution:
In most cases, you don't need to do anything as you already have the latest version deployed.
If you have made customization to your manifest file and wish to deploy them, please increase the version number within the manifest and try again.
Deployment failed
Deployment failed
This operation was unsuccessful - reasons may include:
- Learn more about eligibility requirements.
(7ff11c40-c5fd-4f57-8c7c-ce55dd4cf581)
This error is often caused by insufficient permissions for the admin user doing the add-in deployment.
Solution:
Please navigate to the Exchange Admin Center and make the following changes.
From EAC > Roles > Admin Roles, go to Organization Management > Permissions, and make sure Org Custom Apps is ticked as shown below:
TIP: Errors during deployment can often be ambiguous and without a proper description. It's a good practice to open your web browser's Inspect (dev tools) and look for any error messages during UploadAddIn command in Network tab.
See example below:
You do not have permission to install add-in for organization.
Add-in is not showing up in any Outlook client
Symptom: Add-in is shown as deployed in Centralized Apps but not shown as deployed to anyone in Powershell.
If you're deploying Office add-ins and none are showing up, then as a first troubleshooting step, use the Get-OrganizationConfig | fl AppsForOfficeEnabled PowerShell command. If the query returns a value of False, set this parameter to True using the Set-OrganizationConfig -AppsForOfficeEnabled:$True command. The add-ins should then appear as expected.
We don't recommend that the AppsForOfficeEnabled parameter be set to False. A value of False overrides all the Administrative and User role settings and prevent any new apps from being activated by any user in the organization.
Read more here: Check the AppsForOfficeEnabled parameter