agent used in teams session details not shown and power app connector not working for with session

(0) Share

Report

Posted on by AP-24110620-0

I am a new user and do not have much information about Copilot Studio and am facing the following issue

point 1) The agent used in the Teams session details is not shown

When my agent is accessed via MS Teams, the session details and analytics are not visible in the Copilot Studio agent tab. so, not able to see or get any information for the user session and usage patterns

point 2) Power App connector not working with the session

My agent has a Power Apps flow attached, but when the user accesses the agent, the flow fails with a connection issue. The connection for that user is shown as not connected, even though a Power App connection was made with SPN, and its connection shows as connected in the Copilot Studio manage connection tab

Categories:

General

I have the same question (0)

All responses (1)

Answers (0)

Suggested answer

Sam_Fawzi 722 Super User 2025 Season 2 on at

Like (0)

Report
agent used in teams session details not shown and power app connector not working for with session

Hi @AP-24110620-0 ,

Both issues you’re seeing are caused by how Copilot Studio works with Teams and Power Platform authentication. Here’s what each one means and how to fix it.

1) Teams sessions not appearing in Copilot Studio
This happens when the agent is not installed using the official Microsoft Teams channel setup.
To ensure sessions and analytics appear:

Checklist

Go to Publish → Channels → Microsoft Teams inside Copilot Studio

Complete the Teams channel setup

Use “Add to Teams” to install the bot

Make sure users access the agent from the Teams app, not from:

A test link

A preview URL

An outdated bot installation

This behavior is described in the Microsoft Learn article “Configure Copilot Studio for Microsoft Teams.”
If the bot is not installed using the Teams channel, Copilot Studio cannot log session data.

2) Power Apps connector fails when users chat with the agent in Teams
Why this happens
When users interact with the agent in Teams, the bot runs using their identity, not the one you used during testing.
If your Power Automate/Power Apps connectors were created using:

your personal user account

or a service principal that is not configured correctly

the Teams user does not inherit your connection, so the flow fails with “connection not found” or “not connected.”
Fixes
A — Use a Service Principal (recommended)
Microsoft explains this in the Learn document titled:
“Use service principal authentication in Copilot Studio connectors.”
A properly configured SPN lets every Teams user run the flow through one secure application identity.
B — Use a Power Automate flow that runs as a service account
This is documented in “Run a cloud flow using a service account.”
This prevents the connector from trying to authenticate every Teams user individually.
C — Require users to authenticate (not recommended)
Every Teams user must manually approve the connector.
This only works for small-team deployments.

hope this will help you with the issue.

Was this reply helpful? Yes No