How can we help you today?

Go ahead and ask us anything.

See the KanBo newest version.

KanBo Outlook Add-in Installation (O365 & On premise)

Last modified:

email to card exchange o365 Office365 outlook

The Outlook Add-in makes it easy for you transfer information from an email to KanBo. This App equips you with the ability to convert Emails into KanBo Cards. It is also possible to select an existing KanBo Card and attach information from the email to it.

You can read more about The KanBo Outlook Add-in here.

Install Outlook App in Exchange 2013 or Office 365

To install the Outlook application on Kanbo, you need to have at least Exchange 2013 or Outlook 2013. KanBo won't work on Outlook 2010, but you can use OWA (Outlook via a browser) to get KanBo Outlook app instead of upgrading to Office 2013/2016.

You must be a KanBo Manager to install the Outlook App.

Check the Outlook Add-in plugins

    Make sure you have `KanBo.OutlookAppPlugin.dll` and `KanBo.OutlookAppPlugin` to your KanBo extensions folder.

    In Azure installation scenario, you should go to htttps://{yourKanBoName} -> Debug Console -> Powershell -> site -> wwwroot and enter KanBo Extensions folder.


      Get the id of issuers expected from Outlook.

      First way:

      Go the metadata file, it should be at location:
      For on-premise: `https://**exchange address**/autodiscover/metadata/json/1`
      For O365: `**your domain**/metadata/json/1`

      See the **issuer** field, the example outputs are:

      On-premise: `[email protected]`
      O365: `[email protected]`

      The part after @ is identifying your domain.

      Fill the `...` with `00000002-0000-0ff1-ce00-000000000000` - it's the constant identifier for outlook apps.

      The result should be:
      On-premise: `[email protected]`
      O365: `[email protected]456789012`

      Second way:

      Run the outlook app without providing any issuers (you must apply step 3 - enter the configuration... to run the Outlook app)

      Example of configuration in KanBo web.config

              <accept id="">

      See the error - the numbers in the communicate are your Issuer ID.

      Modify the web.config of KanBo.

      Go to your KanBo location on a server or in Azure, scenario htttps://{yourKanBoName} -> Debug Console -> Powershell -> site -> wwwroot -> web.config/. Start modyfing it by adding the following entry in the <plugins> section and paste your Issuer ID.

              <accept id="[email protected]xxxx6">

      Get KanBo Outlook app manifest

      Go to https://{your-kanbo-url}/plugins/outlook-app/manifest.xml

      Copy the entire manifest to Notepad or other text editor and save it as manifest.xml.

      Add KanBo Outlook Add-in Manifest to Exchange

      On Premise Exchange deployment

      Go to Exchange admin center -> Organization -> Add ins and add this add-in. Use + button and then Add from file.

      Use the manifest.xml file which as created earlier.

      When the manifest.xml is successfully added, double click on KanBo Outlook App and set it to be Optional, enabled by default and save.

      Cloud (Office 365/Exchange Online) deployment

      Go to Office 365 admin center and select Try the preview (of the new Office 365 admin center).


      Go to and select Deploy the Add-in.

      Now select Next.

      Browse for KanBo Outlook App manifest in I have the manifest file (.xml) on this device. 

      In Next window, specify who has access. Then, select Deploy Now.

      Now select Next.

      In the last window, select Close.

      According to Microsoft, it might take up to 12 hours to deploy the add-in, hovewer it might appear right away if the tenant is not busy.

      Add a test mail to KanBo.

      When all the steps are performed, go to your Outlook (OWA or client) and use KanBo Outlook Add-in !

      See how you can use it by reading this article:

      #### Constructing the issuers list

      To ensure that only allowed exchange servers are using the application, there's a need to provide your list of domains/issuers that will be able to user your application. There are two ways to detect issuers list:

      Official MS Description


      In case your KanBo is hosted on a new, custom domain, you might see the following error.

      You will be redirected to the following URL, which is not registered as the app's launch URL.
      https://your old kanbo address/_p/93243-489293842?KBRedirSkip=sp
      If you trust this URL, click here to go to the app now.
      Otherwise, return to the previous page or close this page.
      If I Trust the URL and click, then comes this message:
      Fail authenticating: No KanBoToken field Fail authenticating: Status: EndpointAuthorityDoesNotMatch ErrorInfo: You could not authenticate with any of your identities and there are no more redirect targets

      In this case you must open KanBo web.config, edit it and add the following entry in the plugins section. You must adjust the address to the address of your new, custom domain for KanBo. This will override the old KanBo address and remove problems connected to it.

       <server-url>https://your kanbo new address</server-url>

      This article was helpful for 1 person. Is this article helpful for you?