Forum Discussion
Office Add-ins error: Cannot connect to catalog
One of our admin-managed add-ins (Adobe Sign) has gone AWOL from the ribbon of the Word desktop app recently (it still shows up in the web-app version of Word). One of the suggested troubleshooting s...
Charles_Kenyon
We, as IT-administrators, also experience this issue on our Mac-clients - "Cannot connect to catalog".
The issue not only occurs in Word - but apps like Excel as well. And we don't think it is related to a specific add-in, since we have tried with many different ones, with the same result.
We have deployed a few Add-ins via the Microsoft 365 admin center -> Integrated apps.
We can see the Add-ins in the web-browser on both PC and Mac. We can also see the Add-ins on the PC Desktop client of Word. But when we try to open Office Add-ins, and the Admin Managed-pane, via Word (or other Office-apps like Excel) on a Mac we get following error: Cannot connect to catalog
This error is seen for all users in the tenant.
We have tried the following:
Re-installed the MacOS.
Upgraded to latest version macOS Ventura, 13.2.1.
Secured that the Office version number is the latest: 16.71.
We have "Turn on optional connected experiences" enabled on the Mac-clients.
We have allowed full disk access to Word, Outlook etc.
Is Admin Managed Add-ins supported for Mac or not? It seems like a general issue, since johannesboyne and TheIronRock95 also recently reported this.
securebeam
I solved the problem on my Mac.
- Removed the entire office install of version 16.71/70, including the license tool and update tool. (https://support.microsoft.com/en-us/office/how-to-remove-office-license-files-on-a-mac-b032c0f6-a431-4dad-83a9-6b727c03b193)
- Then restarted my laptop.
- Installed an older office 16.69.23010700. (https://learn.microsoft.com/en-us/officeupdates/update-history-office-for-mac#release-history-for-office-for-mac)
- After this I am able to install Admin Managed Add-ins again.
TheIronRock95 check this out from the official repo: https://github.com/OfficeDev/office-js/issues/3221
it looks like it's an issue with v16.70 and MacOs Ventura and has been reported and acknowledged by the office team.
