Copilot studio Agents published on Sharepoint

(2) Share

Report

Posted on by JH-15051849-0

Hi everyone,
I'm hoping someone can confirm or correct my understanding of a limitation we're experiencing.
We have a Copilot Studio agent published to a SharePoint site. When users interact with the agent, they are unable to see their previous chat history — unlike the built-in SharePoint AI agents (e.g. SharePoint Agents / Copilot for SharePoint), which do appear to retain and display conversation history.
Is it correct that Copilot Studio agents published to SharePoint do NOT support persistent chat history visible to the end user, while native/built-in SharePoint AI agents do support this out of the box?

Categories:

Copilot Studio skills development

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

11manish 3,052 on at

Like (0)

Report
Copy link

Link copied!

Yes, currently Copilot Studio agents published to SharePoint do not provide end users with native persistent chat history visibility, whereas the

built-in SharePoint/Copilot experiences generally do. If persistent conversation history is required for a Copilot Studio agent, it typically needs to

be implemented through custom storage and retrieval mechanisms rather than relying on an out-of-the-box SharePoint chat history feature.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,526 on at

Like (1)

Report
Copy link

Link copied!

Hi @JH-15051849-0,

Your understanding is correct and confirmed. Copilot Studio agents published to SharePoint do not provide end users with persistent visible chat history. Each session starts fresh from the user's perspective.

This is a channel-level limitation. The SharePoint channel (embedded agent widget on a SharePoint site) doesn't have a persistent conversation UI the way Teams does.

Teams has persistent chats where history is stored in the Teams conversation thread itself, which is why built-in SharePoint/Copilot experiences that run through Teams or M365 Copilot Chat can surface previous messages. The SharePoint embedded widget doesn't have that underlying thread storage.

If you need to give users visible conversation history on the SharePoint channel, you'd need to build a custom solution, typically storing transcripts in a Dataverse or SharePoint list and surfacing them through a custom web part or Power Apps component alongside the agent.

For admin-level transcript access (not end-user visible), Copilot Studio does store conversation transcripts for the last 29 days accessible via the Analytics page, but those aren't shown to users.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

Haque 3,486 on at

Like (0)

Report
Copy link

Link copied!

Hi @JH-15051849-0,

Let's see the key difference:

Native SharePoint AI Agents: These are tightly integrated with SharePoint and Microsoft 365 Copilot infrastructure. They automatically maintain session and conversation history for users, providing a seamless chat experience with visible past interactions.

Copilot Studio Agents Published to SharePoint: These are custom agents deployed via Copilot Studio with broader customization and integration capabilities. However, their chat interface in SharePoint does not currently persist or display previous conversation history to users. Each interaction is treated as a new session.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No