REDMOND, 11 AUG 2026 — Microsoft has stopped new customers setting up Live chat in Teams, and will switch it off on 5 October. The feature launched in March 2025. It gets about eighteen months of life and small businesses get two months' notice.
Live chat is the widget a company embeds on its website so visitors can talk to someone. In this case those conversations were routed into Teams, where a support team of up to 25 people picked them up.
The dates, and what happens on each
Microsoft's own documentation is unambiguous, which is more than can be said for the notice period.
<script> tag with id="chatbot" and delete it.Existing data is not deleted. Teams channels and the associated list data remain subject to your tenant's normal retention policies, and Microsoft advises exporting anything you want to keep independently.
Who this lands on
Live chat was available only on the small-business plans: Microsoft 365 Business Basic, Business Standard and Business Premium. Enterprise tenants never had it.
This change lands squarely on the group with the least capacity to absorb it: companies without a dedicated IT function, who used a feature because it was already there, and who now have eight weeks to replace a live customer-facing channel.
The 25-user cap confirms this was built for a small support desk, not a contact centre.
Where Microsoft points next
Two places: Dynamics 365 Contact Center with Live Chat, and Copilot Studio's contact centre AI capabilities.
Both are substantial products, but neither is a like-for-like replacement. Live chat in Teams was a bundled feature of a business subscription; Dynamics 365 Contact Center is a separate line of business with its own licensing. Microsoft's documentation does not describe the commercial difference, and a small business reading the retirement notice will not learn from it what the replacement costs.
That is the substance of the complaint, and it is not really about this feature. A capability that arrived inside a bundle is being retired toward a product that is sold separately. Whether or not that is the intent, it is the shape.
The data answer is thinner than it reads
Microsoft's retirement notice says previously created customer data will not be deleted, and that existing Teams channels and the associated list data remain available "according to the applicable Microsoft 365 data retention and lifecycle policies in your tenant".
Read that second clause carefully. It is not a commitment to keep anything. It is a statement that the normal rules continue to apply — and in a small tenant that has never had anyone configure retention, the normal rules are whatever the defaults happen to be, which almost nobody running a Business Standard subscription has looked at.
Remember, these are customer support conversations. They contain complaints, order details, personal information volunteered by members of the public, and occasionally the only record of what a business promised someone. Under PDPA or GDPR that is personal data the business is accountable for, and a retirement notice does not transfer that obligation to Microsoft.
So the export advice in the notice is not housekeeping. Deciding what to keep, for how long, and on what lawful basis is a task with a deadline attached to it now, and the deadline is the same 5 October.
The pattern is the story
Live chat is not alone. Microsoft retired Teams live events in February 2026 in favour of a newer events experience, and Together mode has also gone.
Features that ship inside a large suite carry an implicit promise of permanence that standalone software does not. Nobody signs a contract for Live chat; it simply appears in the admin app, and a business builds a customer-facing process on it because it is there and it is included.
The rational response is not to avoid bundled features, which would be wasteful. It is to know which of your operational processes depend on one, and to treat the ones that touch customers directly as carrying a shorter expected life than the suite around them.
What to do if you are running it
The mechanical part is small: remove the script tag before 5 October, or the widget will simply vanish from your site on Microsoft's schedule rather than yours. Silent disappearance is the worse outcome, because the page keeps working and nobody notices the channel is gone.
The real work is deciding on a replacement, and eight weeks is only enough time if you start now. Worth asking before reaching for the suggested upgrade: how many conversations actually arrived through that widget, and would an email address and a published response time serve the same customers at no cost.
Tell the support team too. Microsoft's own checklist says so, and a queue that quietly stops producing work is not something a busy team will flag quickly.
What to watch
Whether anything replaces it inside the Business plans. If the answer is nothing, then a capability has moved from bundled to separately licensed, which is a pricing change communicated as a retirement.
How the next one is announced. Two months for a customer-facing channel is short, and the precedent set here applies to every other convenience feature sitting in the same admin app.
