Outlook calendar on a Mac when the sync only runs one way

The complaint behind a search for Mac Outlook calendar sync is almost never that nothing arrived. Something arrived. An event created in one place shows up in the other, and then an edit made on the Mac never travels back. Or a meeting accepted on the phone stays tentative in Outlook. Or a calendar that was correct last Tuesday has quietly stopped changing since.

Direction is the whole problem. A calendar that flows one way is not broken, and no amount of restarting Outlook will turn it around, because the direction was decided by which of four different mechanisms is actually connected. Naming the mechanism takes about a minute and settles what can be fixed and what cannot.

Four different things wearing the same word

The word sync covers at least four arrangements on a Mac, and they behave nothing alike.

The first is a direct account connection. Outlook signs in to a Microsoft 365 or Outlook.com mailbox and reads and writes the same calendar the server holds. Changes travel in both directions because there is only one calendar, viewed through a window.

The second is a bridged account. A Gmail, Yahoo, or iCloud account is added to Outlook, and a copy of the data moves between that provider and Microsoft. Microsoft describes this plainly: when the account is synced to the Microsoft Cloud, a copy of the email, calendar, and contacts is synchronized between the email provider and Microsoft data centres. Two systems now hold a version of the same events.

The third is a subscription to a published link. Someone sends an address ending in .ics, it gets pasted into Calendar on the Mac or into Outlook, and events appear. This one is read-only by design, and the next section covers why.

The fourth is a different client reading the same mailbox. Apple Calendar is given the Exchange or Outlook.com account directly, and it reads and writes the server copy the same way Outlook does.

Only the first and the fourth are genuinely two way. The second is two way in theory and lossy in practice. The third was never intended to be two way at all. Most of the frustration in this area comes from expecting the third to behave like the first.

The one that is read-only on purpose

Publishing a calendar in Outlook produces two kinds of link, and Microsoft states the limit in a single sentence: HTML and ICS calendars are read-only, so recipients will not be able to edit the calendar. An HTML link opens a view in a browser. An ICS link can be downloaded and imported once, or subscribed to so that updates keep arriving.

Subscribed is the interesting case, because it looks like sync from the outside. Events appear, they update later, nothing announces that the connection is one directional. Then a colleague drags a meeting to a new time inside the subscribed copy on the Mac, the change sits there looking correct, and nobody on the other side ever sees it.

Refresh timing makes this worse. Microsoft says only that how often an ICS calendar syncs depends on the recipient's email provider, which means the delay is set by the receiving side and is not always adjustable. On a Mac, Calendar does expose a control: control-click the subscribed calendar, choose Get Info, and set the Auto-refresh interval. There is also View then Refresh Calendars for a manual pull, and a per account refresh setting under Calendar, Settings, Accounts.

If writes need to travel back, publishing is the wrong tool and no setting will rescue it. The replacement is sharing with a permission level. Outlook on the web offers a ladder that runs from showing only availability, through showing titles and locations, through showing all details, up to edit rights and full delegate access. Edit and delegate are the two that allow another person to change the calendar, and they require the recipient to be given access to the calendar rather than a link to a copy of it.

What Outlook for Mac actually connects to

Two facts about the application itself decide whether any of this is available.

The Mac App Store listing for Microsoft Outlook currently shows version 16.113 and requires macOS 14.0 or later, and the listing price is free. Microsoft supports the three most recent major versions of macOS for Microsoft 365 and Office for Mac, and from the September 2025 update, build 16.101, macOS Sonoma or later is required to receive updates to Word, Excel, PowerPoint, Outlook, and OneNote. Older installs keep launching, but they stop receiving updates, including security updates.

The second fact concerns which accounts can hold a calendar at all. Gmail, Yahoo, and iCloud accounts can bring mail, calendar, and contacts into Outlook for Mac through the Microsoft Cloud sync. An account configured as plain IMAP brings mail only, with no calendar and no contacts. A mailbox added the manual IMAP way will therefore never show a calendar, and that is the documented behaviour rather than a fault to troubleshoot.

Google accounts carry a set of known gaps worth checking before spending an evening on them. Tasks and notes are not supported. The Weather calendar from Google Calendar does not appear. The Birthdays calendar shows up under a different name in legacy Outlook for Mac. Responding to a Google meeting invitation requires the meeting to be visible on the calendar, which depends on a setting inside Google Calendar rather than anything in Outlook.

Going the other way, into Apple Calendar

