The error shown in the screenshot ("You don't have permission to use this add-in. Contact your system administrator.") is a known class of issue with Office Add-ins and is typically caused by how add-ins are configured for the signed-in account/tenant, not by the add-in itself.
From the context provided:
- Errors like this are usually due to Microsoft 365 tenancy or catalog configuration that prevents acquisition or execution of Office Store add-ins. In such cases, the add-in information box or task pane error is expected and users are instructed to contact their Microsoft 365 administrator.
- There is also a specific known issue for centrally deployed add-ins in certain Office builds where users see the same message ("You don't have permission to use this add-in"). A fix is being rolled out, and in the meantime the recommended workaround is to refresh admin-managed add-ins or have an admin force a refresh via a registry key.
Because the work account add-ins function but the personal account does not, the most likely explanations supported by the context are:
- The personal account’s tenant or catalog configuration is blocking access to the Office Store or specific add-ins, which leads to the permission error.
- If the add-in is centrally deployed (admin-managed) and the Office build is affected by the known issue, the catalog may need to be refreshed for that account.
Actions supported by the context:
- In Excel, open Home → Add-ins → More add-ins → Admin Managed, then select Refresh in the top-right. After refresh, try opening the add-in again.
- If the add-ins are centrally deployed and an IT admin is available, the admin can force a refresh by creating the registry key
HKCU\Software\Microsoft\Office\16.0\WEF\TrustedCatalogs\ClearInstalledExtensions with DWORD = 1 for the affected profile, then having the user restart Office and test again.
- If the error continues, the account’s Microsoft 365 administrator needs to review add-in and Office Store settings for that tenant, because configuration-level restrictions are a documented cause of these permission errors.
Registry changes already attempted (such as UseOsfWebHost) are not mentioned in the context as a fix for this scenario, whereas catalog refresh and tenant configuration checks are.
References: