Forum Discussion
Copilot Call Delegation Does Not Work with Compliance Recording Applications
Hello,
I was able to isolate an issue related to Copilot Call Delegation and compliance recording applications.
We have successfully configured Copilot Call Delegation and confirmed that it functions as expected in a standard Teams Phone environment. However, when a compliance recording application is assigned to the user, Copilot Call Delegation no longer works correctly. The Copilot delegate does not join or participate in the call as expected.
Has anyone else encountered this behavior? Is there a known limitation, compatibility issue, or recommended configuration when using Copilot Call Delegation alongside Teams compliance recording solutions?
Any guidance from the Microsoft product team would be greatly appreciated.
Thank you.
1 Reply
You isolated Copilot Call Delegation as working until a compliance-recording policy assigns a recorder, after which the voice delegate no longer joins. Microsoft currently delivers Call Delegation through Frontier early access, and its published known-issues list does not document compatibility with compliance-recording applications. Compliance recording uses certified third-party bots automatically invited by policy. Two call bots in the same screening path is therefore a plausible interoperability gap, not a guaranteed configuration. Confirm Teams is current, supported, and set to English. In an approved test account only, compare calls with and without the recording policy and note whether strict recording is enabled; do not weaken production compliance. Capture UTC time, caller, callee, call ID, policy assignments, and recorder logs. Report the call in Teams under Copilot Call Delegation and open a joint case with Microsoft and the certified recording vendor. There is no documented admin switch for this combination.