The reverse arrangement has the same fork in it. An Outlook.com or Microsoft 365 account added to Calendar on the Mac through Internet Accounts is a live connection, and edits made in Calendar reach the server. A published ICS link pasted into Calendar is a subscription, and edits go nowhere.

The two look nearly identical in the sidebar once they are set up, which is why the direction is worth confirming at the moment of adding. Control-click a calendar and choose Get Info. A subscription shows a web address and an Auto-refresh menu. An account calendar does not.

Route	Direction	Typical delay	What it cannot do
Microsoft account in Outlook	Two way	Immediate	Nothing, it is the server copy
Gmail or iCloud in Outlook	Two way, with gaps	Minutes	Tasks, notes, some Google-only calendars
Published ICS subscription	One way, read only	Set by the receiving side	Any write back, at all
Microsoft account in Apple Calendar	Two way	Immediate	Outlook-only interface features
Outlook on the web	No sync, single copy	None	Work offline

Telling them apart in two minutes

Before changing anything, establish which of the four is actually connected, because the repair differs completely.

Start on the Mac, in Calendar. Control-click each calendar in the sidebar and open Get Info. A subscription reveals itself immediately through a web address field and an Auto-refresh menu. An account calendar shows neither. Anything with a web address in that field is read-only, whatever it is named in the sidebar.

Then look at where the calendar was added. Calendar, Settings, Accounts lists every account with its type, and an account described as Exchange or Outlook.com is a live connection to the server. A calendar that appears under a heading such as Other or Subscriptions came from a link.

In Outlook for Mac, the equivalent check is the account list in settings. An account added through the Google or iCloud sign in flow is bridged through the Microsoft Cloud and carries the documented gaps. An account typed in manually with a server name and port is IMAP, which supports mail only and will never produce a calendar no matter how long it is left to sync.

Write down which mechanism each calendar uses before touching any settings. Half the time the answer makes the problem disappear, because the behaviour turns out to be documented rather than broken.

Every hop is a copy, and copies argue

There is a deeper reason to keep the count of connections low. Each bridged arrangement creates another stored version of the same events, and every stored version needs a rule for what happens when two of them disagree.

A recurring meeting edited on a phone while the Mac is asleep, an all day event whose time zone is interpreted differently by two systems, an invitation accepted in one client and declined in another: these are the cases that produce duplicated events, ghost entries that refuse to delete, and reminders that fire twice. They are not caused by a bad application. They are caused by the number of copies.

The practical rule is to decide which system owns the calendar and connect everything else to that system directly, rather than chaining one bridge onto another. A Google calendar bridged into Outlook, then published as an ICS link, then subscribed to from Calendar on the Mac, is three copies deep. Something in that chain will drift, and diagnosing which link did it is a bad way to spend a Thursday.

When the tab is the actual complaint

There is a version of this problem where the calendar is fine. It syncs, it is accurate, both directions work, and the real irritation is that Outlook on the web lives inside a browser tab next to twenty others, so the calendar is never where the eye expects it and alerts only arrive while the browser happens to be running.

Outlook on the web has one clear advantage in the list above: there is no second copy, so there is nothing to fall out of step. Reaching it costs nothing and breaks nothing. What it costs is a permanent home on the screen.

Browsers offer a partial answer. Chrome can install a page as an app from the More menu, under Cast, save, and share, and Safari on macOS Sonoma and later has Add to Dock in the File and Share menus, which Apple describes as producing a web app that shares no browsing history, cookies, website data, or settings with Safari. Both create an icon and a window without a tab strip.

The limit shows up with a second account. A browser installed app is tied to the browser profile it came from, so a work calendar and a personal calendar created from the same profile end up fighting over one signed in identity. A tool that turns a website into a standalone Mac app handles that differently, by giving each generated app its own isolated profile and its own icon, so two Outlook calendars can sit side by side in the Dock, each permanently signed in to a different account. The Features page describes how per app profile isolation works, and the Supported services list covers the mail and calendar services that come preconfigured.

What to change first

Open Get Info on the calendar that is misbehaving. If it shows a web address and an Auto-refresh menu, it is a subscription, it is read-only by design, and the fix is to ask for shared access with edit rights instead of a published link. If it is an account calendar and writes still fail, reduce the chain: connect the client directly to whichever system owns the events, and remove the middle hop. If the calendar was never the problem and the browser tab was, give Outlook on the web its own window and its own icon with a site to app tool such as Kagemusha, and leave the working sync alone.