Microsoft Teams integration patterns with Dynamics 365

Microsoft Teams is increasingly where business work happens — meetings, chat, file collaboration, decisions. Dynamics 365 has invested heavily in Teams integration over the past several releases so the work that touches CRM and ERP can stay in the Teams flow. The integration patterns are varied; choosing the right one per use case matters.

Pattern 1: Share-to-Teams of CRM records. From any Dynamics 365 record (account, opportunity, case, customer in Business Central, work order in Field Service), the user can share to a Teams chat or channel. The record renders in Teams as an adaptive card with key fields and a deep link back to Dynamics 365. The most common pattern; works out of the box.

Pattern 2: Embedded model-driven apps in Teams. Any Dynamics 365 model-driven app (Sales, Customer Service, Field Service) can be added as a Teams app, where the entire CRM experience appears as a tab inside a Teams channel or in the user's left navigation. Sellers can browse opportunities, update accounts, and respond to cases without leaving Teams.

Pattern 3: Linked Teams collaboration on records. A Dynamics 365 record (typically Account or Opportunity) can have a linked Teams team or channel. Conversations in the linked channel surface on the record's timeline; documents in the channel's file library link automatically to the record. Used for deal teams where many people collaborate on one opportunity.

Pattern 4: Meetings with CRM context. Adding a CRM contact as a meeting participant pulls in meeting insights: who they are, recent activity, open opportunities, open cases. Real-time during the meeting, Copilot summarises decisions; post-meeting, the recording can be saved to the related opportunity or account automatically.

Pattern 5: Adaptive card actions from CRM. Power Automate flows triggered by Dataverse can post adaptive cards to Teams chats or channels, with buttons for users to take action — approve a discount, accept a deal handoff, decline a service request. The action posts back to Dataverse or runs a follow-up flow. Used heavily for approvals and notifications.

Pattern 6: Business Central in Teams. Business Central has its own Teams app for SMB scenarios — share a customer/vendor/item card, look up records from Teams compose, run a quick action. Useful for organisations that live primarily in Teams.

Pattern 7: Copilot agents in Teams. Copilot Studio agents with Dynamics 365 knowledge sources and actions publish to Teams as chat-style agents. Users converse with the agent — "what's the status of opportunity X?", "open a case for customer Y" — and the agent reads/writes Dynamics 365 via the configured actions.

Pattern 8: Teams calls integrated to CRM. Dynamics 365 Omnichannel for Customer Service handles voice via Azure Communication Services; Teams calls (consumer-grade calls between Teams users and Dynamics 365 agents) integrate to surface CRM context, record the call, and post a summary.

Choosing.

• Casual sharing of records — built-in share-to-Teams.
• Heavy CRM use in Teams — model-driven app added as Teams tab.
• Deal-team or case-team collaboration — linked Teams team.
• Meetings with customers in CRM — meeting integration.
• Approval workflow notifications — adaptive card actions via Power Automate.
• Conversational interaction with CRM — Copilot Studio agent.

Governance. Tenant-wide policies (Teams app permission policies, DLP) govern what Dynamics 365 components can run in Teams.

Operational reality. The Teams story for Dynamics 365 has been evolving across releases; document the integration choices and revisit them at each wave for new capabilities and deprecations.