Outlook Calendar not working: what to check, in order

An event that should be on the calendar is missing. A meeting that moved still shows the old time. A shared calendar stopped updating on Tuesday and nobody changed anything. When Outlook Calendar is not working on a Mac, the instinct is to open settings and start toggling things, or to remove the account and add it again. That sometimes produces a temporary improvement and almost never explains what went wrong.

The faster approach is a fixed order of checks, each one ruling out a whole category of causes. Most problems resolve within the first four steps, and the later steps exist mainly to stop time being spent on things that are not bugs at all.

Name the symptom before touching anything

"Outlook Calendar is broken" usually means one of five distinct things, and each points somewhere different.

Symptom	Where to look first	What it tells you
Events missing	Outlook on the web	Whether the server has the event
Events not updating	How the calendar was added	Whether the delay is expected
Events cannot be edited	Sharing permission or subscription type	Whether the route allows writing
Reminders missing or repeating	The same event on the web or phone	Whether the fault is local to the Mac
App will not open or keeps asking to sign in	Legacy toggle and app version	Whether the client itself is the issue

The first three are about where the data lives and how it reaches the Mac. The last two are usually about the state of the app on this particular machine. Writing down which row applies before starting sounds trivial, but it prevents a common trap: changing a setting, seeing a different symptom disappear for a while, and concluding the original problem is fixed.

Step one: open the web version

Sign in to Outlook.com for a personal Microsoft account, or Outlook on the web for a work or school account. The web client renders what is stored on the server with no local cache in between, so it is the reference point for everything else.

If the event looks correct on the web, the data is fine. The fault sits on the Mac, and the remaining work is local: updating the app, forcing a sync, or checking which version of Outlook is running.

If the event is also wrong on the web, no amount of work on the Mac will help. Attention moves to whoever created the event, the state of the account, and the service itself.

This single check is also the reason not to delete and re-add an account as a first move. If the server is the problem, re-adding forces a full resync against a service that is already misbehaving, and the original evidence is gone. Confirm the web client looks right first, and only then consider rebuilding the local account.

A phone is a useful second reference. If Outlook on an iPhone shows the correct event and only the Mac is wrong, the cause is almost certainly inside that Mac.

When the symptom is reminders

Reminders deserve their own short branch, because the web check answers a different question for them. If the reminder time is set correctly on the event in the web client, the calendar data is fine and the failure is in delivery on the Mac. Two places decide delivery there, and neither is inside Outlook's calendar view.

The first is macOS itself. System Settings, then Notifications, holds a separate entry for Microsoft Outlook, and a Focus mode or a notification style set to none will silence reminders without any sign inside the app.

The second is duplication. The same work calendar added both to Outlook and to the built in Calendar app on the Mac produces two reminders for every event, and dismissing one leaves the other. That looks like a reminder that refuses to go away, but it is two apps each doing their job. Deciding which app owns reminders, and turning them off in the other, ends it.

Step two: check whether Microsoft is having an outage

When the web client is also missing events, or everything suddenly slows down at once, check the public service status page at portal.office.com/servicestatus. It separates consumer products, which cover personal accounts, from Microsoft 365 business and enterprise services.

For business and enterprise tenants, that page does not show the detail. It sends visitors to the admin center instead, which most employees cannot open. If several colleagues on the same work account are affected at the same moment, the quickest path is the internal IT contact, who can see the service health dashboard for the tenant.

For personal accounts, an active incident means there is nothing useful to change locally. Adjusting settings during an outage tends to leave a second, self-inflicted problem behind once the service recovers. Keep the web client open to see the schedule and wait.

Step three: confirm which Outlook is running

Two apps named Outlook can live on the same Mac: the current Outlook for Mac and legacy Outlook for Mac. The legacy client includes a toggle inside the app for switching to the new one, and the position of that toggle shows which is open.

This matters right now because the legacy client depends on a service with a fixed retirement date when connecting to Exchange Online, which is what Microsoft 365 work accounts use.

Legacy Outlook for Mac uses Exchange Web Services (EWS) in Exchange Online to deliver your email. The EWS service will be retired on October 1, 2026. Source: support.microsoft.com

The same page lists the support timeline by license. Legacy Outlook for Mac with Microsoft 365 Personal or Family reaches end of support in October 2026. Business plans connecting to Exchange Online end in October 2026. Connections to on-premises Exchange continue until October 9, 2029. Non-subscription copies of Outlook for Mac, including the version downloaded from the App Store, are listed as not supported on the legacy client at all.

