Keeping one calendar in two places without duplicates

Two calendars, one schedule. Work lives in Outlook because that is where the invitations arrive, and the rest of the week lives on the Mac because that is where everything else is. Keeping them in agreement sounds like a settings problem. It usually turns out to be a question of which direction the data is allowed to flow, and the answer has changed twice in the last two years.

There is also a deadline attached to one of the common setups. The legacy Outlook for Mac client stops working against Exchange Online mailboxes starting in October 2026, because the service it depends on is being retired. Anyone still running that client with a work mailbox has a fixed date rather than an open-ended choice.

Decide the direction before touching any settings

Three shapes are possible, and mixing them carelessly is where duplicate events come from.

In the first shape, Outlook is the single window. Every account, including Google and iCloud, is added inside Outlook, and the Mac's own Calendar application is left unused. In the second, Apple Calendar is the single window, and the work mailbox is added to macOS as an Exchange or Microsoft 365 account. In the third, both applications sign into the same accounts independently, each holding its own copy, which is supported and works.

What does not work is the same calendar arriving by two different mechanisms into the same application. An account added properly and the same calendar also subscribed as a published link produces every event twice, and no amount of hiding calendars cleans it up. Hiding leaves the duplicates in search results and in anything else reading the same database.

Deciding the shape first takes two minutes. Undoing the wrong one after three months of accumulated events takes considerably longer.

What the current Outlook for Mac can hold

Microsoft's documentation for adding an account states that most email accounts, including Microsoft 365, Exchange server accounts, Outlook.com, Hotmail, Live and Google accounts, can be set up in Outlook for Mac.

The important detail is what comes across besides mail. Microsoft describes the current behaviour as syncing non-Microsoft accounts to the Microsoft Cloud, and lists what that covers.

Calendar (Gmail, Yahoo, and iCloud accounts) Note: IMAP only supports mail. Contacts (Gmail, Yahoo, and iCloud accounts) Note: IMAP only supports mail. Microsoft, Sync account in Outlook for Mac to Microsoft Cloud

So a Google account added to the current Outlook for Mac brings its calendar with it. The same is true for iCloud. An account added as generic IMAP brings mail only, which is the single most common reason a calendar fails to appear after what looked like a successful setup. If the calendar is missing, check how the account was added before checking anything else.

Microsoft also documents an alternative to routing through its cloud. During setup, the option described as syncing directly with the provider turns the Microsoft Cloud path off, which matters for anyone whose organisation has a view about where mailbox data is copied. POP accounts cannot use the cloud path at all.

For iCloud specifically, the route is Tools, then Accounts, then Add an Account, then Sign In. If the provider is not detected automatically, the window offers a link to choose a different provider, and iCloud can be selected from that list. Microsoft notes that this replaced the older workaround of subscribing to a published iCloud calendar through Outlook on the web.

Legacy Outlook for Mac cannot do this, and it has a date

The legacy client behaves differently enough that half the advice circulating about Mac Outlook calendar sync applies to a version that is about to stop working.

Microsoft states plainly that the legacy client does not support the CalDAV or CardDAV internet standards, which is why adding an iCloud email account to it never brought the calendar along. The published feature comparison puts Gmail, iCloud and Yahoo calendar and contact support in the column available only in the current Outlook. The same comparison lists several other calendar features as current-Outlook only, including the three day calendar view, group calendars, the macOS calendar widget and reminders in the macOS notification centre.

The deadline comes from the underlying service. Microsoft's support notice states that Exchange Web Services in Exchange Online is being retired on 1 October 2026, and that starting in October 2026 the legacy client stops working against Exchange Online mailboxes. On-premises Exchange mailboxes are given until 9 October 2029.

Switching is a toggle. In the legacy client it is the Legacy Outlook switch, and the return path was moved to the Help menu as Revert to Legacy Outlook. Two exceptions are documented. Administrators can pin users to one experience or hide the switch, and Microsoft has removed the revert option entirely in the Office 2024 Home and Business consumer version for macOS, recording that as by design rather than a fault.

Apple's side of the same transition is documented too. Apple's deployment guidance notes that it is working with Microsoft to move Mail, Calendar, Contacts, Notes and Reminders to the Graph API in a future update to macOS 27, for the same reason.

The other direction: a work calendar inside Apple Calendar

Putting Exchange or Microsoft 365 into the Mac's own Calendar application is the setup that makes work events visible to Spotlight, to the menu bar and to every other application on the machine.

