Skip to main content

​
Before you begin

Before you share or deploy a manifest file, confirm:
  • The organization’s Global Auth migration status
  • The organization’s processing region: EU, US, AP, or AU
  • Whether the organization is multi-org
  • Whether the admin can use Microsoft AppSource or the Microsoft 365 admin center
Most admins should use the standard install flow. Use a manifest file when AppSource is unavailable or the client’s deployment environment requires XML-based deployment.

​
What the Word Add-in manifest is

The Word Add-in manifest is an XML file that tells Microsoft Word how to install and load the Legora Word Add-in. It includes information such as:
  • The add-in’s app ID
  • The add-in name and metadata
  • The Legora domains the add-in can access
  • The permissions and entry points Word needs to run the add-in
Admins can use the manifest to deploy the add-in centrally through the Microsoft 365 admin center or, for on-premises Exchange, with New-App or Set-App.

​
When to use a manifest file

Use a Word Add-in manifest when the client has one of these requirements:
  • On-premises or older Exchange: The client uses on-premises Exchange or Exchange Online below version 15.2
  • Central deployment at scale: The client needs org-wide deployment and must split on-premises New-App or Set-App deployments into groups of 1,000 users or fewer
  • Microsoft Store or AppSource is blocked: The client’s security policy blocks Microsoft Store or AppSource access
  • Global Auth reinstall: The organization needs to reinstall the Word Add-in after Global Auth migration

​
Choose the correct Word manifest

Use the client’s Global Auth migration status and processing region to choose the correct file.
  1. If your org has completed Global Auth migration: Use the Global manifest.
  2. If your org is multi-org: Use the Global manifest.
  3. If your org has not migrated: Use the manifest that matches the org’s current processing region: EU, US, AP, or AU.

​
Word Add-in manifests

​
Downloads

Global: manifest-legora-global.xml EU: manifest-legora-eu.xml US: manifest-legora-us.xml AP: manifest-legora-ap.xml AU: manifest-legora-au.xml

​
Deploy the Word Add-in manifest

  1. Confirm which Word manifest the org needs.
  2. Download the matching XML file.
  3. Open the Microsoft 365 admin center.
  4. Deploy the add-in centrally with the XML manifest file.
  5. For on-premises Exchange, use New-App or Set-App.
  6. If the org has more than 1,000 users, split the install into multiple deployments.
  7. Ask users to open the add-in in Word and enter their work email in the sign-in window.

​
If someone opens the XML file in Word

The manifest is not a Word document. It should not be opened directly in Word. If someone opens the file in Word, they may see a message about non-standard XML elements. This does not mean the manifest is broken. Ask the IT admin to upload or deploy the XML file through their Microsoft admin tools instead.