Keep team calendars honest when Teams-Google sync ends: a manager script

A manager opens the team calendar and sees a meeting on one side and free time on the other. Microsoft began notifying affected customers in August 2026 about the Teams-Google calendar sync retirement. The preparation window is short.

The meeting hours are the first cost

Start with the shared calendar and mark every recurring invite that has not been reviewed recently. Meetings with no owner, no agenda, and no decision are debt. The invite is small; the hour is the real cost.

One calendar shows a meeting; the other shows free time. The mismatch is simple. The shared calendar is the first place the team sees the conflict. Double-booked meetings cost an apology. Skipped meetings cost the decision that was supposed to happen. Count both.

The script needs to beat the deadline

Administrators will lose access to the Teams-Google calendar sync setup in the Teams Admin app beginning in October 2026. Do not wait until that setup is gone. Use this five-line manager script:

The Teams-Google calendar sync will stop in October 2026.

If your calendar was matched, it will stop syncing the other side.

Use the Microsoft Teams Meeting add-on for Google Workspace, the booking tool Microsoft recommends, to book Teams meetings from Google Calendar.

Check recurring invites before October 1, 2026.

Ask for a reschedule when a meeting no longer has a clear owner.

Recurring invites need a cancel rule

Recurring invites add a standing cost to a full calendar. They survive because nobody owns the first decision. Keep the calendar useful. Meetings that have run without a visible outcome should be canceled, not renewed. Graceful cancels are short: name the meeting, say the load is too high, and offer a better format. For a decision, ask for a one-time meeting with an agenda. Otherwise, remove the recurring block. Make the calendar easier to trust, not punish the creator.

Keep the cancel message short: the meeting name and removal date, the reason in one sentence, and the replacement offer. Short cancels are easier to accept than a long explanation. The message also gives the creator a clear path back. The replacement should fit the meeting's purpose. Status updates can become written summaries. Decision meetings need a decision owner and a date. Social or training blocks can move to a lower-frequency slot.

The new calendar rule needs a test week

• Inventory the calendars in organizations that currently use the Teams-Google sync through the Teams Admin app, the group the retirement primarily affects. Turn them into a short table of names and recurring invites.
• Confirm the admin path is still available. Note where the sync setup was configured.
• Replace the sync with a booking rule. Leave a team note naming the tool that books the meeting.
• Review recurring invites before the deadline. Sort them into meetings that need an owner, a cancel, or a reschedule.
• Ask for reschedules in the same thread. Close with a reply naming the meeting, the conflict, and the proposed new time.

Pick the calendar that the team already checks first. Make it the source calendar for booking, links, and reschedules. The other calendar can still show a block, but it should not drive the schedule. The team should not have to ask which calendar is real. Answers to moved meetings should cite the booking rule, not a personal apology. That keeps the correction out of the manager's inbox.

For the test week, treat every conflict as a clue. Note which calendar showed the meeting, which one was empty, and who noticed the gap. Move meetings to the source calendar when the same person keeps missing blocks. Give a standing owner to any meeting that keeps drifting.