Microsoft Teams chat inside Dynamics 365 Sales

What it does

Puts a Teams chat pane inside the Dynamics 365 app so a seller can start or continue a Teams conversation while looking at a record, and have that chat remembered against the record next time they open it. Dynamics stores the link between the record and the chat; the messages themselves stay in Teams.

Key facts

Turned on from Sales Hub under App Settings > General Settings > Chat and collaborate, or from the Power Platform admin centre at Environments > Settings > Integration > Teams integration settings. Same switch, two front doors.
The master toggle is Turn on Microsoft Teams chats inside Dynamics 365, with a choice of Turn on for all Dynamics 365 apps (including apps created later) or Turn on for selected Dynamics 365 apps.
The setting is environment-wide across customer engagement apps, not per-app-per-team. Turning it on for Sales turns the plumbing on for Customer Service in the same environment.
Out of the box the connected-chat experience covers Account, Contact, Case, Knowledge article and Email. Other tables, including custom ones, have to be added explicitly under Add record types.
Per record type you get two switches: Join chat (lets other people on the record join an existing chat) and Automatically name chats (uses the record title as the default chat name, which the user can then rename).
It is enabled by default in Copilot Service workspace and Customer Service Hub. It is not on by default in Sales Hub, so somebody has to make the decision.
Dynamics stores only the mapping between record ID and chat ID. Chat content is not copied into Dataverse unless a user deliberately puts it there.
Teams and Dynamics permissions are both honoured. A user cannot see a record through the chat pane that their security role would not show them anyway.
Link Dynamics 365 records to Microsoft Teams channels was deprecated with effect from May 2026, and Add chat message to Dynamics 365 record from the Teams side went in January 2026. The channel-based collaboration story is over; chat is what remains.

When to use / skip

Turn it on. It costs nothing, it needs no extra licence, and the alternative is sellers alt-tabbing to Teams and losing the thread. The value is small but the cost is close to zero, which is a rare combination.

Where it does not earn its keep is anywhere the client expects it to be a system of record. It is not. If the requirement is "we need the customer conversation captured against the account for audit or handover", chat integration will disappoint, because the messages live in Teams and only the pointer lives in Dataverse. That conversation is a records-management conversation, not a Sales one, and it usually ends with Purview retention policies rather than a toggle in Sales Hub.

Skip it, or at least delay it, on environments where Teams governance is unsettled — where anyone can create teams and channels, or where the client is mid-migration between tenants. You will end up with orphaned chat links and a support queue.

Configuration decisions

All apps versus selected apps. "All" is convenient and quietly grants the experience to every model-driven app in the environment, current and future; "selected" is the safer default on a shared environment with other workstreams.
Which record types get connected chats beyond the shipped set. Opportunity is the obvious Sales addition and is not there by default — decide early, because sellers will ask.
Whether Automatically name chats is on. Auto-naming makes chats findable in Teams search; it also leaks record titles into Teams, which matters if opportunity names contain client-confidential deal codes.
Whether Join chat is enabled per record type. It is the difference between a chat that a deal team can pick up and a private conversation between two people.
Who owns the switch afterwards. It sits in an environment-level integration setting, so it will be changed by a Power Platform admin, not a Sales admin, unless you write that down.

Gotchas

The environment-wide scope catches people out on multi-app environments. Enabling it "for Sales" is not what actually happens.
Anything built on channel linking is dead. If the client has an existing solution, a Power Automate flow, or a training deck that references connecting a record to a Teams channel, it needs rework, not migration — Microsoft's stated replacement is "use Dynamics 365 in the browser".
Chat links follow the record, not the user's Teams membership. A seller who leaves the deal keeps access to the chat in Teams until somebody removes them there; nothing in Dynamics does that for you.
Guest and external users in the chat see nothing of Dynamics, but they do see the chat name. Auto-naming plus external guests is a small but real disclosure route.
Deleting a Dynamics record does not delete the chat. You get an orphaned Teams conversation with no obvious owner.
The pane needs the user to be signed into Teams in the same tenant. Cross-tenant sellers, contractors on a second identity, and anyone using Teams on a personal account will just see it fail to load rather than get a useful error.

Consultant notes

Demo it against a Contact or Case, not an Opportunity, unless you have already added Opportunity as a record type — the default set does not include it and the demo falls flat.
Tell the client plainly that this is collaboration, not capture. Set that expectation before UAT, or somebody will raise it as a defect.
Check the Teams side before you promise anything: meeting and chat policies, external access, and whether the tenant blocks chat with guests.
Before go-live, confirm the toggle survived any environment copy. Integration settings are environment-scoped and do not always come across the way people assume from a solution import.
If the client asks for chats to be archived into Dataverse, push back and route it to Purview. Building it yourself is a bad trade.

Worth another look once Microsoft says what, if anything, replaces channel-based collaboration.