You build a Copilot agent in Copilot Studio, test it, and later cannot find the conversation transcript in the analytics or topic history. The transcript is missing from the Copilot Studio portal even though the agent processed the conversation correctly. This problem usually occurs because the transcript retention settings are misconfigured or because the conversation was routed to a fallback topic that does not log content. This article explains the root causes of missing transcripts and provides step-by-step fixes to restore logging for your Copilot agents.
Key Takeaways: Recovering Missing Copilot Studio Agent Transcripts
- Copilot Studio > Settings > General > Data retention: Controls how long transcripts are stored; default is 30 days.
- Copilot Studio > Topics > System topics > Fallback: Disables logging for unrecognized user inputs unless you enable content logging per topic.
- Copilot Studio > Analytics > Customer satisfaction > Transcripts: Location where transcripts appear only after the agent completes a session.
Why Copilot Studio Agent Conversation Transcripts Go Missing
The Copilot Studio platform stores conversation transcripts in the Azure Bot Service channel behind the scenes. When a user interacts with a Copilot agent, the conversation is processed by the bot runtime and then saved to a storage container tied to your Copilot Studio environment. Transcripts are not written to the analytics section until the conversation ends naturally or after a timeout period of 30 minutes of inactivity.
Three root causes account for nearly all missing transcript reports:
Data Retention Settings Delete Transcripts Too Early
By default, Copilot Studio retains transcripts for 30 days. If you check the analytics section after this window, the transcripts have been purged automatically. This setting is global and applies to all agents in the environment.
Fallback Topic Logging Is Disabled
When a user asks something the agent does not recognize, the system routes the conversation to the Fallback topic. This topic does not log the full transcript by default. Only the fact that a fallback occurred is recorded in analytics, not the user’s actual text.
Conversation Never Completes
If the user closes the chat window or navigates away before the agent finishes processing, the transcript may not finalize. Copilot Studio only writes a complete transcript after the session ends cleanly. Partial or abandoned sessions are discarded.
Steps to Restore Missing Conversation Transcripts
Follow these steps in order. Start with the retention check because it is the fastest to verify.
- Check data retention period
Sign in to Copilot Studio. Navigate to Settings > General > Data retention. Confirm the retention period is set to at least 30 days or higher. If you need longer retention, change the value to 90 or 180 days. Click Save. - Enable content logging for the Fallback topic
Go to Topics > System topics. Find the Fallback topic. Open it. In the topic properties pane, locate the Logging section. Set Log full transcript to On. Click Save. This ensures unrecognized inputs are recorded. - Enable transcript logging for all custom topics
Repeat the same logging setting for every custom topic you created. Open each topic, go to Properties > Logging, and set Log full transcript to On. This step is optional if you only care about fallback conversations, but recommended for complete auditing. - Verify the analytics section
Go to Analytics > Customer satisfaction. Scroll down to the Transcripts section. If transcripts still do not appear, wait 15 minutes after a new test conversation. Transcripts are not written in real time. They appear after a short processing delay. - Check the Azure Bot Service storage container
If transcripts are still missing, open the Azure portal. Navigate to your Copilot Studio resource group. Locate the Storage account associated with your bot. Open Containers > transcript-store. If you see JSON files here but not in Copilot Studio, the issue is a sync delay or a permission problem. Contact your Microsoft 365 tenant administrator to verify the Bot Service role assignment for your user account.
If Copilot Studio Still Has Issues After the Main Fix
Transcripts Appear Empty or Show Only System Messages
This happens when the agent uses a Redirect action to send the conversation to another topic without logging. Review each Redirect action in your topics. Add a Log step before the Redirect to capture the user input. Alternatively, restructure the topic to end with a Show message node instead of a Redirect so the transcript finalizes before the handoff.
Transcripts Show Only the First Message
This indicates the conversation timed out after 30 minutes of inactivity. Copilot Studio considers the session abandoned and writes only the initial message. To avoid this, configure the Conversation timeout setting in Settings > General > Conversation timeout. Increase the value from the default 30 minutes to 60 minutes if your users have long pauses between messages.
Transcripts Missing for Specific Users or Channels
If transcripts are available for some users but not others, the issue is often a channel-specific configuration. For example, the Microsoft Teams channel may strip transcript data if the Allow transcript download setting is disabled in the Teams admin center. Verify that the channel configuration in Copilot Studio allows full transcript logging. Go to Settings > Channels > Teams and confirm Enable transcript logging is checked.
Transcript Retention Settings: Default vs Extended
| Item | Default (30 days) | Extended (90 or 180 days) |
|---|---|---|
| Storage cost | No additional Azure storage cost | May incur extra storage fees in your Azure subscription |
| Compliance coverage | Suitable for short-term audits | Suitable for regulatory compliance requirements |
| Fallback topic logging | Disabled by default | Must be enabled manually regardless of retention period |
The table above shows that extending retention alone does not fix missing transcripts. You must also enable logging per topic. The two settings work together: retention determines how long logs survive, and topic-level logging determines whether logs are created at all.
Now you can recover missing Copilot Studio agent conversation transcripts by adjusting retention settings, enabling logging on the Fallback topic, and verifying the Azure storage container. Start by checking the data retention period because it is the fastest fix. For ongoing monitoring, set up a weekly review of the Analytics > Transcripts section to catch logging gaps early. If you manage multiple agents, create a topic template with logging enabled to avoid reconfiguring each new agent manually.