Skip to main content
The Microsoft Word replica implements 21 endpoints of Microsoft Graph v1.0 for one OneDrive. Word files are real .docx packages built from paragraphs, with PDF conversion on download. Its key is microsoft-word. It was tested with @microsoft/microsoft-graph-client.

Connect

Node
This is what ancha connect microsoft-word --lang ts prints. The Graph client signs only Microsoft’s HTTPS hosts and drops a capitalized Authorization header elsewhere, so the token also goes in fetchOptions as a lower-case header. Its api() takes paths, so follow an @odata.nextLink with the part after /v1.0.

Endpoints

All 21 endpoints are partial. Anything else returns HTTP 501 with Graph’s error shape and x-ancha-gap: 1.

Starter data

The microsoft-word-starter dataset is the OneDrive of ancha@acme.example in the tenant Acme. The users are the automation account, Anna Fischer, Tom Hughes, Mike Turner and the external “Pinecrest Health Legal”. Every document is a .docx whose paragraphs ancha sandbox configuration --tools microsoft-word --json prints.

Checks

Microsoft Word has no state checks. Use trace checks, for example { called: "POST /v1.0/me/drive/items/*/invite" } or { not_called: "DELETE /v1.0/me/drive/items/*" }.

Limits

  • One OneDrive. Word files are real .docx packages built from paragraphs, with PDF conversion. No Word document object model, comments or co-authoring.
  • The Graph client signs only HTTPS Graph hosts: set baseUrl to MICROSOFT_GRAPH_API_URL plus / and pass the token as a lower-case authorization header in fetchOptions.headers. Follow @odata.nextLink with the part after /v1.0.
  • Invitations and sharing are recorded, never emailed; no upload sessions, delta queries or shared-with-me.