You’re offline. This is a read only version of the page.
I have a Copilot Studio virtual agent published to Microsoft Teams. The bot is working for multiple users in Teams (they can access it and complete conversations), however Copilot Studio Analytics is only capturing my own conversations. Other users’ interactions are not appearing in analytics, even after repeated testing.
This prevents us from validating adoption and performance across the wider pilot group and creates risk moving toward production because telemetry appears incomplete.
All relevant Copilot and environment options are enabled, including Enhanced transcripts.
The bot is correctly published to Teams and is usable.
Analytics is not fully blank — it does record my interactions — but not other users’.
When I interact with the bot in Teams, those sessions appear in Analytics.
When other users interact with the same Teams bot/app, their sessions do not appear in Analytics.
Validated functionality for other users: users can find the bot and complete conversations in Teams.
Environment / version alignment: confirmed the agent/environment I’m viewing in Copilot Studio is the one published to Teams.
Telemetry settings enabled: confirmed environment options and Enhanced transcripts are switched on.
Re-published after configuration checks to rule out stale publishing artifacts.
Investigated activity logging / telemetry enablement path, including the known limitation that Protected mode publishing can prevent enabling logging later.
Checked Teams policy/governance areas that could restrict logging, and noted cases where configuration changes could not be saved (Save disabled).
What typically causes analytics to only record the publisher/owner’s conversations but not other users?
For example: role-based access, licensing, Teams policy restrictions, tenant-level telemetry settings, data loss prevention policies, user consent/privacy settings, or differences between using the bot in a personal chat vs a channel context
Are there known differences in analytics capture between:
personal chat with the bot vs channel installationusers in different Teams policies / security groups
If the app was published in Protected mode, can this result in telemetry being effectively limited to the owner/tester account? If so, what is the supported recovery path?
What prerequisites must be true for other users’ transcripts/analytics to be recorded (exact roles, environment security roles, tenant settings, and any required consent/telemetry toggles)?
We are in testing/UAT moving toward production, and need reliable multi-user analytics before sign-off.
If you want to maximise the quality of responses, include these specifics in your post (people will ask anyway, and it speeds resolution):
Are the “other users” internal licensed users, or guests/external?
Are they chatting with the bot directly, or using it inside a Teams channel?
Are they on the same tenant, and do they have the same Teams app permission policies?
What is the environment type (Default/Dev/UAT) and is it tied to any DLP policy?
Share
Report
All responses (
Answers (
666
