Teams Meeting Integration

Status: Public Preview — behaviour may change.

What it does

Lets representatives create and join Microsoft Teams meetings from Dynamics 365 and see the linked record in a side panel during the call, with notes and tasks syncing back to the record. The aim is to stop people alt-tabbing between Teams and the case while a customer is talking.

Key facts

Admins turn it on in the Copilot Service admin center or Contact Center admin center under Support experience > Collaboration, by selecting Manage on meeting integration using Teams and setting Show Dynamics 365 data in Teams meetings to Yes.
Add and join meetings is a required setting, configured in Power Platform admin center feature settings. Sync calendars is optional and puts meetings on Outlook and Teams calendars.
The record side panel supports only Contact, Opportunity, Lead, Account and Case. Case applies to Customer Service only.
You shape the panel through the In Context Form of the table. Supported changes: add or remove header and Key Details fields, change labels, set required or read-only.
Unsupported: rearranging or disabling tabs, adding custom tabs or sections beyond Key Details, Contacts, Notes, Tasks, Collaboration and Recent Opportunities, adding web resources or subgrids, and changing layout or some field properties.
Linking a Regarding record when creating the meeting adds the Dynamics 365 app to it automatically.
The Record and get insights setting only appears in Sales apps with a premium licence.
It's a preview, with the usual preview terms: changes expected, and no Microsoft support commitment.

When to use / skip

Use it where representatives run scheduled video calls with customers about a case or account, such as onboarding sessions, complex troubleshooting or account reviews, and are tired of copying notes across by hand.

Skip it for the inbound voice and chat channels in omnichannel; this is about calendar meetings, not conversations in the workspace. Skip it in production if a preview with no support commitment is a problem for your change board.

Configuration decisions

Whether to turn on calendar sync. Optional, but without it meetings created in Dynamics won't appear on representatives' calendars, which people notice immediately.
Side panel content. Decide which case and contact fields matter mid-call. Short beats complete; the panel is read while someone is talking.
Read-only fields. By default every field in the In Context Form is editable from the panel. Set read-only on anything that shouldn't be changed live.
Mailbox configuration. For Teams calendar visibility, mailboxes need server-side synchronisation for appointments, contacts and tasks, then approval and a successful test and enable.

Gotchas

Meetings created in Outlook aren't linked to a record automatically. Representatives need the Dynamics 365 app for Outlook to set the Regarding record, or the panel is empty.
If nobody linked a record, add the Dynamics 365 app to the meeting before it starts; adding it mid-call works but is clumsier.
The mailbox needs to show Success after test and enable before Teams appointments appear. Teams refresh lag looks like a fault; refresh the mailbox record first.
Side panel customisation is limited to fields. Requests for custom tabs or subgrids will arrive and can't be met in this version.

Consultant notes

Show the panel to representatives in the first workshop. Most of the scoping questions ("can we add the case timeline?") answer themselves once they see what the supported customisations are.
Get the Regarding habit into the process, not the training slides. A linked record is what makes the whole thing work, and it's the thing people skip when rushed.
Mailbox sync is usually owned by a different team from the one running Customer Service. Raise it as a dependency in week one.
Treat it as a pilot with a small group. Preview terms mean you want a fallback of notes in Teams and manual copy until the behaviour settles.

Preview feature — worth revisiting when it reaches general availability.