Almanac
Microsoft/d365salesDynamics 365

Consultant-focused KB for Microsoft Dynamics 365 Sales: implementation notes, gotchas, and configuration decisions beyond the official docs — across pipeline management, opportunities, forecasting, sequences, sales accelerator, Copilot, integrations, administration, and licensing.

d365sales/11-decision-guides/feature-native-teams-outlook-or-custom-build.md
feature-native-teams-outlook-or-custom-build.mdv1 · history
CurrentApplies to AllUpdated 6 days agoSource Microsoft Learn ↗

What it does

Dynamics 365 Sales ships first-party integration with Teams and Outlook: chats attached to records, the Dynamics 365 App for Outlook for tracking email and meetings, and a Teams dialer. The recurring question on projects is whether to take what Microsoft gives you or build something with the Graph API and a custom PCF control. This doc is about when building is defensible, which is less often than clients think — and which native pieces Microsoft is currently retiring underneath you.

Key facts

  • Teams chat in Dynamics is controlled by the admin toggle Turn on Microsoft Teams chats inside Dynamics 365, with a scope choice of all Dynamics 365 apps (including future ones) or a selected list.
  • Connected chat works out of the box for case, account, contact, knowledge article and email records. Admins can add custom record types, each with its own Join chat and Automatically name chats toggles.
  • Settings apply organisation-wide across customer engagement apps, not per app. Enabling for Sales Hub touches the whole estate.
  • Nothing from Teams is stored in Dynamics except the mapping between record ID and connected chat ID. Traffic is secured with TLS, and Dynamics record permissions are honoured — a record shared into a chat only opens for someone who could already see it.
  • Configuration lives in Sales Hub under App Settings > Chat and collaborate, or in the Power Platform admin centre under Environments > Settings > Integration > Teams integration settings.
  • Linking Dynamics 365 records to Microsoft Teams channels is deprecated effective May 2026. The stated replacement is using Dynamics 365 in the browser.
  • Adding a chat message to a Dynamics 365 record from within Teams was removed in January 2026.
  • The Sales Hub Dialer (preview) is deprecated effective July 2026, with the Microsoft Teams dialer as the replacement.
  • Dynamics 365 App for Outlook runs on Outlook desktop, web and mobile, tracks email and meetings against records, syncs contacts, and inserts email templates, knowledge articles and sales literature.
  • Multiplexing through Outlook does not reduce the number of Dynamics 365 licences required. A user touching Dynamics data via Outlook still needs a licence.

When to use / skip

Take the native integration. That is the recommendation, and on most engagements it should not be a long conversation. Teams chat and the Outlook app cover the two things sellers actually do — talk about a deal, and track the emails about it — and they cost nothing to switch on. A custom build starts at weeks of effort and inherits permanent maintenance of Graph permissions, admin consent, token handling and whatever Microsoft changes next quarter.

Build custom only when you can name a requirement the native integration structurally cannot meet. The honest ones: a compliance rule requiring every message about a regulated deal to be retained in Dataverse rather than left in Teams; writing deal context into a channel from a back-end process with no user present; or an embedded experience in a bespoke app where the first-party controls are unavailable. "We want it to look different" is not, and it does not survive the first support ticket.

Be careful about building on the parts that are being withdrawn. Record-to-channel linking is deprecated from May 2026 and the in-Teams "add chat message to record" action has already gone. If your design brief is "recreate record-to-channel linking because Microsoft is removing it", stop and ask what the underlying requirement was. It is usually document collaboration, which SharePoint integration handles, or deal-room context, which a connected chat covers well enough.

The Outlook side is more clear-cut. The App for Outlook is the supported path across desktop, web and mobile, and rebuilding email tracking against Graph is a lot of work to arrive somewhere worse. Custom work earns its place there only as a thin add-in for one specific action, sitting alongside the native app rather than replacing it.

Configuration decisions

  • Whether Teams chat is enabled for all Dynamics 365 apps or a selected list, remembering the setting is organisation-wide and affects Customer Service too.
  • Which record types get connected chat beyond the out-of-the-box set, and whether opportunity and lead are added for sales use.
  • Whether Automatically name chats is on, and what the naming convention means for managers scanning a chat list.
  • Whether the Teams dialer is adopted now, given the Sales Hub Dialer preview is going in July 2026.
  • How email tracking is scoped in the Outlook app, and what that implies for storage and for what ends up visible to colleagues.
  • Whether any custom collaboration surface is genuinely required, and if so, whether it sits alongside the native integration rather than replacing it.

Gotchas

  • Teams integration settings are tenant-wide across customer engagement apps. Turning it on for a Sales pilot switches it on for everyone in Customer Service too, and nobody tells them.
  • Record-to-channel linking disappears in May 2026. Any design or training material referencing it needs rewriting now, not later.
  • Connected chats live in Teams, not Dynamics. If retention or eDiscovery is a requirement, that is a Purview conversation — Dynamics holds only the chat ID mapping.
  • Outlook multiplexing does not save licences. Someone always tries this, usually for a back-office team, and it is a licensing compliance problem waiting to be found.
  • Custom Graph-based builds need admin consent for delegated or application permissions. That approval routinely takes longer than the build, and it lands with a security team who were not in the project.

Consultant notes

  • Show the client the deprecation list at design time. It reframes the conversation from "what can we build" to "what will still exist", which is the more useful question.
  • Demo connected chat on an opportunity with two people in the room. It sells itself in about thirty seconds, and it removes most of the appetite for a custom build.
  • Push back hard on rebuilding native integration for cosmetic reasons. Ask what the actual failure mode is; nine times in ten it is training, not the product.
  • Before go-live, confirm the Teams integration scope with whoever owns Customer Service, and confirm the Outlook app is deployed to the right mailboxes rather than assumed.
  • If you do build something custom, keep it to one narrow action and document the Graph permissions it holds. The next consultant will need that.

Worth another look after the May 2026 Teams channel linking deprecation lands, or when the Teams dialer replaces the preview one.

Was this accurate?
Related
Microsoft Teams chat inside Dynamics 365 Sales08-integrationsSales in Microsoft 365 Copilot (formerly Copilot for Sales)08-integrationsMicrosoft Teams dialer in Dynamics 365 Sales08-integrationsDynamics 365 App for Outlook08-integrationsEmail engagement03-leads-and-activitiesDynamics 365 Sales licence tiers10-licensing