Problem solving O365 integration

When it comes to Office 365 integration there can be many reasons why there might be differences between your Outlook resource calendars and Officebooking. In this article, we’ll explore some main causes of calendar mismatches, providing practical tips to diagnose issues.

Checking for errors

Differences in how Exchange Online and Officebooking process meetings may cause calendar discrepancies. To identify these differences, switch between the ‘Office 365’ view, which displays Outlook meetings in blue, and the Officebooking planner view, which shows reservations in red.

Read more about identifying calendar differences in this article. 

To check for errors and possible conflicts go to the Company log. The Company Log provides an overview of all reservations synchronized between Office 365 and Officebooking. It allows you to easily track reservations and identify why a reservation was not processed. You can find the Company Log under Settings in OfficeAdmin, and by selecting ‘Company Log’ from the menu. Here, you can search and filter O365 entries, for example by cancellations or creation date. You can also select a specific date or search for a particular topic

Problem solving

Asset integration filter

If a meeting does not appear to be synchronized correctly, you can check the synchronization status of the connection. Within assets in OfficeAdmin use the integrations filter to find the relevant asset and check its connection status. Each Asset in the list has a status indicator:

• Green: The connection is active and the subscription is working correctly.
• Orange: The connection has been lost and Officebooking is no longer receiving updates.

Check your email adresses

If a resource shows an orange status, edit the corresponding asset and select ‘Subscribe’ in the Microsoft Exchange Integration section. You should then receive a confirmation that the subscription was successful. If an error occurs or if the ‘Subscription failed’ message is displayed, the resource email address is most likely incorrect. You can check the correct address in your Microsoft 365 environment.

In some events, our clients reported a ‘hybrid integration’ where Office 365 is used but AD is on-premise. In that case, there might be some mismatches between the subscribed email address and the address that is actually used for the reservations. For example, you have subscribed ‘meetingroom601@tijdx.nl’ within Officebooking. However, the resource has an alias ‘Norway601@tijdx.nl’ which is used for creating reservations. This can be resolved by entering all aliases in Officebooking admin.

Check token validity in Azure AD

In the event the integration used to be working fine and suddenly stopped working, the token that was registered with the integration might have expired. Check your token validity in Azure AD.