Why Your IT Department Cannot Fix Your Calendar Problem
Posted: June 2, 2026 · 7 min read
The cross-organization calendar gap
Calendar software was designed for people who work at one company. Google Calendar assumes everyone you collaborate with is in the same Google Workspace domain. Microsoft Outlook assumes everyone is in the same Microsoft 365 tenant. Both products have excellent features for scheduling within a single organization: shared calendars, free/busy lookups, automatic room booking, scheduling assistants that find open time across teams.
None of that works across organizations. If you are a contractor with a Google Calendar at Client A and an Outlook calendar at Client B, those two calendars exist in completely separate universes. Client A's scheduling assistant cannot see your meetings at Client B. Client B's free/busy lookup has no idea you are booked solid on Client A's Google Calendar from 10 to 11 AM.
This is not a bug. It is a deliberate security boundary. Organizations do not want external parties seeing their employees' calendars, and for good reason. But the side effect is that anyone who works across multiple organizations is left with no way to see their own complete schedule in one place.
Why ICS feeds are not the answer
The standard workaround is ICS (iCalendar) feeds. Google Calendar can publish an ICS URL that other calendar apps can subscribe to. In theory, you could subscribe your Outlook calendar to your Google Calendar's ICS feed and see both in one view.
In practice, this fails for three reasons:
Most corporate tenants disable ICS publishing. Enterprise IT administrators turn off ICS feed generation as a security measure. They do not want employees accidentally sharing their calendar URLs with the outside world. If your client's Google Workspace or Microsoft 365 admin has disabled ICS publishing (and most have), the feed URL does not exist.
ICS feeds lag by hours. Even when available, ICS subscriptions do not sync in real time. Google Calendar refreshes external ICS subscriptions roughly every 12 to 24 hours. Outlook is slightly faster but still measured in hours, not minutes. A meeting booked at 9 AM might not appear in your subscribed view until late afternoon. By then, you have already double-booked yourself.
ICS feeds are read-only and stripped down. Subscribed events cannot be edited, moved, or used for conflict detection in most calendar apps. They show up as flat, non-interactive entries. You cannot RSVP, you cannot see attendee lists, and in some implementations you cannot even see the full event description or meeting links.
Why cross-tenant federation requires admin access you will never get
Microsoft 365 does have a feature called Organization Relationships that allows two tenants to share free/busy data. Google Workspace has a similar feature called Calendar Interop. In theory, these could solve the problem.
In practice, setting up cross-tenant federation requires a Global Administrator in both organizations to configure the trust relationship. As a contractor, you do not have Global Admin access to either tenant. You probably do not even know who the Global Admin is. And even if you did, no enterprise IT team is going to configure a federation trust because a single contractor asked for it. The security review alone would take longer than your contract.
This is the core of the problem. The technical capability exists, but the organizational reality makes it inaccessible to the people who need it most. Contractors, consultants, fractional executives, and anyone else who works across organizational boundaries are stuck in the gap between what the technology can do and what IT will actually configure.
Cloud-based aggregators: solving one problem, creating another
Several calendar aggregation tools attempt to fill this gap by connecting to your calendars through OAuth and APIs. You grant the tool access to your Google Calendar, your Outlook calendar, and any others, and it merges them into a unified view on their platform.
This approach works, but it introduces trade-offs that many professionals are not comfortable with:
Your calendar data lives on their servers. Every event, attendee, description, and meeting link is synced to a third-party platform. If that platform gets breached, your complete professional schedule is exposed. If it gets acquired, your data goes with it. If it gets a legal request, your calendar history is discoverable.
OAuth access requires admin consent in many tenants. Enterprise Microsoft 365 tenants often restrict which third-party apps can receive OAuth tokens. If Client B's IT has configured an app allowlist, your calendar aggregator may not be able to connect at all. You are back to square one, except now you also have an account on a platform that only sees half your calendars.
You are trusting a third party with competitive intelligence. Your calendar reveals who you work for, how much time you spend with each client, and how your engagements are structured. For consultants managing competing clients, or for anyone whose work arrangement depends on discretion, sending that data to a cloud service is a meaningful risk.
The browser-based alternative
There is a category of calendar tools that sidesteps all of these problems by working entirely within your browser. Instead of connecting to calendars through APIs and syncing data to a server, they read your calendars from the browser tabs you already have open.
This approach has several advantages for multi-organization professionals:
No IT approval required. The tool reads what is already on your screen. It does not need OAuth tokens, API access, or admin consent. If you can see your calendar in a browser tab, the tool can read it. This works regardless of what Client A's or Client B's IT has configured.
No server, no sync, no data leaving your machine. Your calendar data stays in your browser's local storage. There is nothing to breach, nothing to subpoena, and nothing to sell. If you uninstall the extension, the data disappears.
Works with any provider. Google Calendar, Outlook Web, Apple iCloud Calendar, Fastmail, any web-based calendar interface. The tool does not care which provider hosts the calendar. It reads the rendered events from the page, which means it works with any calendar you can open in a tab.
Real-time data. Because the tool reads from your live browser tabs rather than a cached ICS feed, the data is as current as the calendar itself. A meeting booked 30 seconds ago appears in your unified view the moment you refresh.
How manyCalendars compares to the alternatives
Here is a straightforward comparison across the dimensions that matter most to multi-organization professionals:
ICS Feeds
IT approval: Not needed (when available)
Real-time sync: No (12-24hr lag)
Conflict detection: No
Data location: On provider servers
Works when feeds are disabled: No
Cloud Aggregators (Reclaim, Morgen, etc.)
IT approval: Often required (OAuth)
Real-time sync: Yes
Conflict detection: Yes
Data location: Third-party servers
Works when feeds are disabled: Sometimes
Scheduling Tools (Calendly, Cal.com)
IT approval: Required per calendar
Real-time sync: Yes
Conflict detection: Within connected cals only
Data location: Third-party servers
Works when feeds are disabled: No
manyCalendars (Browser-Based)
IT approval: Not needed
Real-time sync: Yes (tab-based)
Conflict detection: Yes, cross-calendar
Data location: Your browser only
Works when feeds are disabled: Yes
The bottom line for contractors and consultants
If you work for a single employer, your IT department has already solved the calendar problem for you. Your meetings, your colleagues' availability, and your scheduling tools all live in one ecosystem. It just works.
If you work across multiple organizations, nobody has solved the calendar problem for you. Not your IT department (they cannot see across tenants), not the calendar providers (they built for single-org use), and not traditional scheduling tools (they need API access you may not have).
The solution has to meet you where you are: in the browser, with the calendar tabs you already have open, without requiring anyone's permission but your own. That is what manyCalendars was built for. No IT tickets. No admin consent. No cloud sync. Just your calendars, unified, on your machine.
Install manyCalendars for free and see what a complete picture of your schedule actually looks like.