> ## Documentation Index
> Fetch the complete documentation index at: https://support.legora.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Outlook Add-in manifests

> In this article, you’ll learn what the Outlook Add-in manifest is, when to use it, and how to choose the correct manifest for a client’s organization.

## 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 Outlook Add-in manifest is

The Outlook Add-in manifest is an XML file that tells Microsoft Outlook how to install and load the Legora Outlook Add-in.

It includes information such as:

* The add-in’s app ID
* The add-in name and metadata
* The Legora domain the add-in should connect to
* The permissions and configuration Outlook needs to run the add-in

Admins can use the manifest to deploy the add-in centrally in the Microsoft 365 admin center. For a scripted deployment, use the Centralized Deployment PowerShell cmdlets. For on-premises Exchange, use `New-App` or `Set-App`.

## When to use a manifest file

Use an Outlook 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 Outlook 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.

## Outlook Add-in manifests

| **Region** | **File** | **App ID** | **Target domain** |
| - | - | - | - |
| EU (default) | outlook-addin-manifest-eu.xml | 12345678-1234-1234-1234-123456789014 | [outlook-addin.eu.legora.com](http://outlook-addin.eu.legora.com) |
| US | outlook-addin-manifest-us.xml | 12345678-1234-1234-1234-123456789015 | [outlook-addin.us.legora.com](http://outlook-addin.us.legora.com) |
| AP | outlook-addin-manifest-ap.xml | 12345678-1234-1234-1234-123456789016 | [outlook-addin.ap.legora.com](http://outlook-addin.ap.legora.com) |
| AU | outlook-addin-manifest-au.xml | D9C0A5B8-5B0A-4E9F-A808-6ACEB92012AD | [outlook-addin.au.legora.com](http://outlook-addin.au.legora.com) |
| **Global** | [outlook-addin-manifest-global.xml](https://outlook-addin.legora.com/manifests/outlook-addin-manifest-global.xml) | EF25030E-A99A-4657-BD4D-611A2987F8CF | [outlook-addin.legora.com](https://outlook-addin.legora.com) |

## Downloads

Global: [outlook-addin-manifest-global.xml](https://outlook-addin.legora.com/manifests/outlook-addin-manifest-global.xml)

EU: [outlook-addin-manifest-eu.xml](https://outlook-addin.eu.legora.com/manifests/outlook-addin-manifest-eu.xml)

US: [outlook-addin-manifest-us.xml](https://outlook-addin.us.legora.com/manifests/outlook-addin-manifest-us.xml)

AP: [outlook-addin-manifest-ap.xml](https://outlook-addin.ap.legora.com/manifests/outlook-addin-manifest-ap.xml)

AU: [outlook-addin-manifest-au.xml](https://outlook-addin.au.legora.com/manifests/outlook-addin-manifest-au.xml)

## Deploy the Outlook Add-in manifest

Microsoft is discontinuing the Exchange admin center page for Outlook add-ins. Deploy the manifest from the Microsoft 365 admin center. You need the Global admin or Exchange admin role.

1. Confirm which Outlook manifest the organization needs.
2. Download the matching XML file.
3. Open the [Microsoft 365 admin center](https://admin.microsoft.com).
4. In the left navigation, open **Settings** > **Integrated apps**.
5. Select **Upload custom apps**.
6. Choose **Office Add-in** from **App type**.
7. Upload the XML file, or paste its URL and select **Validate**.
8. Select **Add users**.
9. Choose **Entire organization**, **Specific users/groups**, or **Just me**.
10. If the wizard asks for consent, select **Accept permissions**.
11. Select **Finish deployment**.
12. Ask users to open the add-in in Outlook and enter their work email in the sign-in window.

To deploy with a script, use the [Centralized Deployment PowerShell cmdlets](https://learn.microsoft.com/en-us/microsoft-365/enterprise/use-the-centralized-deployment-powershell-cmdlets-to-manage-add-ins). `New-OrganizationAddIn` uploads the manifest.

For on-premises Exchange, use `New-App` or `Set-App`. If that install covers more than 1,000 users, split it into groups of 1,000 or fewer.

## If someone opens the XML file

The manifest is not a document for end users. It should not be opened directly.

If someone opens the file, they may see XML code or a message from the app they used to open it. 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.