Installation and Configuration of the Add-in

Due to recent changes to the Microsoft Legacy tokens from Microsoft in late June 2025, starting today is required a different installation process to be able the use of the plugin through Outlook or OWA. This configuration has to be performed for all the customers desiring to use the LibraCyber Outlook Add-in with a Microsoft 365 online / Exchange Online tenant.

Create App Registration for the Archiver Add-in

• Navigate to https://portal.azure.com/ and log in using your administrator credentials (make sure is the SuperAdmin of the Microsoft tenant you are configuring)
• Open the App registrations portal as shown:

• Click on the New registration button on the top left of the page
• Insert Email-Archiver-Add-in as the name of the application (Or any name you prefer to identify the APP registration)

Setup Authentication Parameters

• Now click on Authentication on the left menu:
  • Click Add a platform
  • Choose Single-page application (SPA) option
  • Enter the your Archiver hostname (e.g.: https://archiver.example.com) in Redirect URIs
  • Enter the your Archiver hostname (e.g.: https://archiver.example.com) in Front-Channel Logout URL

Setup API Permission

• Now click on API permissions on the left menu:
  • Click Add a permission
  • Select Microsoft Graph API
  • Select the following permissions under Application permissions
    • Mail.Read
  • Select the following permissions under Delegate permissions
    • offline_access
    • openid
    • profile
  • Click Done

• Click Grant admin consent and click Yes in the dialog

Copy the App Registration Data

• Take note of:
  • Application (Client) ID
  • Directory (Tenant) ID

Apply admin app consent

• Go to: App registration > Overview > scroll down > click “Go to Enterprise applications”

• Go to: Security > Permissions > click “Grant admin consent for ….”

• Accept permission request

Create Manifest.xml file for Archiver Add-in

• Go to your EmailArchiver > Settings > Authentication > Outlook add-in Microsoft 365

• Click on "+" (in case of multiple tenants, select the tenant you need to create the manifest.xml file for)
• Insert the Application (Client) ID and the Directory (Tenant) ID

• Open the "</>" button link and save it as a file.

Multi user deployment

If you need to deploy the Add-In automatically to many users you can manage to get this done centrally by connecting to Exchange Management Console.

• Log on to your Office 365 tenant through Microsoft’s Online Portal admin.microsoft.com with an admin account.
• Navigate to Settings and then Integrated Apps
• Click on Upload custom apps

• Select as App Type Office Add-in
• Upload the manifest.xml file created previously (refer to this guide)

• Choose Entire organization or Specific user/groups

• Click Next and Finish

Single user deployment

• • Log on to your Office 365 tenant through Microsoft’s Online Portal admin.microsoft.com with an admin account.
  • Navigate to Settings and then Integrated Apps
  • Click on Upload  custom apps

  

  • Select as App Type Office Add-in
  • Upload the manifest.xml file created previously (refer to this guide)

  

  • Choose Specific user/groups and specify the User

   

  • Click Next and Finish
   

Troubleshoot Login after deployment

If after deploying the Add-in is requested to login for a first time :

• Open the new deployed Add-in in Outlook or OWA

• Select the user to login and authenticate following the prompt

• Approve the permissions request and ensure that “Consent on behalf of your organization” is selected; this will be required only on the first login.

• This might process be requested the first time after deploying the new plugin