Why Busy Is Missing Across Microsoft 365 Tenants

Your client colleague opens Microsoft Outlook on their computer. They click New Meeting to organize a project review with you.

They add your client tenant email address to the attendee field. Then they open Outlook Scheduling Assistant to locate a shared opening.

Outlook Scheduling Assistant renders a horizontal grid of time across the working day. Every colleague in their organization appears on this grid.

Green and white boxes indicate open working time. Purple or blue bars indicate that an attendee is already booked.

Your row shows entirely empty white slots for the upcoming afternoon. The scheduler assumes you have no commitments during that hour.

Just as Google Find a time inspects only its own workspace, Outlook Scheduling Assistant checks only your client directory.

The client picks that hour because your row looks completely open. They send the meeting invite without hesitation.

They do not know that you booked an executive presentation during that exact hour. That presentation lives on your firm calendar in your own organization.

Exchange Online enforces strict boundaries around each Microsoft 365 tenant. A tenant acts as a secure container for one company data environment.

The free/busy service inside Exchange handles availability queries. This service resolves queries by checking user mailboxes on the local tenant directory.

When a scheduler adds your client account, Exchange checks only that specific mailbox. It does not know that you operate a second tenant mailbox elsewhere.

Your firm account lives in a completely separate Microsoft 365 tenant. The two directories do not share identity records or calendar databases.

Microsoft documents that free/busy between two organizations is shared only when both sides set up an organization relationship. Most companies leave that off. The hour on your firm calendar stays there, and no message reaches the client tenant.

Even when organizations attempt federation, IT policies often restrict sharing to plain free/busy or block external domains entirely. External lookups regularly fail silently.

Because no connection exists, the hour you placed on your firm calendar remains trapped there. No message travels to the client tenant.

The client Exchange server looks at your client mailbox and sees an empty calendar folder. It reports your status as free to Outlook Scheduling Assistant.

You might try using a personal booking link to solve cross-tenant collisions. A booking link does not solve this issue.

Internal colleagues at a client organization do not use external scheduling links to book team members. They expect you to show accurate availability inside Outlook Scheduling Assistant.

If a project lead wants to meet, they open the native schedule grid. Sending them a personal scheduling link creates friction and looks unprofessional.

A booking link also requires manual coordination. It expects the other person to change their daily workflow to accommodate your separate calendars.

Another common workaround is subscribing to an external ICS feed across accounts. Subscribing to an ICS feed fails to solve the problem.

When you add an Internet Calendar via ICS URL into Outlook on the web, Exchange creates a separate secondary calendar. It places this calendar in your Other Calendars folder.

Exchange Online never reads secondary or subscribed calendars when calculating free/busy availability. Outlook Scheduling Assistant reads only the default primary Calendar folder of your mailbox.

Events from an ICS feed appear visually on your personal screen when you overlay calendars. Yet those events remain invisible to every other person in the organization.

To fix this breakdown, an event must exist on the default primary calendar inside the client Microsoft 365 tenant. There is no other mechanism.

Outlook Scheduling Assistant reads only default primary calendars. Any busy block from your firm account must replicate directly into that primary client mailbox.

The event inside the client tenant must carry the standard Busy availability status. It must occupy the exact start and end times of your original meeting.

Crucially, the replicated block must protect client data. It omits attendee lists. It strips meeting descriptions. It removes client titles.

The replicated event needs only a neutral title such as Busy. This marks your availability accurately without leaking confidential information across client boundaries.

OnlyBusy writes native calendar events directly between your two calendars to secure your schedule. It mirrors your busy hours without exposing sensitive client notes.

Current plans are on the OnlyBusy pricing page.

When a real event lives on your primary calendar, Outlook Scheduling Assistant updates instantly. The next time a client scheduler checks your name, the purple bar blocks that hour.