How to Sync Your Work Outlook Calendar to Skylight, Google Calendar, or Other Apps When IT Blocks Direct Sync

This comes up constantly for people trying to sync their work Outlook calendar to a household calendar device like Skylight, a shared family Google Calendar, or any other third-party app — they request access, and IT denies it. This isn't usually IT being unreasonable for the sake of it. Most organizations restrict outbound calendar sync by default because a work calendar can quietly leak more than just "busy" times — meeting titles, attendee lists, and locations can expose client names, deal details, or internal project information to apps and accounts outside the company's control. Once you understand that's the real concern, the workarounds make a lot more sense.

Option 1: Ask for a "busy-only" feed instead of full sync

Before trying any workaround, it's worth going back to your IT admin with a more specific request. A blanket "let me sync my calendar" request is an easy no, because it sounds like full access to everything on it. A request to publish a busy/free-only feed — no titles, no attendees, no locations, just blocks of time marked busy — is a much easier yes, because it removes the actual data-leak concern IT is worried about.

In Outlook, this is technically possible through a published ICS calendar link with privacy settings limited to free/busy information. Many IT departments that would never approve full sync will approve this, because it gives you what you actually need (when you're free or busy) without exposing anything sensitive. If your admin previously said no to a general request, it's worth asking again with this specific framing.

Option 2: Forward meeting invites to your personal calendar

The simplest workaround that requires no setup at all: when you receive or create a meeting in Outlook, forward the invite to the personal email address connected to your Skylight, Google Calendar, or other app. Most calendar apps automatically detect calendar invite attachments (.ics files) in forwarded emails and offer to add the event.

This is manual and a little tedious for a packed week, but for most people it takes just a few minutes to forward the week's meetings in one sitting. It has the advantage of being completely within company policy, since you're not syncing anything — you're just manually sharing specific events you choose to share, the same as forwarding any other email.

Option 3: Use Outlook categories with Power Automate (semi-automated)

If you want something closer to automatic without needing IT's involvement, Microsoft Power Automate (included with most Microsoft 365 plans) can watch for a specific category you apply to events and automatically copy those to a personal Google Calendar, which your third-party app then reads normally.

Here's how to set it up:

1. In Outlook, create a category — something like "Personal Sync" — that you'll apply to any meeting you want visible elsewhere.
2. Go to make.powerautomate.com and sign in with your work Microsoft 365 account.
3. Create a new Automated cloud flow.
4. Set the trigger to Office 365 Outlook → When a new event is created (V3).
5. Add a Condition step. On the left side, insert the dynamic Categories field (not typed text — it needs to be the actual dynamic content field for this to work). Set the operator to contains, and on the right side, type your category name (e.g. Personal Sync).
6. Under the "If yes" branch, add a new step: Google Calendar → Create an event.
7. Map the fields: Start time → the dynamic Start time with time zone field; End time → the same for end time; Title → you can prefix it with something like "Busy:" plus the dynamic Subject field if you don't want full meeting titles visible; Location and Description are optional and worth leaving out if you'd rather keep details private.
8. Save the flow, then test it by creating a new Outlook event with your category applied.
9. Once events are landing in Google Calendar correctly, connect that same Google account to Skylight (or whichever third-party app you're using) — it'll pick up the synced events automatically going forward.

Which option to actually use

• If you rarely need this and don't mind a few minutes of admin each week: forwarding invites (Option 2) is the lowest-effort, zero-setup choice.
• If you want it mostly automated and are comfortable with a one-time setup: the Power Automate flow (Option 3) is worth the fifteen minutes it takes to configure — after that, it runs on its own.
• If you want the cleanest long-term solution: go back to IT with the busy-only feed request (Option 1). It's the only option that doesn't require you to manually maintain a workaround indefinitely, and it directly addresses why IT said no in the first place.

Why IT locks this down in the first place

It's worth understanding the reasoning, partly because it makes the busy-only request land better. A full calendar sync to a personal account or third-party app effectively creates an uncontrolled copy of your calendar data outside the company's security boundary — meeting titles can reveal who's meeting with whom about what, attendee lists can expose org structure or client relationships, and locations can reveal travel or site visit patterns. None of that is usually sensitive in any one instance, but IT departments tend to apply blanket policies rather than evaluate every individual's calendar content case by case, since that's far more practical to manage at scale. Understanding that the policy is about data categories, not about distrust of you personally, makes it easier to find a workaround everyone's comfortable with.