Versions Compared

Key

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

...

Tip

Conditions for Connection

  • This extention is installed on Outlook Web App or Exchange On-Premises/Exchange Online.

  • OWA server must access to 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.

Creating Manifest File

Troubleshooting

OWA Classifier Setup

Separate installation method for individual users or for all users is provided for OWA/Office 365 environment.

Web Service Address: No matter which method you use, you must provide the address used to access OWA. You must add /ews/exchange.asmx at the end. If OWA has an SSL, GEODI must also work with an SSL.

OWA Setup for Single User

Username and password must be given. Username, if it is in the domain, should be written as domain@username, if not, should be written directly. After entering the information, "Install to Server" completes the installation for the relevant user.

...

The batch installation steps are described below in the "Installation for All Users" step.

OWA Installation for All Users

With this process, we will be able to deploy the OWA plugin to all users defined on the Microsoft 365 Admin Center. In the installation tab in the GEODI Classifier settings, we download our xml file that we will use during installation with "Download Manifest".

We click + in the Microsoft 365 Admin Center Organization / Add-ons section.

On the screen that opens, click Choose File, select our downloaded xml manifest file and upload it. Classifier OWA plugin has started to be distributed to all or desired users in the institution. Depending on the number of people, the distribution process will take between 3-24 hours. In order for the plugin to serve smoothly, the OWA plugin must have access to GEODI.

Now our classification plugin can also be used in Outlook, which we access through the browser

...

  1. GEODI will create manifest file automatically. Download .xml file by pressing “Download Manifest” button in setup tab which itself is in GEODI Classifier settings.

  2. You can make an Add-In upload from 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 may end between 3-24 hours.

...

Troubleshooting

Expand
titleOWA add-in doesn't appear while sending an e-mail in an On-Prem Exchange environment.

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 OWA e-mail users.

There may be several reasons.

  1. Is the GEODI server running?

  2. Make sure that typed down 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 repeated.

  3. Microsoft OWA servers must see the GEODI server. If you are using Exchange Online, 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 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.

Expand
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.

Expand
titleThere has been a change in classification rules. Is it necessary to re-upload the manifest file?

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
titleCan i create the manifest file with many projects and perform an Exchange upload?
  1. 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 issue.