# Deploying Outlook Native (Deprecated)

{% hint style="danger" %}
[Support for Office 2016 and Office 2019 ended on October 14, 2025](https://learn.microsoft.com/en-us/officeupdates/update-history-office-2019). If you haven't already begun to upgrade your Office environment to a newer version of Office, Microsoft recommends that you start now. For more information, see [Plan an upgrade from older versions of Office to Microsoft 365 Apps](https://learn.microsoft.com/en-us/deployoffice/endofsupport/plan-upgrade-older-versions-office). 

Because Microsoft has deprecated these versions of Outlook, any issues with the Reporting Plugin on those platforms are a result of Microsoft’s decision to end support. Unfortunately, we are unable to provide troubleshooting or further assistance for software Microsoft has retired.
{% endhint %}

## Introduction

The native Outlook plugin supports these versions of the desktop application:

* Outlook 2016
* Outlook 2019
* Office 365 Desktop

The Outlook plugin is static, it cannot read changes from the Lucy server like the Office 365 version can. If you want to change settings, you must re-download the plugin and redeploy.

***

## Azure (Entra ID) settings

1. Login to your [Azure portal](https://portal.azure.com) and navigate to Microsoft Entra ID (formerly Azure AD).
2. Navigate to **App Registrations** and create a **New Registration**.
3. Give the application a name.
4. For the organization type select **Accounts in any organizational directory (Any Microsoft Entra ID tenant - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)**.
5. Define a **Web** redirect URI like so: \
   `https://<yourLucyURL>.<tld>/oauth`
6. Click **Register**.

<figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2F52CXvlBrAwfi4mVLtksG%2Fimage.png?alt=media&#x26;token=9039a167-91c0-44d3-9af6-1b8421964e83" alt=""><figcaption></figcaption></figure>

* In the application overview, click the **Redirect URIs** option then select **Add a platform**.<br>

  <figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2F6ehvoIFbBR10YujvWu0b%2Fimage.png?alt=media&#x26;token=5632fa88-58c0-4649-8879-98a4a2a15573" alt=""><figcaption></figcaption></figure>
* Select the **Mobile and Desktop Applications** option, enable all three of the pre-defined URIs, then click **Configure**.<br>

  <figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2FANXqgcmk9NYZYpB8A84E%2Fimage.png?alt=media&#x26;token=1c9c612e-7cff-4dec-8316-59b156b18249" alt=""><figcaption></figcaption></figure>
* Scroll to the bottom of the **Authentication** page and enable **Live SDK Support** and **Allow Public Client Flows**, then click **Save**.<br>

  <figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2FpjG4hMQWNrKXBELH1uCA%2Fimage.png?alt=media&#x26;token=2908619d-1e05-40cc-b1df-a1ac777854d8" alt=""><figcaption></figcaption></figure>
* Navigate to **Certificates & secrets** and create a **new client secret**. Give the secret a name and expiration date, then click **Add**.
* Copy the **Secret Value**. Then navigate to the **Overview** and copy the **Application (client) ID** and **Directory (tenant) ID** as well. You will need all three values for the next steps.

## Download the plugin

Whether you are deploying the plugin manually on a single computer or globally via GPO, step one is to [Configure and download the plugin.](https://wiki.lucysecurity.com/guides/reporting-plugin)&#x20;

## Individual deployment

Local installation is simple, just run the MSI and allow it to install the plugin for you.

## Deploying via GPO

#### **1. Prepare the Plugin Package**

Ensure the plugin installer is accessible on a network share that all target computers can access. Set permissions to allow **read** access for authenticated users.

#### **2. Open Group Policy Management Console (GPMC)**

On the Domain Controller, open the Group Policy Management Console (`gpmc.msc`).

#### **3. Create a New GPO**

Right-click on the **Organizational Unit (OU)** where you want to deploy the plugin, and select **Create a GPO in this domain, and link it here**.

Name the GPO (e.g., *Deploy Lucy Plugin*).

#### **4. Edit the GPO for Software Installation**

Right-click the newly created GPO and select **Edit**.

In the Group Policy Management Editor, navigate to **Computer Configuration > Policies > Software Settings > Software Installation**.

#### **5. Add the Plugin for Deployment**

Right-click **Software Installation**, select **New > Package**.

Browse to the network share where the plugin installer is stored, select it, and choose **Assigned** to ensure it’s installed automatically on all targeted machines.

#### **6. Update Group Policy on Target Computers**

Either wait for the next Group Policy update cycle or force an update manually by running\
`gpupdate /force`.

## Technical Information

* The MSI logs operations under `C:\ProgramData\LucySecurity`
* Upon installation a temporary `config.dat` file is created, but all settings are written in the registry. The plugin may be installed in the user context (HKCU) or machine context (HKLM).
* The Plugin is available in 32 and 64-bit versions, so make sure you're downloading the correct one.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.lucysecurity.com/guides/reporting-plugin/deploying-outlook-native-deprecated.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.