Building and customizing solutions using Microsoft 365 Copilot APIs and tools
Copilot - Changes has not made this tool completely useless and cost me time
Microsoft recently migrated Projects to Notebooks while introducing Cowork as the new way of working in Copilot. As a paying Microsoft 365 customer, this change was not clearly communicated, and it has created significant disruption to my business workflow.
I had built months of project-specific knowledge, instructions, decisions, and context into Projects. Those Projects have now become Notebooks, but that historical context does not appear to flow into Cowork projects or tasks. The result is that I am having to rebuild workflows and retrain Copilot from scratch.
My concern is not the interface change itself. My concern is the loss of continuity and business value. Many of us invest significant time building operational knowledge into these tools and expect that investment to be protected.
Can Microsoft explain:
- Whether integration between Notebooks and Cowork is planned?
- Whether the current loss of continuity is temporary or the intended long-term design?
- What protections Microsoft will put in place to ensure future changes do not disrupt business-critical workflows?
At what point can customers trust that the time invested in building AI-assisted workflows will not be made obsolete by product changes beyond our control?