Versions Compared

Version Old Version 10 New Version Current
Changes made by

Ozan Ergun

Ozan Ergun

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Table of Contents
stylenone

Tip

Conditions for ConnectionMinimum Setup requirements

  1. This

extention is

  1. extension can be installed on the Outlook Web App

or

  1. , Exchange On-Premises

/

  1. , or Exchange Online.

  2. The OWA server must access

to

  1. the GEODI server

and SSL must be defined for GEODI address. Make sure this address is valid from UI.User name and password must be created in such that they’ll not be changed and they should not get changed. In the case of change, same procedure must be repeated

  1. , (The mail server requires SSL for GEODI Url)

    1. For Exchange Online GEODI Url must be public.

  2. The user name and password for the token should not be changed. Otherwise, you will have to repeat the installation.

Creating Manifest File

  1. GEODI will create manifest file automatically. Download .xml file by pressing Create the Manifest → You can download the .xml file with “Download Manifest” button in the setup tab which itself is in GEODI Classifier settings.You can make an .

  2. Load the manifest → Use Add-In upload from in Microsoft 365 Admin Center/Built-In Apps for all defined users or desired ones.

  3. After this process, the system will start distribution. Distribution phase Deployment may end between take 3-24 hours.

...

Troubleshooting

.
Expand
titleOWA add-in doesn't appear puop-up does not show while sending an e-mail in an .

  1. Your policy settings may be so, change the settings

  2. For On-Prem Exchange environment

  1. : This is an issue that must be solved in Microsoft side. You should take the actions in the link below. It should work afterwards. You don’t have to re-create the manifest file.

https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/outlook-on-send-addins?tabs=classic#install-outlook-add-ins-that-use-on-send

View file
nameEnablingonSenDforclassicOWA.pdf

Expand
titleAdd-in cannot be seen by did not activate in OWA e-mail users.

There may be several reasons.

  1. Is the GEODI server running?

  2. Make sure that typed down Before creating the manifest file, make sure the GEODI URL address in the UI was correct before the manifest file is created. If it was wrong, the manifest creation and uploading must be repeatedis correct. Otherwise, repeat the installation.

  3. Microsoft OWA servers must see the GEODI server. If you are using Exchange Online, the GEODI address must be public.

  4. SSL must have been defined for the GEODI address. Be sure that SSL is defined and that it is not expired.

Expand
titleSuddenly Add-in stopped working!

  1. Is the GEODI server running?

  2. Is the project that is used to create the manifest file still active? If not, revert the project or re-create it. In case of re-creation, the manifest process must be repeated.

  3. Is the TokenUser and its password still valid. ? If not, the manifest process must be repeated.

All classification changes made in the project where you defined and created a manifest file are automatically reflected. There is no need to re-upload
Expand
Expand
titleThere has been a change in classification rules. Is it necessary to re-upload the manifest file?
titlePop-up doesn't appear.

  1. SSL must have been defined for the GEODI address. Be sure that SSL is defined and that it is not expired.

  2. If SSL definitions are not done on GEODI server (done over a LoadBalancer for example), “ServerUri” must be defined in SystemSettings.json folder.

Does Policy changes require Manişfest to be reloaded.

  1. No, all changes applied automatically.

  2. Manifest reload is required in cases like GEODI Url or Tokenuser changes.

Expand
titleCan i create the manifest file with many projects and perform an Exchange upload2 or more manifest?

  1. Yes, It can be done for testing or to do classification definitions over specific users.

  2. You can create a manifest file by creating different projects.

  3. If the manifest files will be used on the same Exchange server, you should definitely contact with our Technical Support Team. They will you about the issueother requirements. Create multiple projects and manifest files for each.