Synchronize absences with your Outlook calendar

Before you get started

First, the feature must be activated on your platform by the Lucca Help desk. Please contact us to request this. This feature is free of charge if you set the parameters yourself, otherwise a service will be offered.

You will then need the following Timmi Absences permissions to be able to configure leave synchronizations: 

  • Configure
  • Manage leave synchronizations
  • Consult leave synchronizations

Timmi Absences lets you synchronize absences in real time with employee Outlook calendars (with Office 365 or Exchange). When an absence is created/approved/deleted in Timmi Absences, it is automatically created/updated/deleted in the employee's calendar. 

Warning: Exchange Server 2010 or 2013 versions are no longer maintained by the publisher and may result in a degraded experience as well as security risks. We recommend upgrading to Microsoft Exchange 2019 or Office 365 before setting up synchronization.

Note: Timmi Absences can also be synchronized with Google Calendar.

In this file you will find: 

Configuration for Office 365 (and Exchange Online with Microsoft account)

For Outlook Office365 synchronization, Timmi Absences uses our Microsoft service application (Azure AD), which you give your administrator consent to access your corporate calendar. This operation must be performed once by the Office 365 account administrator.
  • Access the absence synchronization module in the Timmi Absences application Settings Absence synchronization.
  • Click on "Create a synchronization
  • Choose the establishments where you want to create this absence synchronization
  • Select synchronization type: Exchange
  • Click on "Create a configuration" to confirm
  • On your new configuration panel, click on "Configure".
  • On the configuration page, click on "Grant access rights"
  • Then, in the window that opens, connect to Office 365 with an administrator account (from the Office 365 application) to give Timmi Absences the necessary permissions to access your calendar.
  • Once consent has been granted, the synchronization is updatedand ready to use.
Please note: absence synchronization is not immediate, and it may take several minutes before you can see the absences in your third-party tool. Allow the synchronization to run for a while before returning to the interface to check that the events have been added to your calendar tool.
You can view the permissions you have granted Lucca at any time from Office 365 administration: Admin Azure Active Directory Enterprise applications Timmi Absences - Absence synchronization Permissions

Configuration for Exchange on-premises (hosted on your servers)

For Outlook on-premises synchronization, Timmi Absences relies on a service account, which has read and write access rights to employee calendars.

This is how to create the service account in Exchange Server 2010 or 2013:

  • Start by creating a user (called "SynchroFiggoUser" in this example)
  • Create a custom permission scope (called "SynchroFiggoScope" here):
    New-ManagementScope –Name:SynchroFiggoScope –RecipientRestrictionFilter:{RecipientType -eq "UserMailbox"}
  • Assign the standard impersonation role to the user created for Timmi Absences:
    New-ManagementRoleAssignment –Name:SynchroFiggoAssignment –
    Role:ApplicationImpersonation –User:SynchroFiggoUser –CustomRecipientWriteScope:SynchroFiggoScope 
  • Force update to make associations effective: gpupdate /force

Then in Timmi Absences: 

  • Go to Settings Absence synchronization
  • Click on "Create a synchronization
  • Choose the establishments where you want to create this absence synchronization
  • Select synchronization type: Exchange
  • Click on "Create a configuration" to confirm
  • On your new configuration panel, click on "Configure".
  • Then go to Connection settings on the configuration page
  • Select "Exchange"
  • Next, enter the server URL and the service account username and password (please note that your username and password must be case-sensitive and exactly the same as those entered in the service account) in the settings for the Exchange synchronization ():


The Exchange server URL must be in the format:

You must also ensure that the Lucca webservice IP is authorized to access the server concerned.

Note: synchronization with an Exchange server uses HTTPS and requires a certificate issued by a certification organization. Self-signed certificates are not sufficient.

Enter the various settings for your absence synchronization Click "Apply change" to approve.

Do not click the "Grant access permissions" button, which is used for online authentication, not on-premises

Once this is done, you can go back to the synchronizations list Then click your synchronization insert to go to monitoring

Do not click the "Update calendar access permissions" button, which is also only used for online authentication, not on-premises.

Important: let the synchronization run for a while before trying to find the sent events and checking if they are actually visible on your calendar.

Details of synchronized information

Event label

You can choose to show the type of absence or not (PL, Comp day, Illness etc.) in the event label. By default, labels are hidden (the event displays "Absent").

  • If the setting "Counted as an absence" is checked (=yes) in the Timmi Absences account, the event will appear as Busy in Outlook.
  • If the setting "Counted as an absence" is not checked (=no) in the Timmi Absences account, the event will appear as Free, or "Available" by Microsoft. This is particularly the case with Remote working accounts, for example.

In addition, the synchronization settings can be used to send event labels, which correspond to the name of the account in Timmi Absences:

  • If the setting "Hide labels" = yes in the synchronization settings: Timmi Absences sends the "Absent" label to Outlook, except for Timmi Absences accounts where the setting "public reason" is checked (=yes), where the name of the account as it appears in Timmi Absences is sent.
  • If the "Hide labels" setting = no in the synchronization settings: Timmi Absences always sends the account label to Outlook as it appears in Timmi Absences.

Whole days

For one-day events, you can choose to send them as a "whole day" or a time entry. If you choosethe time entry, Timmi Absences will create an event at the set times.

This corresponds to the "Send whole days as time entries" setting available in your synchronization configuration.

Note: for half days, absences will always be sent as time entries, even if this setting is unchecked in the configuration.


When entering a request pending approval, a provisional type event is created in the calendar. When the request is approved, the event is confirmed.

Batch synchronization of absences

It is possible to force the synchronization of absences already present in Timmi Absences using the Batch synchronization of absences feature available at the bottom of the settings page of your synchronization.

This feature is particularly useful when testing synchronization.

The date field allows you to specify the date from which Timmi Absences should synchronize absences. This allows you to retrieve absences from the last month, for example.

You must choose the establishments for which to synchronize absences. This makes it possible to force synchronization only for certain establishments.

Note: the balance of the "Initialize x events" button is always incremented according to the date entered in the field.
The number of events does not indicate the number of events waiting to be synchronized, but rather the number of events existing after this date.



Frequent problems

When setting up a calendar synchronization, you may encounter the following errors.

  • All events are erroneous: this is usually a server URL (Exchange on-premises) or service account access permissions issue.

  • The events are erroneous for some users: check the email address of the employees in Lucca. It may not be the same as in Office365/Exchange.
    The error code in the logs (by clicking on Detail on the erroneous event) is generally the following one.
  • Absence cancellations are erroneous, with this type of error code:
    Two possible causes.
    • Either the absence was created by an ICS from Timmi Absences notifications, and not by the synchronization module. This is normal when setting up the sync, after 2-3 months the problem should not happen any more.
    • Or the absence has already been deleted from the calendar by the employee.

Page content

Was this article helpful?
5 out of 6 found this helpful