How to Merge Calendars Without OAuth

The merge everyone wants, the connection nobody can get

If you work across two or more organizations, you want one merged view: every meeting from every account on one screen, conflicts visible at a glance. Every mainstream tool builds that view the same way, by connecting to each account through OAuth. And that is exactly where it breaks on a managed tenant. This page covers how to merge calendars without OAuth, why the connection-based model fails for contractors and consultants, and what a local merge looks like instead.

Why OAuth mergers stall on managed tenants

OAuth is how a cloud service gets standing permission to read an account. You click "connect", the provider issues the service a token, and the service's servers pull your events from then on. It is a per-account handshake: every calendar you want merged needs its own connection, approved by whoever owns that account's tenant.

On your personal Google account, that is you, and it takes ten seconds. On a client's Microsoft 365, it is their IT department. Since November 2025, Microsoft Entra's default settings block user consent to third-party apps requesting calendar permissions (Calendars.Read and Calendars.ReadWrite). An admin must approve the app first. Existing grants were grandfathered, but new connections wait in a queue, often indefinitely. This is why CalendarBridge, OneCal, Reclaim.ai, and Morgen all publish admin-approval help articles for managed Microsoft tenants: their model cannot work without the handshake. One client saying no, or just never answering the ticket, and your merged calendar has a permanent hole in it. We cover the Microsoft change in detail in Microsoft blocks calendar apps by default.

Credit where it is due

None of this makes OAuth tools bad. CalendarBridge in particular is a serious product: patented server-mediated two-way sync, booking pages, a HIPAA BAA for regulated industries, priced at 4, 8, or 32 dollars per user per month depending on tier. If every tenant you work with will approve the connection, it does things a local tool cannot, like syncing events between accounts while your laptop is closed. We wrote up the full comparison in manyCalendars vs CalendarBridge and manyCalendars vs OneCal.

The problem is not quality. The problem is the word "approve". A consultant with four clients needs four separate tenants to say yes. In practice, at least one will not.

Tab Sync: a merge with no connection at all

manyCalendars merges differently. It is a desktop browser extension. You open each calendar in a browser tab, signed in as yourself, exactly the way you already do. Tab Sync then makes a calendar in your combined view follow that tab, showing its events alongside every other calendar you have added. Your Google Calendar in one tab, a client's Outlook in another, and one merged view shows both, color coded per calendar.

No account connection ever happens. There is no token to issue, no consent screen to clear, no server holding your data, and nothing installed on any tenant. IT has nothing to approve because you are not asking for anything beyond the access you already have. As far as we know, it is the only calendar tool that works when IT says no. The same idea, applied to a single account, is covered in sync a calendar without connecting the account.

A concrete Tuesday: a fractional CFO signed into two client Outlook tenants and a personal Google account opens three tabs in the morning, and the combined view shows a 10 a.m. board prep at client one, an 11 a.m. close review at client two, and a 3 p.m. school pickup, stacked on one week grid. When the second client moves the close review, the change appears the next time that tab is in view. Nobody at either client did anything, because there was nothing for them to do.

What a local merge cannot do

Being honest about the trade-offs:

• Tab Sync reads what is visible in a tab you are signed into. No tab access, no merge.
• It is read-only on the source. It will not copy events between accounts or write anything back.
• It is a desktop browser extension. The merged view lives in your browser, not on your phone.

If those limits are dealbreakers and your tenants cooperate, use an OAuth service. If your tenants do not cooperate, those limits are the price of a merge that actually happens.

What you need to get started

The Free tier handles unlimited manual calendars from .ics files and feed URLs, with month, week, and day views and color coding, 100 percent local, no account needed. Tab Sync is part of Pro at $15/month or $150/year ($12.50/month equivalent), alongside meeting reminders, a custom work-week view, time zones, and .ics export. The full ladder is on the pricing page.

Every install starts a 14-day trial of everything, no card, no account, so you can test Tab Sync against your real calendars before paying anything. Install it free, open your calendar tabs, and watch them merge.