User setup

Installing the Saga Word add-in takes a couple of minutes. There are two ways to do it — from inside Word or from the Microsoft Marketplace. If your organization deploys it centrally, it may already be installed (see Admin setup).

​

Install from Word

Windows (Microsoft 365 / Word 2021 / 2024):

1. Open Word and click Add-ins in the ribbon, then More Add-ins.
2. Search for Saga in the Office Add-in Store.
3. Click Add.

Windows (Word 2019 / 2016):

1. Go to Insert > Get Add-ins (or Store).
2. Search for Saga.
3. Click Add.

Mac:

1. Go to Insert > Get Add-ins.
2. Search for Saga.
3. Click Add.

Word for the Web:

1. Open a document in Word for the Web (via office.com or OneDrive).
2. Go to Insert > Add-ins > Get Add-ins.
3. Search for Saga.
4. Click Add.

After installation, the Saga add-in appears in the Home or Insert tab in the ribbon.

​

Install from the Microsoft Marketplace

You can also install it directly from the Microsoft AppSource Marketplace:

1. Open the link and click Get it now.
2. Sign in with your Microsoft account if prompted.
3. Follow the on-screen instructions to add the add-in to Word.

​

Signing in

When you open the add-in for the first time, enter your email and your organization’s Saga URL (e.g., https://your-firm.sagalegal.io). Saga sends you a magic link — click it to confirm, and the add-in connects to your account. You only need to do this once.

​

Troubleshooting

​

The add-in doesn’t appear in search or fails to install

• Check with your admin — On company-managed devices, your IT department may need to allow third-party Office add-ins or explicitly approve the Saga add-in.
• Check your Office license — Some Volume License (LTSC) editions have limited access to the Office Add-in Store. Your admin may need to deploy the add-in centrally instead.
• Check your sign-in — In Word, go to File > Account and make sure you’re signed in with your Microsoft account.
• Check your Word version — Go to File > Account > About Word and make sure your version is up to date. Outdated builds may have issues loading add-ins.

​

The add-in shows ‘404 not found from Microsoft Azure’ or freezes after install

This happens when Word is loading an old, sideloaded version of the Saga add-in. Sideloading was the install path used in earlier Saga onboarding rounds — your admin or account team gave you an .xml manifest file that you registered manually in Word. The manifest in that file points at a hosted URL that’s no longer served; the current URL is reachable only via Microsoft AppSource. Reinstalling the same .xml doesn’t help — the file still points at the dead URL. Fix: remove the sideloaded add-in and reinstall from AppSource. You only need to do this once; future updates then roll out automatically through the Store.

1. Remove the old add-in. In Word, open Insert > My Add-ins. Find Saga, click the ⋯ menu next to it, and choose Remove.
2. Close Word completely (quit the application, don’t just close the document).
3. Install from AppSource. Reopen Word, then either:
   • Use Insert > Get Add-ins and search for Saga, then click Add, or
   • Open Saga on Microsoft AppSource in your browser and click Get it now.
4. Open Saga from the ribbon and sign in.

The same steps apply for everyone on your team — there is no .xml file to share anymore.

​

Sign-in fails with a Microsoft ‘account doesn’t exist’ page

This happens when Word is signed in with a different Microsoft account than the one your Saga workspace expects — common on machines that have a personal Microsoft account and a work account, or two work tenants.

1. Close Word completely (quit the application, don’t just close the document).
2. Sign Word out of any extra Microsoft accounts. In Word: File > Account > Sign out. If you see more than one account listed, sign out of all of them, then sign back in with only the account you use with Saga.
3. Clear the Office add-in cache. Microsoft maintains the current cache locations at Clear the Office cache for Windows, Mac, and Word for the Web. Only Office add-in state is removed — your documents are unaffected.
4. Reopen Word, open the Saga add-in, and sign in. When the Microsoft prompt appears, pick the account you want. If no chooser is shown, click Use another account and type the email manually.

If the recovery page still appears, take a screenshot of the full URL on that page (including the client_id= and login_hint= parameters) and send it to support — that URL identifies the account Microsoft is being pointed at and lets us pinpoint the mismatch.

​

Sign-in fails with ‘Error during token exchange: failed to fetch’

The add-in couldn’t reach Saga’s authentication endpoint from inside Word.

• Corporate firewall or proxy is the most common cause. The add-in is hosted at word.sagalegal.io and calls back to your tenant’s Saga host (e.g., app.sagalegal.io or your-firm.sagalegal.io). Both need HTTPS reachability from inside the corporate network. Ask IT to allowlist them for Office add-ins.
• Stale add-in cache. Follow the cache-clear steps above.
• Office build out of date. Run File > Account > Update Options > Update Now.

​

The add-in pane is blank and never loads

The pane sometimes fails to load its JavaScript bundle on first open, especially on slow connections.

1. Close the pane and reopen it from the ribbon.
2. If still blank, restart Word.
3. If still blank, clear the Office add-in cache (Microsoft docs), then reopen.

The add-in is hosted at word.sagalegal.io and Office itself loads the add-in runtime from Microsoft’s CDN. If your firm uses a strict network policy, confirm with IT that both are reachable.

​

Track changes don’t apply to footnotes

Word treats footnote content as a separate story, and the Office add-in API can’t always propagate tracked changes into it. When a suggestion targets footnote text, copy the suggestion from the add-in pane and paste it manually inside the footnote with track changes turned on. We’re working with Microsoft on a longer-term fix.

​

Still stuck?

Contact the Saga support team with:

• A screenshot of File > Account > About Word so we can see your exact Office version and platform.
• A screenshot or recording of the error you encountered.
• Whether the issue reproduces in Word for the Web (a quick way to isolate desktop vs. browser issues).