Power Platform Community Forum Thread Details

We are currently implementing a Copilot Studio voice bot integrated with the Dynamics 365 Contact Center (voice channel via workstream).
Our goal is to create a Case during the bot conversation and correctly link it to the active Omnichannel conversation (msdyn_conversation / msdyn_ocliveworkitem) so that it appears properly in the agent experience.
However, we are running into the following issue:

Within the Copilot Studio bot we are unable to retrieve the correct Conversation ID that exists in Dynamics (msdyn_conversationid).
What we tried:

system.conversationId → returns a Bot Framework conversation ID (not matching Dataverse)
system.activity.id / turn.activity.id → not usable
channelData → does not contain usable Omnichannel context in the voice channel
global.msdyn_* variables → no conversationId exposed
Power Automate triggered from the bot → no reliable conversationId in trigger payload

In all cases, the ID we get does not match the Conversation record visible in Dynamics (msdyn_ocliveworkitem / msdyn_conversation).

Context:

Channel: Voice (through Dynamics 365 Contact Center)
Bot: Copilot Studio (IVR scenario)
Workstream configured and bot correctly attached
Conversation is visible in Dynamics during runtime

Goal:

Retrieve the active Omnichannel Conversation ID during the bot session
Use it when creating a Case (msdyn_conversationid lookup)
Ensure proper linking between Case ↔ Conversation

Question: Is there any supported way to access the current Omnichannel Conversation ID (msdyn_conversationid / live work item ID) from within a Copilot Studio bot running in the voice channel?
Or is this context not exposed to the bot runtime by design?
Are there any recommended patterns to:

either retrieve the correct Conversation ID
or reliably link a Case to the active Conversation during a bot interaction?

Any guidance or confirmed limitations would be highly appreciated.

Thanks from a very desperate Sam :)

Categories:

Bot administration

Calling actions from Copilot Studio

1. Is the Omnichannel Conversation ID (msdyn_conversationid) exposed to Copilot Studio bots in the voice channel?
No, it is not currently exposed.

The Bot Framework’s system.conversationId is a channel-specific (Bot Framework) ID and does not map to the Dynamics 365 Omnichannel msdyn_conversationid.
The Omnichannel context (including msdyn_conversationid and msdyn_ocliveworkitemid) is not passed to the bot runtime in the voice channel, either in channelData or as a global variable.
This is a known limitation and is by design for security and abstraction reasons.

2. Are there any supported ways or workarounds to link a Case to the active Omnichannel Conversation?
Currently, there is no supported, direct way for a Copilot Studio bot to retrieve the Dynamics 365 Omnichannel Conversation ID during a voice session.

The only reliable way to link a Case to a Conversation is to perform the association after the bot session, using backend automation (e.g., a Power Automate flow or plugin triggered by the creation of the Case or the end of the conversation).
Some organizations use a custom integration or plugin in Dynamics 365 that: Monitors new Cases created during a voice session. Matches them to the active msdyn_ocliveworkitem based on timing, agent, or other metadata. Updates the Case with the correct msdyn_conversationid.

3. Recommended Patterns
Post-session association:
Use a Power Automate flow or Dynamics plugin to link the Case to the Conversation after the bot session, based on available metadata (e.g., customer, time, agent).
Custom context passing (unsupported):
Some advanced implementations use custom middleware or APIs to pass the Omnichannel Conversation ID to the bot, but this is not supported out-of-the-box and may break with updates.