How to keep your own calendar private on a client’s Microsoft 365 tenant

When a client sets you up with an Outlook account inside their Microsoft 365 tenant, you have a calendar you don't fully control. Their IT department owns the mailbox, their colleagues can usually see into it, and anything you put on it — a meeting with another client, a personal appointment, a note to yourself — is visible inside their organisation. At the same time, that tenant calendar needs to know when you're busy with them, and your own calendar needs to know when you're busy with everyone else. The short version: keep the tenant calendar to tenant business only, block time on it as plain “Busy,” and don't rely on invite-forwarding or manual copying to keep the two sides in sync — connect the accounts with busy-only mirroring instead, or fall back to a share link if the tenant won't allow a third-party app at all.

The one-way trust problem

A client-tenant calendar is not neutral ground. Anything with a title, description, or attendee list on it is visible to whoever in that organisation can see your calendar — which, on a lot of Microsoft 365 setups, is more people than you'd guess by default. That rules out the obvious fix of just putting your other clients' meetings on it with real titles. You also can't make the trust flow the other way: there is no setting that lets a client's tenant read your personal or other-client calendars and show your real availability there. The tenant calendar only ever knows what you put on it.

So the actual goal is narrower than “keep everything in sync.” It's: the tenant calendar should show you as busy exactly when you're unavailable, with no explanation of why, and your own calendar should show the same for whatever time the client has booked with you. Nothing else needs to cross the boundary.

The manual options, and where each one breaks

The most common approach is to duplicate events by hand: every time something lands on another calendar, you open the tenant account and add a matching “Busy” block, no title, no details. It works, and it's the safest option if you only ever have one or two other things going on, because you're the one deciding exactly what crosses over. It also fails quietly — you forget one, or a meeting moves and you don't move the copy, and now the tenant calendar is wrong in a way nobody notices until someone gets double-booked.

Free/busy sharing — the built-in Outlook and Microsoft 365 feature that lets colleagues see when you're free without seeing what you're doing — only works insidea tenant, between accounts on the same organisation's Microsoft 365 setup. It does not cross into a different tenant unless both admins set up an organisation relationship, and it has nothing to say about a Google Calendar you use for other clients. It solves visibility for people already inside the client's organisation; it does nothing for the boundary between that organisation and the rest of your work.

Forwarding or auto-accepting invites into a personal calendar is the other common shortcut, and it's the one to avoid here. It copies the full event — title, description, attendees — out of the tenant account, which usually means client meeting details leaving an environment your contract or their IT policy expects to stay contained. It also only runs one direction: the client's tenant still won't know about your other commitments.

A busy-only mirror between the tenant account and the rest of your calendars

The automated version of the manual copy is a calendar mirror set to busy-only mode: it copies a plain “Busy” block — no title, no description — from one calendar to another whenever an event appears, and removes or moves the copy when the source is rescheduled or deleted. Set up in both directions between your tenant Outlook account and your other calendars, it does exactly what the manual version does, without you remembering to do it: the tenant calendar shows you unavailable during your other work, and your own calendars show you unavailable during tenant meetings, with neither side learning what the time is for.

What crosses the boundary is the time only. What never crosses: the event title, description, attendee list, or which other client or calendar the block came from. BusyBoard is the automated way to run this — it connects both a verified Google account and a verified Microsoft 365 account, mirrors busy-only blocks between them, and never modifies the original event on either side. Mirroring between calendars is a Pro feature, with a 14-day free trial and no card required to start it.

The admin-consent question

Connecting a client-tenant Outlook account to any third-party app requires the account owner's consent, and on some Microsoft 365 tenants — usually the more security-conscious ones — a tenant admin also has to approve any third-party app before it can be connected at all. That approval is the client's IT department's call, not yours, and it can take anywhere from a few minutes to a few weeks depending on how their process works. BusyBoard has completed Microsoft's publisher verification, requests calendar access plus basic sign-in (no mail, no files, no directory), and stores no event content from a connected calendar — details worth having ready if you're the one asking their admin to approve it.

Even so, some tenants will say no, or simply never get to it. That's worth planning for rather than waiting on.

If you can't connect the tenant account at all

If admin consent is denied — or the request just sits unanswered — mirroring isn't available for that calendar in either direction. A mirror needs an active connection to both calendars it copies between, so a blocked tenant account can't send or receive busy-only blocks at all, no matter which way you'd want the time to flow.

The honest fallback in that case is the same combination as before, minus the automation on one side: connect whatever calendars you're actually allowed to connect — your personal calendar, your other clients' — and mirror busy-only blocks between those, and for the client on the blocked tenant, send a share link instead. A share link shows your real, merged availability from the calendars you canconnect, without asking the tenant to grant a third-party app access to anything. For your commitments to that client specifically, you're back to blocking time by hand on your other calendars whenever the tenant books you, the way we described above, since nothing can read that calendar automatically until — or unless — the admin says yes.

See our guide on stopping double-bookings across clients for the broader pattern this fits into when you're juggling more than one calendar boundary at once.