finding

Dynamics 365 voice works in a custom model-driven app, despite what the docs say

Microsoft's docs say the voice channel only runs in Copilot Service workspace. I tested it in a custom app and it works.

· Vernon Juelich

Dynamics 365 Contact CenterModel-driven appsVoice

The question

A client already has its own model-driven app, and their reps want to take calls in it rather than switch to Copilot Service workspace. Microsoft’s voice FAQ gives a flat no: voice is supported in Copilot Service workspace only. Another page says multisession doesn’t work in custom apps at all.

What I found

  • The docs disagree with each other. Custom multisession apps became generally available in late 2025. The “workspace only” statements look older than that and were never updated.
  • Microsoft’s own platform code expects custom multisession apps. The behaviour isn’t accidental.
  • In a test custom app built around an insurance demo, all of it worked: presence, the dialer, inbound calls with the caller’s record popping up, outbound calls and transfers.
  • No custom code and no changes to Microsoft components. Turning on the documented multisession setting for the app was enough.
  • I found no public write-up of anyone testing voice this way, so this was the first evidence one way or the other.

The trap

Use the admin switch, not a shortcut. Setting the app’s properties directly got me a phone icon that did nothing and no presence. The app looked right but wasn’t actually connected. The admin setting does more than the obvious property.

Takeaway

When the docs say “not supported”, test it, then get Microsoft’s support position in writing before it goes to production. “It works” and “it’s supported” are different answers, and a customer needs both.

All writing Talk about this