Forum Discussion
Synchronization issue in New Outlook for Mac – ״Failed to refresh subscriptions.״
Hello,
I am using Microsoft 365 (Exchange Online) on Mac, running macOS 26.1 (Tahoe). My Outlook client is: Outlook for Mac Version 16.103.3 (25113013), with a Microsoft 365 Subscription license.
Since yesterday morning, in the New Outlook interface, my inbox has suddenly appeared empty, and I constantly receive the following error message: “Failed to refresh subscriptions.”
It’s important to note:
- In Legacy Outlook, everything works perfectly.
- The web version and the Outlook app on my mobile phone also work well.
- The issue persists regardless of the network I am on (home, office, cellular, etc.).
Troubleshooting steps I already tried: • Updating Outlook to the latest version • Removing and re‑adding the account • Clearing cache and preferences • Formatting my Mac and reinstalling everything from scratch
Unfortunately, none of these steps has resolved the issue.
Is this a known bug, and is there a recommended workaround or an upcoming fix?
Appreciate assistance on that issue.
4 Replies
- theketchupCopper Contributor
We encountered this issue as well. The fix we found was deleting all draft and sent emails. Corrupt attachments and emails in the drafts or sent folder can cause sync issues with the Outlook for Mac database.
I found that information here: https://discussions.apple.com/thread/255907080?sortBy=rank
- AviadkrCopper Contributor
Thanks for sharing the solution and the link. I will try deleting drafts and sending emails as you suggested, and hope it resolves the issue. Appreciate your help and the time you took to respond!
- ginger9077Brass Contributor
I have users across my org who are having this newest update crash Outlook vs not having emails in it. It starts happening immediately after the update :(. You don't even have to be actively using Outlook.
note to everyone on a mac- don't update Outlook to 16.103.3- AviadkrCopper Contributor
Thanks for sharing the warning! This is essential information. I also noticed similar issues after updating, so it’s good to see it’s not just on my end. If you hear of any fixes or workarounds from Microsoft, please update!