Get Conversation IDs for Copilot Studio Agents
Diesen Beitrag auf Deutsch lesen
Use the correct debug command to retrieve a Conversation ID from custom or declarative agents and give support teams the details they need.
TL;DR
Custom agents show a Conversation ID after users type /debug conversationid in Microsoft 365 Copilot, Teams, or another chat experience. Declarative agents use /debug in Microsoft 365 Copilot and return a debugging card containing the identifier. Users should share the ID, usage location and time, and expected versus actual behaviour.
Original by Chris Garty, on The Custom Engine. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Use the Conversation ID to locate the exact agent session connected to a reported problem, especially when investigating user interactions.
- Admins/CoE: Ask for the identifier, chat surface, timing, and expected versus actual result so support can locate and investigate the relevant conversation.
- Security/Compliance: Treat full conversation access as permission controlled. Makers can view conversations for agents they own, while administrators and support staff need appropriate assigned roles or data access.
Frequently asked questions
How do I retrieve a Conversation ID for a custom Copilot Studio agent?
Type /debug conversationid in the chat; the agent displays the Conversation ID for that specific session.
Which command reveals a Conversation ID for a declarative agent in Microsoft 365 Copilot?
Type /debug in Microsoft 365 Copilot; the declarative agent shows a debugging card that includes the Conversation ID.
What details should I send with a Copilot Studio Conversation ID when requesting support?
Include the Conversation ID, where and when you used the agent, and what you expected compared with what happened.