Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 272/272 feeds/APIs · 469/469 docs · 8/9 advisories · checked 11:37 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Bi-directional calendar syncing between Google Workspace and Microsoft Teams

Microsoft 365 Message Center Archive by Merill Fernando · Microsoft may not have sent this notice to your tenant.

Rollout

Roadmap
488093

Rollout dates are often only in the text. When Microsoft moves them, the change shows under "What changed".

Schedule dates changed in the text

Date phrases in schedule sentences differ between the versions this installation saw
  • Seen 16 May 2025 early May 2025 → late June 2025

Read from date phrases in Microsoft's text, not from notice metadata. A changed phrase can be a moved rollout, a new milestone or just rewording; "What changed" below shows which.

What the notice says

Microsoft’s text, with source markup removed
Updated May 16, 2025: We have updated the timeline below. Thank you for your patience. Businesses using Google Workspace for email and calendaring can now enable bidirectional syncing with Microsoft Teams through the Admin app in Teams. This improved sync ensures that events created in either platform are seamlessly reflected in both, reducing missed meetings and simplifying scheduling. Previously, calendar forwarding only handled new incoming invites. The updated sync now supports all calendar invites, including incoming, outgoing, existing, and new events. This message is associated with Microsoft 365 Roadmap ID 488093. When this will happen: General Availability (Worldwide): Rollout will begin in late May 2025 (previously early May) and is expected to complete by late June 2025 (previously late May). How this will affect your organization: Administrators must proactively enable this feature; no automatic changes will be made to your environment. This feature is being rolled out gradually. When the rollout is complete, you can sync up to 50,000 users per tenant. If you have previously set up calendar forwarding using this wizard, bidirectional sync is not yet available. Stay updated via your Microsoft admin center Message Center or the Set up calendar syncing between Google Workspace and Microsoft Teams for your small or medium business support article. The feature is rolling out gradually. If it’s not yet available and you haven’t previously set up calendar forwarding, check the Admin app  in Teams periodically. What you need to do to prepare: Refer to the Set up calendar syncing between Google Workspace and Microsoft Teams for your small or medium business help article for setup instructions and additional support.

What changed

Between archive captures, newest first
    • Tags New feature, User impact, Admin impact → Updated message, New feature, User impact, Admin impact

    Updated May 16, 2025: We have updated the timeline below. Thank you for your patience. Businesses using Google Workspace for email and calendaring can now enable bidirectional … 488093. When this will happen: General Availability (Worldwide): Rollout will begin in earlylate May 2025 (previously early May) and is expected to complete by late May 2025.June 2025 (previously late May). How this will affect your organization: Administrators must proactively enable this feature; …

  1. · first version seen

Linked documentation

Microsoft pages the notice links to

The notice links to no Microsoft Learn or Support page that this installation reads.

No related evidence found in this installation's recent collection. This does not establish that no announcement exists.

Not confirmed here

What this page cannot tell you
  • Whether your tenant is affected: this is Microsoft's notice, not a check of your settings.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 26 Oct 11:37 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current