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 09:15 UTC Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Teams: Live chat will be renamed to Customer Connect

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

Rollout

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 6 May 2026 late April 2026 → mid-May 2026

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 6, 2026: We have updated the timeline. Thank you for your patience.  Introduction Live chat in Microsoft Teams enables small and medium businesses to connect with customers through a chat widget embedded on their websites. Website visitors can chat directly with business employees, who receive and manage these conversations in Teams. Transcripts from live chats are stored in a central team and channel, which organizations can use for ticket management and follow‑up. To better align the feature name with how customers use it, Microsoft will rename Live chat to Customer Connect. This is a name change only; there are no functional or behavioral changes. When this will happen General Availability (Worldwide): We will begin rolling out this change in mid-May 2026 (previously late April) and expect to complete the rollout by the end of May 2026. How this affects your organization Who is affected Microsoft 365 tenants that use Live chat in Microsoft Teams Teams administrators who manage Live chat settings Users who support customers through Live chat conversations in Teams What will happen Live chat will be renamed to Customer Connect across:Teams admin settings In‑product references Microsoft documentation There will be no changes to functionality, configuration, or data handling. If your organization already uses Live chat:Existing teams and channels created for Live chat will not be renamed. If your organization begins using this capability after the name change:The team and channel used to manage live chats will be named Customer Connect. The feature will remain enabled and managed the same way as before. Learn more: Set up and manage live chat | Microsoft Teams | Microsoft Learn What you can do to prepare No action is required. You may consider updating internal documentation or informing helpdesk and support staff of the new Customer Connect name to reduce potential confusion. Compliance considerations No compliance considerations identified. Review as appropriate for your organization.

What changed

Between archive captures, newest first
    • Tags Feature update, User impact, Admin impact → Updated message, Feature update, User impact, Admin impact

    Updated May 6, 2026: We have updated the timeline. Thank you for your patience.  Introduction Live chat in Microsoft Teams enables small and medium businesses to … happen General Availability (Worldwide): We will begin rolling out this change in late April 2026  mid-May 2026 (previously late April) and expect to complete the rollout by the end of May 2026. …

  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.

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 09:15 UTC · 272 of 272 readable · 270 fully read · documentation 469/469 current