Microsoft 365 Copilot has now been broadly available for over a year, and we've had enough enterprise deployment experience to move beyond the marketing narrative. The honest assessment: it delivers real value in specific contexts, disappoints in others, and requires deliberate adoption strategy to realize ROI.
What's Actually Working
Meeting summarization and action item extraction: This is the use case with the highest user satisfaction across our deployments. Teams that run frequent status meetings are saving 2-4 hours per week per knowledge worker. The accuracy is high enough that users trust the summaries without extensive review.
Email drafting and thread summarization: In high-volume communication environments — customer success, sales, executive communications — Copilot's drafting capability saves meaningful time. The quality requires editing but provides a solid starting point.
Document first drafts: Copilot in Word is effective for generating structured first drafts from prompts or existing documents. Users consistently report it reduces the "blank page" friction significantly.
Data exploration in Excel: For users who aren't proficient SQL writers, Copilot's ability to analyze spreadsheet data and surface patterns in plain language has been a genuine capability unlock.
What's Underdelivering
SharePoint-based knowledge retrieval: The promise of Copilot finding answers from your organizational knowledge base frequently falls short. Quality depends heavily on your SharePoint hygiene — most organizations' SharePoint is not in a state where AI retrieval returns reliable results.
Cross-application reasoning: Complex tasks that require Copilot to synthesize information from multiple Microsoft 365 apps (pulling context from Teams, email, and SharePoint simultaneously) are inconsistent. The multi-app orchestration is improving but remains unreliable for high-stakes workflows.
Adoption without change management: Organizations that simply deployed licenses and sent an announcement email saw under 20% active usage after 90 days. Copilot requires explicit adoption programs — use case definition, manager modeling, and workflow integration.
Setting Up for Success
The organizations seeing the best ROI shared common practices: they defined three to five prioritized use cases before launch, ran small cohorts before broad deployment, established champions in each team, and actively measured usage and satisfaction at the 30/60/90-day marks.
Copilot isn't a deploy-and-forget tool. It's a capability layer that needs integration into existing workflows.