[M365 Copilot Enterprise] Replicating Claude "Projects" or Gemini "Gems" for persistent context?
I am restricted to M365 Copilot (Enterprise) due to data sensitivity, so external models are not an option. My primary struggle is the lack of a persistent, dedicated workspace.
In Claude (Projects) or Gemini (Gems), you can define a static, continuously updated set of system instructions and core documents. The model treats this as an isolated foundational truth, allowing it to provide complex logical advice across multiple files while still pulling in fresh web or external data when prompted.
In M365 Copilot, the RAG defaults to indiscriminately scraping recent emails, Teams chats, and random SharePoint files. This dilutes the context completely when trying to do focused, multi-document analytical work.
How are you bypassing this limitation to create a persistent context workspace within the M365 ecosystem?
- Can specific SharePoint folders or hubs be rigidly isolated and prioritized to act as a "Project" base?
- Are you using a specific "anchor document" architecture that Copilot reliably treats as a continuously updating knowledge base / system prompt? If yes, do you keep manually extending it or is there any way to make that automated?
- Is there a way to build a Copilot Studio agent that maintains this strict grounding but still has web-search capabilities for real-time data?
Looking for production-tested architectural workarounds, not basic prompt engineering tips.