Calendar sync

Setup for online accounts

Not what you were looking for? Go to Exchange Calendar Sync connect to an on-premise Exchange Server

Overview

The purpose of Calendar sync product is to synchronise the data between Evatic Service users’ calendar and their Outlook mail accounts in Microsoft Exchange Server. This data is fetched from events, tasks, assignments and order lines. The events can be all day events, private, public, or within a specified time interval and some of the events can be regularly scheduled.

In case multiple companies and/or departments are used, then Calendar Sync requires one integration set up per company/department.

Evatic now provides a possibility to connect to Azure portal customers using Microsoft.Graph to run the Calendar Sync job.
The benefit of this is that Microsoft Identity takes over the connection to the database, we no longer require any users' or delegate user's login credentials or access to mail accounts to connect and perform the sync.

Configuring this integration is a 2-step job - on the Azure portal side and in Evatic Service Hub

Integration setup - Azure side

Get access to mail accounts without a user

Documentation on how to set this up in your mail service can be found here: Get access without a user

For setting application permissions, set Calendars.ReadWrite as the sync needs write access to the calendars.

Register your Azure portal with the Microsoft Identity platform

  • How to set this up depends on how you have set up your mail service in Azure. See docs.microsoft for instructions.

From this application you will get a Tenant Id, an Application Id and a Client Secret which you need for configuring your integration in Evatic Service Hub, so make sure you copy these and keep for future reference.

Integration setup - Evatic side

Up-to-date system requirements can be found here.

  • Install and have access to Evatic Admin Web (EAW) and Evatic Service Hub (ESH)
  • In EAW - User: add the user's Outlook 365 mail address to the External User name field. Also, a technician need to be added for the users if you want to access engineer availabilites and assigned jobs.
  • Have ESH installed and running on your system.

Creating and configuration the integration

  • If you don't already have a running Calendar Sync integration, create new integration for Calendar Sync. An integration with Evatic Calendar Sync type will be available in ESH when pressing + Add Integration button.

When configuring the integration for use with microsoft online/Azure portal, values for the parameters below need to be provided or selected:

  • Evatic Database must be selected from the drop-down list
  • Name field needs to be populated
  • Description field can be populated
  • Company
  • Department
  • Calendar Synchronization settings

    1. Synchronise both ways: When not checked - only from Evatic -> Exchange. When checked, also Exchange -> Evatic

    2. Number of days back/forward for full sync

    3. Full sync interval (minutes)

    4. In addition, for Microsoft Online, the checkbox Microsoft Azure Server must be checked.

      Three new fields will be visible:

      • Microsoft Azure Tenant Id
      • Micrsoft Azure Application Id
      • Microsoft Azure Client Secret

      These must be filled in with information from your Azure application - see the section on registering your app above

NB: If you are changing an existing Calendar Sync integration from using on-prem Exchange Server to Azure portal, the mailserver url, the delegate user and password information fields can be emptied. We no longer need to save this information. Also the delegate user access can be removed from the user accounts in Azure. From now on, the integration will use the tenant/ application ids and client secret to access mail accounts.