Answered

Is it possible to add or delete knowledge in Copilot Studio with Power Automate

(0) Share

Report

Posted on by KW-18110402-0

Hi Community

I have to know the feasibility of the following, as I want to fully automate the update of knowledge base from SharePoint to Copilot Studio (with Dataverse indexing)

add/delete knowledge with Dataverse indexing from SharePoint with Power Automate
click the newly added knowledge in the generative answer node with Power Automate

Categories:

Bot administration

General topics

I have the same question (0)

All responses (2)

Answers (1)

Sort by

Verified answer

MS.Ragavendar 7,431 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!

@KW-18110402-0,

I always upload the knowledge and use that as Knowledge source never tried the way you are showing.

I could find some article from Matthew Devaney how-to-add or remove copilot-studio-knowledge-files-using-power-automate check its working for you.

✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Was this reply helpful? Yes No
Suggested answer

Sayali-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hello @KW-18110402-0,

Fully automating the lifecycle of knowledge ingestion from SharePoint into Copilot Studio—such as adding or deleting knowledge with Dataverse indexing or dynamically selecting newly added knowledge within a Generative Answer node—is currently not feasible through Power Automate or any exposed APIs. While SharePoint‑based knowledge sources can be manually added within Copilot Studio, the underlying operations involved—like registering the knowledge configuration, setting up the Dataverse indexing pipeline, and binding the source to specific topic nodes—are handled within Copilot’s internal runtime metadata layer and are not accessible via Dataverse tables or supported connectors. As a result, actions such as programmatically triggering re‑indexing, automating the “Add knowledge” step, or updating the knowledge source selection within generative nodes remain design‑time operations tied to solution deployment rather than runtime logic. For production scenarios that require dynamic content updates from SharePoint, the recommended approach is to shift away from ingestion‑based static knowledge memory and instead use Power Automate to retrieve relevant files or content at runtime via agent actions, pass that information as structured context into the prompt, and allow the agent to generate responses based on live data—eliminating the need for manual re‑ingestion or topic configuration changes while ensuring responses reflect the most up‑to‑date SharePoint content.

Was this reply helpful? Yes No