Microsoft's Copilot for Microsoft 365 has been available to enterprise customers for over 18 months. We've deployed and managed it across organizations ranging from 50 to 2,000 employees. The verdict is more nuanced than either its enthusiastic advocates or skeptical critics suggest.
What genuinely works
Meeting summaries and action item extraction are Copilot's most reliable, highest-adoption features. In organizations where Teams meetings are the primary collaboration medium, Copilot's ability to generate structured summaries with assigned action items has meaningfully reduced the "meeting recovery" time tax. Teams that previously spent 30–45 minutes after meetings writing up notes and distributing them report this dropping to under 5 minutes.
Email drafting is effective for routine, templated communications — follow-ups, status updates, meeting requests, brief replies. For nuanced communications (difficult conversations, sensitive negotiations, complex technical explanations) the drafts require substantial editing and arguably waste more time than they save.
Excel's Copilot integration is genuinely powerful for users who know what analysis they want but don't know the formulas or PivotTable configurations to produce it. The ability to describe an analysis in plain language and have it executed is high-value for the 80% of Excel users who never progressed beyond basic formulas.
What doesn't work as advertised
Copilot's "across all your data" promise significantly overstates current capability. Retrieving relevant information from your Microsoft 365 corpus requires that content to be well-organized, appropriately shared, and recently accessed. In practice, most large organizations have years of poorly organized SharePoint content, inaccessible archived email, and files shared with the wrong permissions. Copilot exposes this data quality problem rather than solving it — organizations that expected plug-and-play knowledge retrieval have been disappointed.
The ROI case is challenging to close. At $30 per user per month, Copilot needs to generate roughly 45–60 minutes of productivity gains per user per day to justify its cost at typical knowledge worker labor rates. In our experience, most users achieve 15–25 minutes per day — meaningful, but not enough to clear the ROI bar at current pricing.
Recommendations
Deploy Copilot selectively, not broadly. Focus initial rollouts on meeting-heavy roles (executives, project managers, account managers) where the summarization features deliver immediate, measurable value. Invest in data hygiene before or alongside deployment — Copilot's quality is ceiling-limited by the quality of your Microsoft 365 content organization. Set realistic expectations: Copilot is a productivity enhancement, not a transformational system.
Found this useful? Share it.