MPUG Editorial · September 15, 2026 · ~4 min read · Category: Microsoft Tooling

Microsoft is retiring Teams Google Calendar sync in October 2026, and if your program spans both stacks, your availability picture is about to go quietly stale. Calendars that were previously matched and configured for synchronization will simply stop syncing — no error, no banner, no announcement to the people whose meetings you are trying to book. For project managers coordinating across a client, a vendor, or an acquired business unit that runs on Google Workspace, this is a scheduling risk with a date on it.

What Microsoft is actually changing

According to Microsoft Learn documentation on Google Workspace and Teams calendar syncing, beginning October 2026, calendar syncing between Google Workspace and Microsoft Teams will no longer be supported. Three specific things happen:

• Calendars previously set up for syncing stop syncing.
• Admins lose the ability to manage calendar sync from the Admin app within Teams.
• Admins also lose custom domain management from that same Admin app, though they can continue managing the custom domain from the Microsoft Admin Center.

Microsoft began notifying affected customers in August 2026 through the Microsoft 365 Message Center, tagged as a major change with both user and admin impact. The company frames the retirement as a decision to focus investment on supported integration experiences.

Who this affects — and who it does not

This is narrower than it sounds, which is exactly why it will catch people out. The retirement applies to organizations using the calendar sync capability available through the Admin app in Teams. If your organization never turned that on, nothing changes for you.

If it was turned on — often years ago, often by someone who has since moved on — nobody in your delivery chain is likely to know. That is the failure mode worth planning for.

Why it matters for project managers

Scheduling is the most boring dependency in your plan and the one most likely to cost you a week. A broken calendar sync does not fail loudly. It fails as a slow accumulation of double-bookings, phantom free slots, and a stakeholder who “never got the invite” — and it takes several rounds of that before anyone traces it back to a platform change that happened a month earlier.

Two practical consequences:

Your free/busy data becomes unreliable for cross-org scheduling. Any process that depends on seeing a Google Workspace colleague’s availability from Teams needs a replacement path before October, not after the first missed steering committee.

This belongs on the risk register, not the to-do list. It has a known date, a known trigger, and a known mitigation — which makes it one of the easiest risks you will log all quarter. If you want a refresher on choosing the right response rather than defaulting to mitigate, MPUG’s on-demand master classes cover risk response selection in depth, and you earn a PDU while you are there.

What to do next

• Confirm whether calendar sync is actually in use. Ask your Microsoft 365 admin to check the Admin app in Teams before the setup screen disappears.
• Retrieve account matching information now. Microsoft’s guidance is explicit: retrieve and retain any account matching data you may need from the Admin app in Teams before the retirement date. After October, it is gone.
• Point users to the supported path. For people who schedule Teams meetings from Google Calendar, the Microsoft Teams Meeting add-on for Google Workspace remains the supported integration.
• Tell your stakeholders before the sync tells them. A one-line note in your status report in September costs you nothing. Explaining three weeks of scheduling chaos in November costs you credibility.
• Log it. Add the October date to your risk register and your PDU tracker reminder cycle so it does not fall through the seam between two months.

How this fits the broader Microsoft work-management shift

This retirement lands during a busy stretch for Microsoft’s project and collaboration tooling. Project Online reaches end of life on September 30, 2026, Planner continues absorbing Project capabilities, and Copilot is being threaded through task and meeting workflows. The through-line is consolidation: Microsoft is narrowing the supported integration surface and investing in the paths it intends to keep.

For PMs, the practical read is that cross-platform conveniences set up years ago are the ones most likely to be retired next. If you are rebuilding your Microsoft tooling skills for this environment, MPUG’s Microsoft Project training path, Microsoft Planner training, and Microsoft Teams training all cover current versions rather than the ones in the manual.

Frequently asked questions

When exactly does Teams Google Calendar sync stop working? Microsoft’s documentation states that calendar syncing between Google Workspace and Microsoft Teams will no longer be supported beginning October 2026. The Message Center notice lists an act-by date of October 1, 2026.

Can I still schedule Teams meetings from Google Calendar afterward? Yes. Microsoft directs users to the Microsoft Teams Meeting add-on for Google Workspace, which remains a supported integration. What goes away is the bidirectional calendar sync configured through the Admin app in Teams.

Does this affect my custom domain settings in Teams? Admins will no longer manage the custom domain from the Admin app in Teams, but custom domain management continues to be available in the Microsoft Admin Center.

The bottom line

This is a small change with a disproportionate blast radius for anyone running work across two ecosystems. It costs about ten minutes to check whether your organization uses the sync, and considerably more than that to untangle a month of scheduling failures that nobody connected to a platform retirement. Check now, export the account matching data, and put the October date somewhere your future self will see it.

Source: Set up calendar syncing between Google Workspace and Microsoft Teams — Microsoft Learn. Verify licensing and tenant-specific details, including your own Message Center notices, against Microsoft’s primary documentation before acting.