---
id: "t-2026-07-17-microsoft-context-tax"
type: "thought"
title: "Microsoft's biggest obstacle to AI ROI may be Microsoft Office"
date: "2026-07-17"
week: "2026-W29"
url: "https://nosov.ai/writing/microsoft-ai-roi-office/"
linkedin: "https://www.linkedin.com/feed/update/urn%3Ali%3Ashare%3A7483790732160512000"
frames: ["specification", "tacit-to-explicit"]
author: "Ivan Nosov"
---

# Microsoft's biggest obstacle to AI ROI may be Microsoft Office

Microsoft’s biggest obstacle to extracting ROI from AI may be Microsoft Office.

Copilot entered the world’s dominant productivity suite with a distribution advantage nobody else could replicate. More than two years later, Microsoft reported over 20 million paid Copilot seats against more than 450 million commercial Microsoft 365 seats - at most 4.4%. The denominator turns an impressive headline into weak penetration: over 95% of the installed base still had no paid Copilot license.

The architecture explains part of the gap. Copilot began as an assistant inside applications, grounded through Microsoft Graph. OpenAI and Anthropic moved toward an LLM-native workspace: a project folder containing selected sources, stable instructions and tools, with permission to execute multi-step work.

Microsoft is now catching up. Copilot Cowork brings multi-file tasks, folder access and reusable skills into its environment, while retaining two constraints created by Microsoft itself.

The first is context. A month-end close needs 20 approved files, one mapping table, explicit rules, known exceptions and a defined output. Broad retrieval across SharePoint, Teams and Outlook adds ambient context - drafts, duplicates and outdated decisions. Relevance does not establish authority.

The second is format. `.docx`, `.xlsx` and `.pptx` are ZIP packages containing XML. An agent must extract content, reconstruct structure, preserve formulas and formatting, then validate the rendered output. With `.md`, `.html`, `.csv` and `.json`, the content and structure are directly readable and editable. The difference is an entire conversion and rendering layer across every file, not a marginal token saving.

I removed manual Excel and PowerPoint editing from my workflows more than six months ago. I dread the rare task that forces me to touch either by hand - it is slow, brittle and unproductive. My working layer is now Markdown, HTML, CSV and JSON, with Office formats generated only when someone needs the final artifact. I have never looked back.

Microsoft therefore pays a translation tax from Office formats and an ambiguity tax from ambient organizational context. Both appear as more tokens, more actions, longer execution, higher consumption cost and more human review.

Cowork fixes the direction of travel, while the economics still run through an architecture built before LLMs.

ROI from enterprise AI will be decided by the cost of constructing trustworthy context. Everything else is noise.