Microsoft 365 Copilot enables deep work but lacks durable project and artifact continuity

a { text-decoration: none; color: #464feb; } tr th, tr td { border: 1px solid #e6e6e6; } tr th { background-color: #f5f5f5; }

icrosoft 365 Copilot enables me to accomplish complex analytical and engineering work without needing to know everything upfront, which is genuinely transformative.

However, the lack of durable project state, reliable artifact persistence (file generation and retrieval), and cross‑device continuity breaks real workflows. Copilot succeeds at reasoning, but outputs cannot be reliably retained, resumed, or transferred across sessions and devices.

This limits sustained use for serious work in Microsoft 365 scenarios where users expect continuity similar to Word, Excel, and OneDrive. This is not a UX polish issue — it is a workflow and demand‑growth constraint for advanced users who want Copilot as a long‑running work partner rather than a disposable assistant.

Copilot feels capable of being a first‑class Microsoft 365 collaborator, but today its lack of persistence prevents users from trusting it with real work.