The practical consequence is simple. If a calendar on the legacy client stops syncing with a Microsoft 365 work account after that date, the cause is the retirement, not a configuration error. The fix is to turn the legacy toggle off. Where the toggle is missing, Microsoft points to Help, then Check for Updates, or a fresh download from the App Store.

Step four: find out how the calendar was added

"Not updating" is the symptom most often reported as a bug that turns out to be designed behavior. It depends entirely on how the calendar entered Outlook.

A calendar added with Subscribe from web is an internet calendar: a school schedule, a sports fixture list, or a private address exported from another calendar service. Outlook fetches it on a schedule rather than receiving changes as they happen. Microsoft's own help page for Outlook.com says updates should happen approximately every 3 hours and can take more than 24 hours.

A calendar added with Upload from file is an import. The events are copied once, and nothing updates afterward even if the original owner changes them.

Neither can be written to from Outlook. So the same root cause explains both "the change from this morning is not showing" and "the event cannot be edited."

The pattern to watch for is the remove and resubscribe loop. Removing a subscription and adding it again pulls a fresh copy immediately, which looks like a fix. The next change on the source side arrives on the normal schedule, and the "bug" returns. If a calendar genuinely needs changes within minutes, a subscription is the wrong route. It needs to arrive as a sharing invitation between accounts, or through an account added directly to Outlook.

Step five: work around the missing sync status screen

People who have moved to the current Outlook for Mac often look for a place to see sync errors. Microsoft's published feature comparison for Outlook for Mac lists both "View sync errors" and "View sync status" as not available. "Synchronize now" is available.

That changes how to read a quiet screen. On this client, the absence of an error message does not mean sync succeeded, because there is nowhere for the error to appear. When events seem stale:

• Run Synchronize now and give it a few minutes.
• Open the same event in the web client and compare.
• If the web is correct and the Mac is not, check for app updates.
• If that fails, collect diagnostics and contact support from inside the app.

In-app support lives under Help, then Contact Support, and sends Outlook logs to Microsoft. There are two limits worth knowing before relying on it. Microsoft states that the free version of Outlook does not include the Contact Support option; it appears with a Microsoft 365 subscription or a perpetual Office license. And work or school accounts are directed to their organization's help desk rather than the in-app route. Administrators can also disable the option by policy. If the option is present but nothing happens when it is selected, Microsoft's workaround is to lock all keychains in Keychain Access and then unlock the login keychain.

Step six: separate missing features from bugs

The current Outlook for Mac does not yet carry every feature from the legacy client, and some calendar behaviors that feel broken are simply absent. From the same feature comparison, the calendar items not yet in place include:

• Calendar outbox: not available
• Duplicate existing event: upcoming
• "From this day forward" editing of recurring events: upcoming
• Access to public folders: not available
• Shared and delegated calendars on on-premises Exchange: noted as coming soon

The recurring series case causes the most confusion. Changing a weekly meeting only from next month onward may not behave as expected in this client, and that is a gap in the product rather than a problem with the account. Performing that one edit in the web client is the practical route.

Account coverage, on the other hand, is broad. The comparison lists Google, iCloud, Yahoo, IMAP, POP, Outlook.com, Office 365, and on-premises Exchange as available. Adding a Google account to Outlook for Mac and seeing its calendar is supported behavior, so a failure there is worth reporting rather than assuming it cannot work.

Step seven: accept that some fixes belong to an administrator

On a work or school account, organizational policy is applied before any setting on the Mac. A few symptoms point straight at it:

• Sign-in completes and then immediately fails, repeatedly, in one particular app.
• External calendars cannot be added, or sharing with people outside the organization is blocked.
• Contact Support is missing from the Help menu on a licensed copy.

Removing and re-adding the account produces the same result each time, because the policy has not changed. What helps the IT team is a screenshot of the error and a one line description of the action that triggered it. They can see sign-in logs that are not visible from the user side.

A personal Outlook.com account used on a work Mac is not subject to those policies. Establishing early which account the problem belongs to decides who can actually fix it.

What to change first

Start with the web client every time. Correct on the web means the problem is the Mac app, its version, or its sync. Wrong on the web means the problem is the source event, the account, or the service. That split, followed by the legacy toggle and the subscription check, resolves most cases without rebuilding anything.

When sync works and the week still does not fit, the cause is usually how the calendars are arranged rather than the app: separate accounts that never appear on one screen, and meetings booked back to back with no travel between them. The Guide walks through building a day from the calendar, and Travel time explains how to plan around the gaps. For a desktop calendar that sits alongside Outlook rather than replacing it, see Caltimate.