Forum Discussion
So many different CoPilots - confusing, unproductive
I think we have all learned that CoPilot is a brand, a suite of tools. That probably makes sense from Microsoft perspective, but it is confusing as heck for end users or people trying to roll out CoPilot in a company. Products include:
- Sharepoint agents
- CoPilot desktop app
- Copilot in Office apps -- different copilots for PPT, Word, excel, Outlook
- CoPilot Studio - custom copilots (which by the way turn into "apps"???)
- Teams Copilot
- Researcher and Analyst Agents
- Prompting Coach
- Visual Creator
What is even more frustrating is they don't all work together or in the same environments. I want to call my Sharepoint Agent from my Copilot, nope. I want my Custom Copilot to use Researcher (or vice versa even), not happening (despite Copilot giving me instructions on how it should).
Meanwhile, in Anthropic-land, I setup an MCP service to integrate Claude and my to do app. Not without hiccups, but it works now.
The whole Copilot ecosystem needs to get a lot more consistent and quickly or you are going to continue to loose users.
PS - as i went to post this, I needed to select Tags -- there were 20 Copilot products to choose from!
6 Replies
Sure thing, Antoni! Here's the English version of your post for the Microsoft Tech Community:
Post Title: 🧠 Lack of Shared Memory and Integration Between Copilots – A Real Obstacle to Productivity
Post Content: Hi everyone, I’d like to share some thoughts (and frustrations) from using different versions of Copilot — in Windows, Microsoft 365 apps, and the more conversational chat-based Copilot.
The issue is that each Copilot operates in its own isolated bubble — there’s no shared conversation history, no context synchronization, and I constantly have to manually transfer information between them. In an era of “automated productivity,” this kind of manual overhead feels... ironic.
I’ve submitted an official suggestion via the Microsoft Feedback Portal: 🔗 https://feedbackportal.microsoft.com/feedback/idea/214a550b-9552-f011-95f3-7c1e5299279a
👥 If you’re facing similar issues, feel free to upvote or comment — the more voices, the better the chance it gets prioritized.
To Microsoft: please consider building a bridge between Copilots before this brilliant idea collapses under the weight of fragmentation and data chaos.
Let me know if you'd like to tweak the tone — more formal, more technical, or with a sharper edge. Ready when you are! /// written by Copilot for Copilot ///
I understand that Copilot can feel overwhelming, with its many features scattered across different areas. However, in my opinion, once you take the time to understand the system, it’s well-structured and supports a wide range of users in accomplishing their tasks. As an experienced user familiar with the integrated MCP service, you clearly grasp the scope of AI, its integration, and its possibilities.
Microsoft is pursuing this on a large scale—from typical end users to seasoned developers. While I don’t agree with everything Microsoft does, I believe that there’s something in AI for everyone, depending on their level of experience. That, in my view, is the goal Microsoft is striving toward.
I appreciate your reply. I do think MSFT is doing things no one else is doing -- enterprise administration, data protection, etc., I give them credit for that. I have tried 10 things to get Copilot to work with Sharepoint. They are making it overly complicated.
Which AI tool or entry point within MSFT have you had the most success, productivity, or usage from?I work for a Microsoft Partner, and we began our journey with Bing Chat Enterprise years ago. I have a deep understanding of the technologies that make up the Copilot ecosystem.
At this point, my answer to your question would be: Agents—designed for specific needs and functioning as expected. Yes, there are four levels of agents within Microsoft:
- Agents on SharePoint
- Agents within Business Chat (requires an additional Microsoft 365 Copilot license)
- Copilot Studio Agents
- Full developer-level agents using AI Foundry
Even though I’m not a developer, I can build agents up to level 3 using Copilot Studio. Of course, having a solid understanding of Microsoft ecosystem products is a big advantage.
Speaking for myself: I’m not sure I could set up an MCP server and integrate it with the cloud—but somehow, that knowledge came from your side as well, didn’t it? So at some point you played around with a service and tried your best in configuring it. Within the Microsoft ecosystem: Play around with Copilot Studio and you can get the same results, as Copilot Studio does now support MCP connections.
