The final task in setting up free time lookups for Microsoft 365 is to configure Domino's Exchange Busytime Connector (ExConn) server task with credentials from Microsoft 365.

Before you begin: Complete the steps in Setting up the Domino credential and certificate stores and Adding an application in Microsoft Azure AD.

Ensuring the ExConn task is started

Make sure that the ExConn task is started in one of the following ways:

• Check the running tasks to confirm ExConn is there.
• Run this console command: load exconn
  • If ExConn is not running, the command starts it and you see "Exchange Busytime Connector started" on the console.
  • If ExConn is already running, you see the following messages on the console:
    Exchange Busytime Connector started
    Exchange Busytime Connector: Error initializing console command queue: Message Queue name already in use.
    Exchange Busytime Connector: Error initializing: Message Queue name already in use.
    Exchange Busytime Connector shutting down

You must provide the ExConn task with the credentials it needs to communicate with Microsoft 365.

• Run the following console command:

  tell exconn configure DOMAINNAME CLIENTID CLIENTSECRET TENANTID

DOMAINNAME is the DNS name of the target domain, such asexample.com

CLIENTID and CLIENTSECRET are values you recorded when registering the Microsoft 365 application

TENANTID is the tenant-id of the domain in Microsoft 365 that you recorded when registering.

Use the console results to verify the setup:

Table 1. Console messages for ExConn configuration

Console message	Meaning/action to take
Credentials for domain DOMAINNAME have been saved	Credentials have been validated and saved into the credential store. Free time searches of the specified domain can now be done.
Exchange Busytime Connector: Configure command error: File does not exist"	You configure the credential store.
Exchange Busytime Connector: CONFIGURE command error: Command parameter list was incomplete	Not all of the required configure command inputs were provided. Check the console command and add any missing values.
Exchange Busytime Connector: CONFIGURE command error: Invalid credentials	The provided credentials could not be validated. Check the console command and correct any invalid values. If the problem persists, it could be related to SSL issues. These can be diagnosed using the SSL debug INIs DEBUG_URLOPEN=1 and maybe DEBUG_SSL_ALL=2 along with the INI DEBUG_EXCHANGE_CONNECTOR=15

Parent topic: Setting up free time lookups for Microsoft 365

Help on Help

All Help Contents

Help on Help