How to Troubleshoot Outlook for Mac (2026 Guide)
Why Outlook for Mac Stops Working
I've seen this exact scenario play out on hundreds of Mac machines across enterprise environments: you open Outlook for Mac on Monday morning, and it either hangs on the loading screen, crashes silently, refuses to sync new emails, or just sits there spinning with no apparent error message. No helpful dialog, no error code, nothing. Just a broken email client when you need it most. I know how infuriating that is , especially in a work-from-home setup where your entire day hinges on getting into your inbox.
Outlook for Mac has a fundamentally different architecture than its Windows counterpart. It doesn't use a traditional .PST file. Instead, Microsoft stores all your mail, calendar, and contacts data in a proprietary SQLite-based database inside your macOS user profile. When that database gets corrupted , even slightly, Outlook can start behaving in completely unpredictable ways. You might lose just a few calendar entries, or the whole application may refuse to launch.
There are several root causes I see repeatedly:
- Corrupted Outlook database (OLM or local cache), The most common culprit by far. macOS file system quirks, forced shutdowns, or interrupted syncs can corrupt the SQLite index.
- Outdated Outlook build, Microsoft ships Outlook for Mac updates through Microsoft AutoUpdate. Skipping even two or three updates can leave you running a build with known crash bugs that were patched months ago.
- Conflicting add-ins, Third-party add-ins like Zoom, DocuSign, or Salesforce can inject code into Outlook's process space. When the add-in build doesn't match your Outlook version, you get crashes or frozen UI.
- Exchange connectivity issues, Autodiscover failures, expired OAuth tokens, or certificate errors on your Exchange or Microsoft 365 tenant can cause Outlook to appear "stuck" when it's actually just waiting on a network handshake that will never complete.
- macOS keychain conflicts, Outlook stores your authentication tokens in the macOS Keychain. After a macOS major version upgrade (like Sequoia or Sonoma), those keychain entries can become inaccessible, causing perpetual re-authentication loops.
- Preferences file corruption, The
com.microsoft.Outlook.plistpreferences file holds your window layouts, toolbar configurations, and account settings. When it goes bad, Outlook either crashes on launch or loses all your customizations.
Microsoft's error messages for Outlook for Mac have historically been vague at best. You might see "Something went wrong" with no error code, or a generic crash dialog that just says Outlook quit unexpectedly. That's why I wrote this guide, to give you the specific, actionable steps that actually fix this, not the boilerplate "reinstall Office" advice you'll find everywhere else.
The Quick Fix, Try This First
Before you go rebuilding databases or reinstalling anything, try this. It resolves the majority of day-to-day Outlook for Mac problems in under two minutes.
Force quit and relaunch in Safe Mode. Outlook for Mac has a Safe Mode that disables all add-ins at startup, and you'd be surprised how often a single broken add-in is the entire cause of your problem.
- Press Command + Q to quit Outlook. If it's frozen, press Option + Command + Escape, select Microsoft Outlook from the list, and click Force Quit.
- Hold down the Option key on your keyboard.
- While holding Option, click the Outlook icon in your Dock or double-click it in Finder.
- Keep holding Option until you see a dialog asking if you want to open in Safe Mode. Click Safe Mode.
- Outlook will launch with a "Safe Mode" banner in the title bar. Check whether the problem still occurs.
If Outlook works fine in Safe Mode, you've confirmed the issue is an add-in. Go to Tools > Add-ins, uncheck each one, and restart normally. Re-enable them one by one to find the offender.
If the problem persists in Safe Mode, move on to the full step-by-step process below. You likely have a database or profile issue that needs a deeper fix.
One more quick thing to try before anything else: check that Microsoft AutoUpdate has run recently. Open any Microsoft app, go to Help > Check for Updates, and install everything pending. I've fixed "mysterious" Outlook crashes just by applying a point release update that Microsoft shipped three weeks prior.
Exception Type: EXC_BAD_ACCESS or com.microsoft.Outlook alongside a third-party framework name.
This sounds obvious, but you'd be amazed how many enterprise Macs are running Outlook builds from six months ago because AutoUpdate was disabled by an IT policy. Old builds carry known bugs, crashes, sync failures, rendering glitches, that Microsoft has already fixed. Running outdated software and expecting it to work is like driving with a flat tire and wondering why the ride feels rough.
To update Outlook for Mac:
- Open any Microsoft 365 app (Word, Excel, or Outlook itself if it opens).
- Click Help in the menu bar, then Check for Updates.
- The Microsoft AutoUpdate application will launch. Click Update All.
- Restart your Mac fully after updates install, don't just close and reopen Outlook.
Also check your macOS version. Go to Apple menu > System Settings > General > Software Update. Microsoft regularly updates Outlook to support new macOS APIs, and running a version of macOS that's significantly older than what Outlook was optimized for can cause subtle rendering and crash issues.
If AutoUpdate is blocked in your environment (common on domain-managed Macs), you can manually download the latest Microsoft 365 for Mac installer directly from Microsoft's volume licensing portal or ask your IT admin to push the update via Jamf, Microsoft Endpoint Manager, or your MDM of choice.
After updating, launch Outlook and reproduce the original issue. If it's resolved, great. If not, continue to Step 2. Always update first. It eliminates the most common cause immediately.
What you should see: Outlook launches cleanly with no crash, and the version number in Outlook > About Microsoft Outlook matches the latest release on Microsoft's release notes page (currently 16.96.x for the Microsoft 365 subscription channel as of April 2026).
If updating didn't fix it, a corrupted local database is the next most likely cause. Outlook for Mac stores your locally cached emails, calendar items, and contacts in a database inside your user profile. You can rebuild this database without losing your email, it just forces Outlook to re-download everything from the server.
Here's how to rebuild it:
- Completely quit Outlook (Command + Q or Force Quit if necessary).
- Open Finder and press Shift + Command + G to open the "Go to Folder" dialog.
- Type the following path and press Return:
~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/ - You'll see a folder named Main Profile (or a custom name if you set one). Open it.
- Locate the file named Outlook.sqlite. This is your main database.
- Right-click the Main Profile folder and choose Get Info to note its size, this helps confirm the rebuild worked later.
- Now relaunch Outlook. At the same time, hold down the Option key. Instead of launching into Safe Mode this time, you'll see a "Microsoft Database Utility" option appear. Click it.
Alternatively, you can open Microsoft Database Utility directly from:
/Applications/Microsoft Outlook.app/Contents/SharedSupport/Outlook Profile Manager.appIn the Database Utility, select your profile and click Rebuild. The process can take anywhere from 2 minutes to 30 minutes depending on your mailbox size. Don't interrupt it. Once it finishes, relaunch Outlook normally.
What you should see: Outlook opens, begins syncing from the server, and the original crash or sync error no longer appears. Your emails will gradually populate as they re-download.
Outlook for Mac uses the macOS Keychain to store your Microsoft 365 or Exchange authentication tokens. After a macOS upgrade, a password change, or an admin-enforced conditional access policy change, those stored credentials can go stale. Outlook then gets stuck in an authentication loop, it keeps asking you to sign in, or it shows your inbox but won't actually sync new mail.
To clear the stale credentials:
- Quit Outlook completely.
- Open Keychain Access (search for it in Spotlight with Command + Space).
- In the search bar at the top right of Keychain Access, type Microsoft.
- You'll see a list of entries like
Microsoft Office Identities Cache 2,Microsoft Office Identities Settings 2, and individual account tokens labeled with your email address or tenant domain. - Delete all Microsoft-related entries. Right-click each one and choose Delete. You'll need to confirm with your macOS password or Touch ID.
- Also search for your email domain (e.g., contoso.com) to catch any Exchange-specific credential entries.
- Relaunch Outlook. It will prompt you to sign in fresh. Enter your credentials, complete any MFA challenge, and let Outlook re-establish the connection.
If your organization uses modern authentication with Azure AD/Entra ID and conditional access, make sure you're signing in from a compliant device. A non-compliant device (one that hasn't checked in with Intune recently, for example) will get an authentication error that looks exactly like a corrupted Keychain entry but won't be fixed by clearing credentials alone.
What you should see: Outlook prompts for your Microsoft 365 credentials, you sign in successfully, and email starts syncing within 30–60 seconds.
The com.microsoft.Outlook.plist file is where Outlook stores your personal configuration, toolbar layouts, reading pane settings, notification preferences, default account settings, and dozens of other options. When this file gets corrupted (it happens after hard crashes or botched updates), Outlook can behave erratically: random crashes, missing toolbar buttons, incorrect default accounts, or the app getting stuck in a launch loop.
Resetting it won't delete your emails, those live in the database. You'll just lose your window layout and preference tweaks, which you can reconfigure in about five minutes.
- Quit Outlook completely.
- Open Terminal (Applications > Utilities > Terminal).
- Run the following command to move (not delete) the preferences file to your Desktop as a backup:
mv ~/Library/Preferences/com.microsoft.Outlook.plist ~/Desktop/Outlook_prefs_backup.plist - Also reset the preferences cache:
defaults delete com.microsoft.Outlook - Relaunch Outlook. macOS will generate a fresh, clean preferences file automatically.
If Outlook now works correctly, the preferences file was the problem. You can open the backup file on your Desktop with a text editor if you want to manually recover specific settings, but honestly, just reconfigure from scratch. It's faster.
If you also want to reset the Office-wide shared preferences (which affects all Microsoft 365 apps), you can additionally remove:
mv ~/Library/Preferences/com.microsoft.office.plist ~/Desktop/office_prefs_backup.plistWhat you should see: Outlook launches as if it's a fresh install, it may show the "New features" welcome screen. Your accounts are still there (stored in the database, not the prefs file) and mail syncs normally.
If you've made it this far and Outlook is still misbehaving, the issue is almost certainly a deeply corrupted profile. Creating a new profile is the nuclear option short of reinstalling, but it works. Think of it as giving Outlook a clean slate while keeping your underlying mail data on the server intact.
- Quit Outlook completely.
- Open Outlook Profile Manager. You can find it at:
Or use Spotlight: press Command + Space and type "Outlook Profile Manager."/Applications/Microsoft Outlook.app/Contents/SharedSupport/Outlook Profile Manager.app - In Profile Manager, click the + button at the bottom left to create a new profile. Name it something like "Fresh Profile" or your name.
- Select the new profile and click Set as Default.
- Relaunch Outlook. It will open with a clean profile and prompt you to add your email account.
- Go to Tools > Accounts and click the + button at the bottom left to add your Microsoft 365 or Exchange account. Enter your email address and follow the sign-in prompts.
Outlook will start fresh, download your email from the server, and populate your new profile. This process eliminates any local corruption entirely. Your old profile is still there, you can switch back to it in Profile Manager if needed. Don't delete it yet; wait a week until you're confident the new profile is stable.
What you should see: A clean Outlook inbox that begins populating with your email from the server within a few minutes. Calendar and contacts will also sync automatically if your account is connected to Exchange or Microsoft 365.
Advanced Troubleshooting
Diagnosing with the macOS Console and Crash Reports
When Outlook crashes, macOS writes a crash report to ~/Library/Logs/DiagnosticReports/. The files are named Microsoft Outlook_[timestamp].crash. Open one in TextEdit and look at the "Exception Type" and "Crashed Thread" sections. An EXC_BAD_ACCESS (SIGSEGV) usually means memory corruption, often caused by an add-in. An EXC_CRASH (SIGABRT) often indicates an assertion failure in Outlook's own code, which typically means a bug that a pending update fixes.
You can also open the Console app, select your Mac in the left sidebar under "Devices," and filter the log stream for "Outlook" in real time while you reproduce the crash. The log lines immediately before the crash are your best clue.
Network-Level Troubleshooting for Exchange Connectivity
If Outlook launches fine but won't sync email, the issue may be network-side rather than local. Open Terminal and test your Exchange Autodiscover endpoint:
curl -v https://autodiscover.yourdomain.com/autodiscover/autodiscover.xmlA successful response returns HTTP 200 or HTTP 401 (the 401 is expected, it means Autodiscover is alive and asking for credentials). If you get a timeout, SSL error, or DNS failure, the connectivity problem is upstream of Outlook and your network team needs to investigate.
Also check your proxy settings. If your Mac is configured to use a corporate proxy (System Settings > Network > [Active Connection] > Details > Proxies), and the proxy isn't passing Microsoft 365 authentication traffic correctly, Outlook will fail silently. Try temporarily disabling the proxy and testing direct connectivity.
Managed Mac / MDM Scenarios
On Macs managed by Jamf Pro, Microsoft Endpoint Manager, or Mosyle, configuration profiles can enforce Outlook settings that conflict with what you're trying to fix. For example, a configuration profile might be disabling modern authentication, forcing a specific Exchange server address, or preventing keychain writes. Check with your IT admin whether any Outlook-specific MDM payloads are deployed to your machine. In Jamf, these appear under the "Profiles" section of the Self Service app.
If you're the IT admin troubleshooting this at scale, pull the Outlook crash logs from affected machines via your MDM and compare crash report timestamps against your patch deployment schedule. More often than not, you'll find a correlation between a botched AutoUpdate deployment and a spike in crash reports.
Outlook New vs. Legacy Outlook for Mac
Starting in 2024, Microsoft began defaulting new installations to the "new Outlook for Mac", a web-based wrapper that uses a completely different codebase. If you're seeing an unfamiliar interface that looks more like Outlook on the web, you may have switched to new Outlook. You can toggle back to legacy Outlook using the "Try the new Outlook" toggle in the top-right corner of the app. Some corporate features (certain S/MIME configurations, shared mailboxes with specific delegate permissions) don't yet work in the new version, which can look like a bug when it's actually a missing feature.
Prevention & Best Practices
Once you've fixed the immediate problem, let's talk about keeping Outlook for Mac stable long-term. Most of the issues I see are entirely preventable with a few simple habits and configurations.
Keep Microsoft AutoUpdate on a schedule. Don't disable AutoUpdate, I've seen IT teams disable it to "prevent disruption" and then end up with fleets of Macs running 12-month-old Outlook builds full of patched vulnerabilities and known crash bugs. Set AutoUpdate to check weekly at minimum, and plan a monthly patch window. You can configure AutoUpdate behavior via MDM using the com.microsoft.autoupdate2 preference domain if you want centralized control without disabling updates entirely.
Avoid force-shutting down your Mac while Outlook is syncing. The SQLite database that Outlook uses doesn't take kindly to interrupted writes. If you're in the middle of a large email sync (say, you just added a 50GB archive mailbox), don't close the lid or shut down until the sync completes. Outlook doesn't always handle unexpected write interruptions gracefully, and you can corrupt the index.
Limit add-ins to what you actually use. Every add-in you install is another piece of code running inside Outlook's process. Audit your add-ins quarterly. Go to Tools > Add-ins and disable anything you haven't used in the last month. The fewer add-ins, the more stable Outlook will be.
Regularly archive older email. Extremely large local databases slow Outlook down and increase the chance of database corruption during operations. If your inbox has 10+ years of email cached locally, consider using server-side archiving or moving older items to an OLM archive file.
- Enable Microsoft AutoUpdate and set it to check for updates weekly, never disable it in production environments.
- Run a monthly Outlook database rebuild proactively, even when things seem fine, it takes five minutes and prevents major corruption from building up silently.
- Back up your Outlook profile folder to Time Machine or a cloud backup solution; the path is
~/Library/Group Containers/UBF8T346G9.Office/Outlook/. - After any major macOS upgrade (Sonoma, Sequoia, etc.), clear your Microsoft Keychain entries and re-authenticate Outlook fresh, don't wait for a sync failure to tell you something's wrong.
Frequently Asked Questions
Why does Outlook for Mac keep asking me to sign in over and over?
This is almost always a Keychain issue or an expired OAuth token. Follow Step 3 in this guide to clear all Microsoft-related entries from your macOS Keychain and sign in fresh. If it keeps happening after that, your organization may have a conditional access policy that's blocking your device, check with your IT admin whether your Mac is enrolled in Intune or another MDM and marked as compliant. A non-compliant device will get its token revoked on every sync cycle, causing exactly this symptom.
Outlook for Mac won't open at all, it just bounces in the Dock and crashes. What do I do?
Start by holding Option while launching to open in Safe Mode and see if add-ins are the cause. If Safe Mode also crashes, go straight to resetting your preferences file (Step 4) and then rebuilding your database (Step 2). Check your crash report in ~/Library/Logs/DiagnosticReports/ for an "Exception Type", if you see EXC_BAD_ACCESS, an add-in is almost certainly the culprit even in Safe Mode if it somehow loaded before the crash occurred. Creating a new profile (Step 5) is the most reliable fix for a launch crash that persists through all other steps.
My Outlook calendar isn't syncing with my iPhone, how do I fix it?
Calendar sync between Outlook for Mac and iPhone typically goes through your Exchange or Microsoft 365 account server, not a direct Mac-to-phone connection. So the fix usually isn't on the Mac side at all, check whether the iPhone's Outlook app (or the native Calendar app, if you're using Exchange sync) shows the same missing events. If the Outlook app on your iPhone is also missing events, sign out of the Outlook app on your phone and sign back in. If the native Calendar app is the problem, go to Settings > Calendar > Accounts on your iPhone, remove the Exchange account, and re-add it. This forces a fresh sync from the server.
How do I back up my Outlook for Mac emails before doing a major fix?
The simplest backup is to export to an OLM file. In Outlook, go to File > Export, select "Outlook for Mac Data File (.olm)," choose what to include (mail, calendar, contacts), and save to an external drive or cloud storage. An OLM file can be re-imported into Outlook for Mac later via File > Import. You can also just copy your entire profile folder to an external drive: it's located at ~/Library/Group Containers/UBF8T346G9.Office/Outlook/Outlook 15 Profiles/. For most people on Exchange or Microsoft 365, though, your email lives on the server and you don't technically need a local backup, just know that any locally-stored items (in "On My Computer" folders) are only in the local database and must be exported manually.
Outlook for Mac is extremely slow, emails take forever to load. How do I speed it up?
Slow Outlook on Mac usually comes down to three things: a bloated local database, too many cached folders from a large mailbox, or an overloaded background sync. First, rebuild your database using the Microsoft Database Utility (Step 2 above), this compacts the SQLite file and removes fragmentation that builds up over time. Second, check how many folders Outlook is syncing. If you have hundreds of folders with thousands of items each, go to Tools > Accounts, click your account, and look for folder caching settings. Finally, check Activity Monitor for Outlook's CPU and memory usage, if it's consistently above 80% CPU, something is looping in the background, and a fresh profile (Step 5) usually fixes it.
After a macOS upgrade, Outlook for Mac looks broken, fonts are wrong and the layout is messed up. What happened?
Major macOS upgrades sometimes change how the system renders fonts and UI elements, and Outlook's preferences file can hold cached rendering values that become incompatible. The fix here is straightforward: reset your preferences file (Step 4), which forces Outlook to re-initialize all its visual settings against the current macOS rendering engine. Also make sure you've updated Outlook itself to the latest build via Microsoft AutoUpdate, Microsoft ships compatibility updates for new macOS versions within days of Apple's releases, and running the old build on the new OS is asking for rendering glitches. If the issue persists, toggle between "New Outlook" and "Legacy Outlook" using the toggle in the top-right corner, they use different rendering engines, and one may look better on your system.