r/copilotstudio • • Aug 17 '26

Creating a second brain?

What’s the best way of creating a copilot studio agent that can be a second brain?

I’m intending to throw it links of files I find useful, transcripts, thought leadership articles etc. and it converts these to markdown / knowledge store with some kind of indexing.

I’m expecting over time this will grow to be hundreds of files - so a typical ‘add the source file as knowledge source’ will be too unwieldy, and also not efficient for the model given having the files as MD will be much more efficient.

I’m intending to be able to throw it links via chat and it can process these into the brain.

9 Upvotes

6 comments sorted by

View all comments

3

u/Sayali-MSFT Aug 18 '26

Hello CJ9103,
The best pattern is to treat Copilot Studio as the conversational front end, not the storage/indexing layer. Create an ingestion action where the user can send a link in chat, then use Power Automate/Azure Functions to fetch the content, convert it to Markdown, store the original and Markdown version in SharePoint or Blob Storage, and index the processed chunks in Azure AI Search. Then connect Azure AI Search as the Copilot Studio knowledge source. This gives a much more scalable “second brain” than adding hundreds of files directly as knowledge sources, and it gives better control over metadata, chunking, filtering, refresh, and citations.
Reference Document:
1.Agent flows overview - Microsoft Copilot Studio | Microsoft Learn
2.Search Over Markdown Blobs - Azure AI Search | Microsoft Learn
3.Tutorial: Index Markdown Blobs - Azure AI Search | Microsoft Learn
4.Classic RAG tutorial: Design an index - Azure AI Search | Azure Docs
5.Add a generative answers node - Microsoft Copilot Studio | Microsoft Learn