Skip to content

Microsoft Word Integration

The Parachute Word add-in brings AI-powered document drafting and document review directly into Microsoft Word. Draft, review, and manage legal documents without leaving your familiar Word environment.

What you can do

  • Draft documents - generate legal documents using Parachute’s AI directly in Word
  • Review content - run document reviews on documents you’re editing
  • Access your knowledge base - reference your organisation’s policies while drafting
  • Collaborate - work with your team and experts using Parachute’s collaboration features within Word

Supported platforms

PlatformStatusNotes
Word on WindowsSupportedFull feature support via WebView2
Word on MacSupportedFull feature support via WebView2
Word on WebSupportedWorks in Edge and Chrome
Word MobileLimitedReduced Office.js feature support

Setup

For individual users (sideloading)

  1. Open Microsoft Word
  2. Go to Insert > Add-ins > My Add-ins
  3. Click Upload My Add-in > Browse for a manifest
  4. Select the Parachute manifest file provided by your administrator
  5. The Parachute add-in appears in your Word ribbon

For organisations (centralised deployment)

Administrators can deploy the add-in to all users in your Microsoft 365 tenant:

  1. Go to the Microsoft 365 Admin Center
  2. Navigate to Settings > Integrated Apps > Centralized Deployment
  3. Upload the Parachute manifest or search for Parachute in the store
  4. Select the users or groups who should receive the add-in
  5. Deploy - the add-in will appear in Word for all selected users within 24 hours

Authentication

The add-in supports two authentication methods:

  • Microsoft 365 SSO - if your organisation uses Microsoft 365, the add-in can authenticate using your existing Microsoft credentials for a seamless sign-in experience
  • Auth0 login - if SSO isn’t available, the add-in opens a login dialog where you sign in with your Parachute credentials

Usage

Once installed, click the Parachute button in the Word ribbon to open the task pane. From there you can:

  1. New document - start a fresh AI-drafted document in your current Word file
  2. Review current document - run document reviews on whatever you’re currently editing
  3. Ask a question - query your knowledge base about legal topics relevant to your document

Troubleshooting

”Add-in could not be started”

This error comes from Word itself, before the Parachute add-in finishes loading, so it almost always points to something on the computer or network rather than your Parachute account. The steps below are written for Word on Windows, where most of our customers work.

First, two quick things that resolve most cases:

  • Fully close every Office app (Word, Excel, Outlook, PowerPoint), then reopen Word. Office shares one add-in process, so a single stuck app can block the add-in everywhere.
  • Confirm you’re online and that https://app.goparachute.ai loads in a browser. If it doesn’t, the add-in can’t load either.

If the error persists, work through these in order.

1. Clear the Office add-in cache. A stale cache is the most common cause. In Word, go to File > Options > Trust Center > Trust Center Settings > Trusted Add-in Catalogs, tick Next time Office starts, clear all previously-started web add-ins cache, select OK, then fully close and reopen Word (Office 2108 or later). If that option isn’t there, your IT team can clear it manually by deleting the contents of %LOCALAPPDATA%\Microsoft\Office\16.0\Wef\ while Word is closed.

2. Check nothing is blocking Parachute. Corporate firewalls, VPNs, proxies, and security software (for example Zscaler or Netskope) can block the add-in or break its secure connection. On the affected computer, confirm both https://app.goparachute.ai and https://appsforoffice.microsoft.com load in a browser without certificate warnings. Ask your IT team to allow app.goparachute.ai, appsforoffice.microsoft.com, and *.office.com, and to turn off SSL inspection for them. Also check the computer’s date, time, and time zone are correct - a wrong clock breaks the secure connection.

3. Repair Office. The add-in runs inside a Windows component (Microsoft Edge WebView2); an online repair reinstalls it. Close all Office apps, open Settings > Apps > Installed apps, find Microsoft 365, choose Modify > Online Repair > Repair, then reopen Word. If that doesn’t help, try launching Word once via right-click > Run as administrator.

4. Update Word. Older builds can’t run modern add-ins (Office 2016 or later is required; Microsoft 365 recommended). In Word, go to File > Account > Update Options > Update Now, then restart Word.

5. Send us a diagnostic log. If none of the above works, Word’s own startup log tells us why it’s failing. Capturing it needs a one-line command and Node.js, so it’s best done by your IT team. Close all Office apps, open Command Prompt (Start > type cmd), and run:

npx office-addin-dev-settings runtime-log --enable "%USERPROFILE%\Desktop\parachute-addin-log.txt"

Reproduce the error in Word, then turn logging back off with npx office-addin-dev-settings runtime-log --disable and email the parachute-addin-log.txt file from the desktop to support. Our add-in’s ID is 12420cde-be57-43ac-b718-53c7390b5e50 (shown as SolutionId in the log).

If you can’t run that command, send support a screenshot of the error, your Word version (File > Account > About Word), your Windows version, and whether https://app.goparachute.ai loads in your browser.

Add-in doesn’t appear in Word

  • Verify the manifest was uploaded correctly
  • For centralised deployment, allow up to 24 hours for propagation
  • Check that your Office version supports add-ins (Office 2016 or later)

“Refused to display in a frame” error

This typically indicates a Content Security Policy issue. Contact your Parachute administrator - the CSP headers may need updating for your deployment.

SSO fails

If Microsoft 365 SSO doesn’t work (common with Conditional Access policies or MFA configurations), the add-in automatically falls back to dialog-based authentication. No action needed - just sign in through the dialog.

Next steps

Was this page helpful?