Exclusive: Microsoft Office 15 will include third-party ‘Agaves’ web extensions
Microsoft is planning to allow developers to create “Agaves” web extensions to bring third-party functionality to Office clients, according to sources with knowledge of its Office 15 plans.
Context & Ripple Effects
This report builds directly on February's closer look at the Office 15 Technical Preview, which Microsoft shipped to a select group of NDA-bound customers and which surfaced the client redesign but said little about extensibility. The new sourcing fills that gap: per sources with knowledge of the plans, Office 15 will carry a framework — codenamed 'Agaves' — letting outside developers bolt web-built functionality onto Word, Excel and the other Office clients.
The claim remains a rumor — Microsoft has not confirmed it — but the pickup was unusually broad for an unannounced feature, with ZDNet's All About Microsoft blog, Neowin, Softpedia and Electronista all running versions of the same sourcing within hours. That spread signals how much attention the next Office cycle is drawing ahead of any public beta.
First-order effects
- Developers gain a prospective new surface: instead of building against desktop-native add-in APIs, they could ship lightweight web extensions that run inside Office 15's clients themselves.
- For Microsoft, Agaves would turn the Technical Preview's quiet NDA program into a controlled runway — seeding a developer ecosystem around Office before the product even gets a public name.
Second-order effects
- Vendors whose businesses rest on native Word and Excel add-ins face pressure to rewrite their offerings as Agaves-style web extensions or risk being frozen out of the next Office upgrade cycle, since Microsoft would control both the framework and its approval path.
- Rival office suites come under pressure to match the extensibility model: if documents become hosts for third-party web functionality, a suite that stays closed looks less like a platform and more like a dead end for workflow-hungry business buyers.
Third-order effects
- If the pattern holds, Office stops being a self-contained productivity suite and becomes a distribution channel Microsoft governs — shifting leverage over how enterprises assemble their document workflows from Microsoft alone toward a developer ecosystem operating under Microsoft's rules.
- That structural move points toward Office being sold less as installed software and more as an open service layer, with third-party code as a core reason to stay inside the franchise rather than defect to cheaper alternatives.
The trend: Office is evolving from a closed productivity suite into an extensible platform for third-party web apps, with Microsoft controlling the framework — a template the rest of the enterprise-software industry will feel pressure to follow.