Calendar Without Admin Approval: A Guide

Q: Can it create events in my client's calendar?

No. Tab Sync is read-only on the source calendar. Writing into a client tenant is exactly the kind of access that requires admin approval, so manyCalendars does not do it.

Why is this so hard?

You work with more than one company, so you live in more than one calendar. A client's Outlook here, another client's Google Workspace there, your own personal calendar underneath it all. Every tool that promises to combine them wants to connect to those accounts first, and on a managed tenant that connection needs someone else's permission. Finding a calendar without admin approval, one that just shows you your own schedule without filing a consent request with somebody's IT department, turns out to be strangely difficult. This guide explains why, and what actually works.

Every tool asks because every tool connects

Almost every calendar aggregator on the market is a cloud service. CalendarBridge, OneCal, Reclaim.ai, Morgen: all well-built tools, and all built the same way. You connect each account through OAuth, the service receives a token, and its servers use that token to read your events and move them around. The model has real advantages. It works on your phone, it can write events back to the source, and it keeps running while your laptop is closed.

It also has one structural requirement: the tenant that owns each account must allow the connection. Your client's Microsoft 365 is not your account. It is theirs. When a third-party app asks for calendar permissions on it, the tenant decides whether that is allowed. All four vendors above publish help articles walking users through requesting admin approval on managed Microsoft tenants, because their OAuth model requires a per-account connection and managed tenants routinely block it. The consent screen is not a bug in these products. It is the foundation they are built on.

November 2025: the default flipped

It used to be that many tenants let users consent to low-risk apps on their own. 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 has to approve the app before anyone in the tenant can connect it. Existing grants were grandfathered in, but every new connection hits the wall.

That one default change turned "connect your work calendar" from a ten-second step into an IT ticket. We cover the change itself in Microsoft blocks calendar apps by default, and what the approval screen actually means in why your calendar app says it needs admin approval.

Why IT says no, and why they are usually right

It is tempting to read a denied request as laziness. It usually is not. From the tenant's side, approving a calendar app means letting a third-party server hold a standing token to organizational data. Meeting titles, attendee lists, dial-in links, and event notes flow to infrastructure the org does not control and cannot audit. For a firm with confidentiality obligations, that is a real risk, not a hypothetical one.

And you are often not even an employee. A contractor asking a client's IT team to approve an unfamiliar app, for the convenience of someone who rolls off the project in six months, is asking them to accept permanent risk for temporary benefit. Most will decline, and honestly, they are doing their job. The fix is not a better-worded ticket. The fix is a tool that never needs the ticket. That matters most for people juggling several tenants at once: consultants, fractional executives, agency contractors, and MSP technicians.

The workarounds people try first

Before giving up, most people reach for the obvious escape hatches. On a locked tenant, most of those doors are closed too:

Export to .ics. Often disabled by policy, with the menu item simply grayed out. See when Outlook calendar export is disabled.
Google's secret iCal address. Workspace admins can turn it off, and on locked domains it just is not there. See when the secret address is missing.
Forwarding invites to a personal account. Fragile, easy to forget, and frequently against the client's own policy.
Keeping every calendar open in its own tab. This one actually works. It is just miserable, and flipping between four tabs all day is exactly how double bookings happen.

We map the whole locked-tenant landscape in how to see calendars IT blocked and how to see your work calendar without IT help.

The local approach: read what you can already see

Notice what that last workaround proves: you already have access. You can open each calendar in a browser tab, signed in as yourself, through the org's own login and MFA. Nobody needs to approve that. It is just you, using the account you were given, the way you were told to use it.

manyCalendars builds on exactly that. It is a desktop browser extension with a feature called Tab Sync: a calendar in your combined view follows a tab you are signed into and shows the events visible there alongside everything else you have added. Because it reads what you can already see in your own browser, there is no OAuth token, no server-side account connection, no consent screen, and nothing installed on any tenant. Your calendar data stays on your machine. It is the only calendar tool we know of that works when IT says no.

Alongside Tab Sync, the Free tier lets you add unlimited manual calendars from .ics files and feed URLs, with month, week, and day views and color coding, 100 percent local, no account needed. The deeper mechanics are in merge calendars without OAuth and sync a calendar without connecting the account.

Honest limits

This approach has boundaries, and you should know them before you rely on it:

It is a desktop browser extension. There is no phone app.
Tab Sync reads what is visible in a tab you are signed into. If you cannot open a calendar yourself, manyCalendars cannot show it to you either.
It is read-only on the source. It will not create or edit events in a client's calendar, which is also precisely why there is nothing for an admin to approve.

If you need true two-way sync across accounts and every tenant you work with will approve the connection, an OAuth service is the better fit. CalendarBridge is a serious product: patented server-mediated two-way sync, booking pages, a HIPAA BAA, at 4, 8, or 32 dollars per user per month depending on tier. We compare the trade-offs honestly in manyCalendars vs CalendarBridge and manyCalendars vs OneCal.

What it costs

Free is genuinely free: unlimited manual calendars from .ics files and feed URLs, all views, color coding, everything local, no account. Pro is $15/month or $150/year ($12.50/month equivalent) and adds Tab Sync, meeting reminders, a custom work-week view, time zones, and .ics export. Premium is $29/month or $290/year ($24.17/month equivalent) and adds Privacy Mode for screen sharing, cross-calendar conflict detection, auto-block busy mirroring, and availability sharing. Team is $39/seat/month or $390/seat/year with a 2-seat minimum. Full details are on the pricing page.

Every install starts a 14-day trial of everything. No card, no account. Install it free and point it at the tabs you already have open.

The full guide, by situation

This page is the hub. Each guide below goes deep on one specific situation, so you can jump straight to yours.

When IT has things locked down

Merging and combining calendars

Day-to-day multi-client work

Who this is for

Comparisons

Frequently asked questions

Does "no admin approval" really mean nothing at all?

Yes. Nothing is installed on any tenant. There is no app registration, no consent grant, no token. The extension lives in your own browser and reads calendar tabs you are already signed into. From the tenant's side, you are simply using the web calendar they gave you.

Is this against my client's rules?

manyCalendars does not bypass any authentication and cannot show you anything you cannot already open yourself. It is read-only on the source. That said, engagement letters and acceptable-use policies vary, and they are yours to check. We would rather say that plainly than pretend the question never comes up.

What happens when a calendar's tab is closed?

Your combined view keeps the events it last read and picks up changes the next time that calendar's tab is open. Tab Sync follows tabs. It does not connect to any server in the background.

Can it create events in my client's calendar?

No. Tab Sync is read-only on the source. You can keep your own manual calendars inside manyCalendars and export them as .ics on Pro, but writing into a client tenant is exactly the kind of access that requires approval, so we do not do it.