Amazon Ships Its Agent Into Word Through Microsoft's Own Add-In Store

Amazon has put its Quick assistant inside Microsoft Word, Excel, PowerPoint and Outlook as generally available extensions, on both desktop and web ^[1][2]. Existing Quick customers on Plus, Professional or Enterprise plans pay nothing additional for them ^[3], which means the question of which assistant occupies the ribbon in Word is now a thing an IT department chooses rather than inherits.

The pitch is not model quality. AWS says outright that the value is not in the underlying agentic model but in the breadth of connected data the agent brings to the interaction ^[5]. The named surface area is the tell: AWS infrastructure, Amazon Quick Sight dashboards, Salesforce pipelines, Jira projects, Slack conversations and SharePoint repositories ^[6], with Quick Sight dashboards, Spaces, AWS data sources and third-party integrations reachable without leaving the Office app ^[4]. Amazon is competing on where the customer's data already sits, and it is willing to reach into a rival's application to do it.

The mechanics matter more than the demo. Quick appears as a persistent side panel opened from the ribbon, and the agent sees the document and acts on it ^[7]. In Word it can find and replace text, insert sections and reformat content, then show a visual comparison of what it changed ^[8]. Every agent action in a document is tracked, surfaced either as an audit trail link or as a visual comparison in the chat, with each change carrying a selectable reference back to the affected content ^[9]. Conversation history survives closing the panel, and in Outlook each email thread keeps its own thread of conversation ^[10]. That audit trail is the part a compliance team will actually ask about, and it is the part that distinguishes an editing agent from a chat window.

Distribution is the quiet part. There is no client-side install; the extensions run entirely in the cloud ^[11]. An administrator pushes them to targeted users and groups from the Microsoft 365 admin center using a standard manifest, the same mechanism as any Microsoft 365 add-in ^[12]. A user can also self-install from the Microsoft add-in store by searching for "Quick" and choosing Add, after which updates ship automatically ^[13]. Authentication uses Quick's native model and does not require an Entra app ^[15], removing one of the usual identity integration steps.

The exception is Outlook. Because most organisations restrict Graph API permissions, AWS advises that the Outlook extension typically needs admin approval for full functionality and should be planned as an admin deployment ^[14]. So three of the four extensions are plausibly user-installable and one is not ^[17], which is where shadow adoption will start and where governance will notice.

Treat the productivity numbers with the caution they deserve. The AWS author's account of drafting request-for-proposal responses in hours where a team previously took weeks, and building customised presentations in an hour rather than a day or two, is one person's own workflow ^[16].

What to watch: whether Microsoft leaves the add-in path open on the same terms, how many tenants block the manifest outright, and whether admins who approve Graph permissions for Outlook understand the scope of what they are approving.