Microsoft Teams dialer in Dynamics 365 Sales

What it does

Lets sellers place and take PSTN calls through Teams from inside Dynamics 365 Sales, with the record open next to the call. It uses the customer's existing Teams Phone setup rather than adding a telephony stack of its own.

Key facts

Needs Teams, a Teams Phone licence, PSTN connectivity (calling plan, Operator Connect-style carrier arrangement, or Direct Routing) and a phone number assigned to the user. Dynamics does not provide any of that.
Configured in Sales Hub at App settings > General settings > Teams calls. In Sales Professional there is no menu entry; you reach it by appending pagetype=control&controlName=MscrmControls.TeamsDialerSettings.DialerSettingsHostControl to the org URL.
Settings include Answer incoming calls in Dynamics 365 (on by default), Internal call will ring only in Teams app (on by default), Display missed calls in notification center, Call from views, and Document call attempts (off by default).
Transfer calls and Add people to calls are preview features and carry the supplemental preview terms. The core dial, answer and call-documentation behaviour is GA.
Users need read access to Note (Core Records), the Teams Dialer Admin settings custom entity, and Notification for missed-call alerts. Miss any of those and the dialer looks broken rather than blocked.
Access is granted either to All security roles or to specific roles, and roles chosen here must be associated with the root business unit.
Scoped to Sales Hub by default; you can add other model-driven apps. Canvas apps are not supported.
Custom tables are not supported. The phone icon renders on them anyway and then does nothing, which generates support tickets.
Recording with real-time transcription and insights is optional, gated by its own security-role selection, and is configured through conversation intelligence rather than the dialer settings.
Enabling the Teams dialer stops other telephony providers wired in through Channel Integration Framework from working. It is one or the other.
The Sales Hub Dialer (preview) was deprecated with effect from July 2026, with the Teams dialer named as its replacement.

When to use / skip

If the client already runs Teams Phone, this is the default answer and you should not spend a workshop debating it. It is free of extra Dynamics licensing, it inherits the existing numbering and compliance setup, and it removes the CIF adapter from your risk register.

If the client's telephony is anything else — a contact centre platform, a specialist dialer, an existing CIF integration that works — leave it alone. The Teams dialer is a seller's phone, not a contact centre. There is no queueing, no supervisor barge, no wallboard, and the preview status on transfer means you cannot promise call-handling behaviour that a service desk would consider basic.

The awkward middle case is the client migrating to Teams Phone during the Dynamics project. Do not couple the two. Deliver Dynamics with telephony out of scope, then switch the dialer on afterwards as a small change.

Configuration decisions

Whether inbound calls land in Dynamics at all, or only in the Teams client. Answer incoming calls in Dynamics 365 defaults to on and is the single most contentious setting with sellers who already live in Teams.
All roles versus named roles, and whether those roles sit at the root business unit — a nominally correct role in a child BU will not be selectable.
Whether Document call attempts goes on. Off by default; turning it on gives managers a real activity trail and gives sellers something to complain about. Decide it as a policy question, not a config question.
Whether recording and transcription are in scope, and if so which roles can hear recordings. This is a works-council and consent question in the UK and EU before it is a technical one.
Which apps the dialer appears in. Adding a custom model-driven app requires removing and re-adding it in the settings; plan the sequence.
Whether any existing CIF provider stays. There is no coexistence.

Gotchas

Teams Phone licensing is the usual project killer. Plenty of tenants have Teams without Teams Phone, and nobody discovers it until the first demo dials and fails.
Config changes need a page refresh before they take effect. Testers will report the setting "didn't save" when it did.
The phone icon on custom tables is a trap: it appears, it is not supported, it does nothing useful. Expect to explain this more than once.
Turning the dialer on silently breaks whatever CIF-based softphone was there. Check for one before you flip the switch, especially on environments shared with Customer Service.
Sales Professional has no UI route to the settings. If nobody on the team knows the control URL, the feature looks unavailable.
Missing read privilege on Notification means missed calls simply never appear, with no error anywhere.

Consultant notes

Get the Teams Phone position in writing at discovery. Ask for a screenshot of an assigned number, not a verbal yes.
Demo with the record open beside the call and the call documented afterwards. The value is the note against the record, not the dialling.
Push back hard on contact-centre requirements arriving under the heading "we just want click to dial". That is a Contact Center conversation.
If recording is wanted, sequence it: telephony first, conversation intelligence second, consent and retention third. Doing them together produces a mess nobody can test.
Before go-live, check role scoping against the root business unit and test one seller in each business unit — this is where it usually falls over.

Worth another look when transfer and add-people leave preview, or if the client's telephony estate changes.