Apple documents two entry points that produce the same result. In Calendar, choose Calendar and then Add Account, select the provider and follow the prompts. In System Settings, open Internet Accounts, click Add Account, and either enter the address or choose the provider from the list. Accounts from providers that are not listed, including a work mail or calendar server, go through the other account option.

One limitation here is documented by Apple and almost never mentioned elsewhere, and it decides whether this setup is viable for anyone who works with a shared calendar or an assistant.

You can add calendars to your Exchange calendar account, but you won't be able to see updated invitations or attendee responses for events in those calendars. Also, events in the additional calendars won't be visible to delegates. Apple, Add calendars and calendar accounts in Calendar on Mac

Apple states that full calendar features are available only in the main Exchange calendar, the one named Calendar. Extra calendars created underneath an Exchange account on the Mac are therefore fine for personal organisation and unreliable for anything involving other people. For a schedule that runs on invitations and responses, the main calendar is the one to use, and the categorisation people want from extra calendars is better handled with a separate account.

Where the duplicates actually come from

Four causes account for nearly all of them, and each has a different fix.

The same calendar added twice by different means is the first, as described above. The fix is to remove the subscription and keep the account, never the reverse, because the subscription is read-only.

Meeting invitations arriving as both an invitation and a forwarded attachment is the second. Accepting one and opening the other creates two events that look identical but are not linked.

Two applications writing to the same calendar during a migration is the third. This shows up while an old setup is still running alongside a new one, and it resolves itself once the old account is removed rather than merely signed out.

The fourth is specific to Google accounts synced through Outlook. Microsoft's known issues list notes that to respond to meeting invitations from Google, the meeting has to be on the calendar already, which depends on the Google setting that automatically adds invitations. A setup where invitations are not auto-added produces a pattern of events that appear only after being answered elsewhere, which reads like a sync failure and is not one.

Limits worth knowing before relying on it

Microsoft publishes a list of known issues for Google accounts synced to its cloud, and several of the entries are the kind that only surface once the setup is trusted.

Behaviour	What Microsoft documents
Shared Google calendars	Appear automatically in the left pane, but the Open Shared Calendar button does not work with them
Number of shared calendars	A limit of 20 calendars shared with the account
Attachments on events	Not currently supported
Weather calendar	Does not appear in Outlook
Categories, tasks, notes, rules	Not supported

None of these are defects to be reported. They are the current shape of the integration, and the twenty calendar limit in particular is worth checking against reality in an organisation where calendars are shared liberally.

Two checks that confirm the direction is right

Sync is easy to declare finished too early, because inbound events arrive first and they are the ones people look at. The two checks below take five minutes and catch the failures that otherwise surface during a meeting.

The first is a write test in the less obvious direction. Create an event in the application that was set up second, then confirm it appears in the first one and in the provider's own web view. A setup that reads correctly and writes nowhere is common when a calendar has arrived as a subscription rather than as an account, and this is the quickest way to tell the two apart.

The second is an invitation test with a real person. Send an invitation from the work mailbox to a personal address, accept it there, and check that the response comes back and is visible on the organiser's side. This exercises the part that matters most and the part that fails most quietly, especially on an Exchange account where the event was placed in a secondary calendar rather than the main one.

If either check fails, the cause is in how the account was added, not in a preference that can be adjusted. Removing the account and adding it again through the provider's own sign-in resolves most of these, and takes less time than reading through settings looking for a switch that does not exist.

A setup that holds

For a Mac with one work mailbox and one personal Google or iCloud account, the arrangement that causes the fewest surprises is a single window with both accounts added natively, whichever window that is. Everything else stays out of the way.

Where the work mailbox has to stay in Outlook for policy reasons, the second best arrangement is Outlook for work alone, macOS accounts for everything else, and no subscriptions bridging the two. The schedule is then read in two places, which is mildly annoying and completely predictable, and a desktop calendar that can show several accounts on one grid is the usual way of getting the overview back without creating a third copy of anything. The comparison of Mac calendars covers which ones connect to what.

What to change first

Find out how each account was added before changing anything, because an account added as IMAP will never produce a calendar no matter what is adjusted afterwards. If the work mailbox still runs through the legacy Outlook client, that migration now has a date on it and should go first. Once the accounts are correct and one schedule is visible in one place, the remaining problem is usually the week itself rather than the sync, which is where travel time between meetings and how fast an event can be entered start to matter more than anything in this article. Caltimate is built for that stage.