Microsoft 365 offers a different and often smaller set of functionality and business rules for room booking than Condeco. This means there are a number of limitations to Condeco functionality when using Exchange Sync.
Condeco Outlook Com+ plug-in
The Condeco Outlook Com+ plug-in enables users to search for rooms from the appointment window in Microsoft Outlook. Exchange Sync is compatible with the Condeco Outlook Com+ plug-in 6.4 and above, however, bookings that were made directly via Microsoft 365 (by inviting the room to the meeting) can be seen via the Room Grid option but cannot be opened or edited via the plug-in.
The Condeco Mobile Room Booking App enables users to make bookings in Condeco (Condeco-initiated bookings). However, you cannot edit bookings that were created in Microsoft 365 directly in the app because Condeco cannot make changes to the calendar appointment they originated from. It is possible however to edit those appointments using the phone calendar.
Setup and clear-down times
As Microsoft 365 does not have a notion of setup and clear-down times, Condeco will not enforce any setup and clear-down times for synchronized bookings. When an Exchange room is mapped to a Condeco room, any pre-defined setup time/clear-down time is removed.
Deleting historical bookings
Historical bookings cannot be deleted from Condeco. If a historical booking is deleted from the Microsoft 365 calendar, it will remain in Condeco.
As Microsoft 365 has no concept of linked rooms, they are not supported by Exchange Sync and should not be set up in Condeco.
We do not recommend applying business hours to synchronized rooms unless they are also applied to the corresponding resource calendar in Microsoft 365. Condeco cancels bookings outside business hours upon synchronization with Microsoft 365 which may result in a disrupted user experience if the business hours do not match.
Advanced booking period
Exchange Sync does not consider any advance booking period when creating bookings originating from Microsoft 365 because this functionality is driven by the Microsoft 365 room policy. Any advance booking period must be the same in both systems. Cancellation rules are not supported.
Advance booking rules
Condeco ignores advance booking rules when working in synchronization with Microsoft 365. Microsoft 365 does not provide any advance booking rules. The default rules will apply.
Microsoft 365 does not provide a booking type so Microsoft 365-initiated bookings will default to the booking type configured in the Condeco group that the room belongs to. If no default is available, none will be selected.
Condeco does not support unlimited recurrences. If a room is booked in Microsoft 365 with an unlimited recurrence, Condeco cancels the booking and sends an email to the user advising that an end date must be set for the recurrence. The user will need to re-book the room.
Both Microsoft 365 and Condeco support a limit to the number of instances in a series and we recommend setting both limits to the same value.
Specific recurrence patterns are not supported by Exchange Sync.
Series – past occurrences
Condeco does not support the editing of past bookings so, in scenarios where instances are in the past and a meeting is updated to a new time in Microsoft 365, Exchange Sync will create a new series in the new slot but will not delete any past bookings.
Condeco waitlist functionality is not supported.
Condeco Smart Recurrences are bookings where a substitute room is offered for dates if the specified room is not available. Smart recurrences in Condeco are not available for Exchange Sync-enabled rooms.
User access in Condeco, such as whether rooms are self-bookable or they need to be requested, is governed by Condeco group settings. User access in external calendars is governed by Active Directory groups. We recommend creating AD groups that mirror the rules applied to the Condeco groups to ensure the access can be reproduced.
Managed rooms are not currently supported in Exchange Sync.
Notice period for managed rooms
We do not recommend using notice periods as Microsoft 365 will not enforce them.
Mapped rooms synchronization
When new Exchange rooms are added to Microsoft 365, it may take up to 24 hours to reflect on the Room Mapping page in Condeco.
Deleting a room
When a room is deleted from an Microsoft 365-initiated booking, Condeco will clear the slot on the room calendar and notify the organizer that the booking has been deleted in Condeco. Exchange Sync does not have access to the organizer’s calendar so the original meeting request will still include the invited room. This is problematic if the organizer updates the meeting in Microsoft 365, as a new room request will be generated which means the room booking will be created again (if the slot is available) and synchronized back to Condeco.
When a meeting is created in Microsoft 365 and multiple rooms are added, Exchange Sync books all the rooms in Condeco and links them as a single booking (conference). The room that was added first is considered the primary room and all the rest are considered secondary. Condeco booking workflows are dependent on the primary room.
Microsoft 365 has no concept of primary and secondary rooms so the rooms have no real attachment to each other, aside from both being invited to the same meeting. If the meeting is moved to a different time, Microsoft 365 sends a separate notification for each room to Exchange Sync. As soon as Condeco receives the first notification for either a primary or secondary room in a conference booking, it will action the changes for all rooms in the conference booking. This eliminates out-of-sync issues if one of the rooms is not available at the new time, for example. The following notifications are still processed but the updates have already been done.
Microsoft 365 does not save the exception that is generated when a change is made in a recurrence series. However, Condeco maintains the exception every time it is generated in Microsoft 365 and is synchronized using Exchange Sync. This behavioral inconsistency can lead to out-of-sync issues when, for example, a user edits a single instance of a recurrence booking in Microsoft 365. The modified instance is considered as an exception but the series cannot be updated because Microsoft 365 does not support the behavior. Condeco creates a separate booking for the new series that is created in Microsoft 365 and does not overwrite the previous booking.
In previous versions, this could lead to out-of-sync errors, however, in Exchange Sync, the chances of this are significantly reduced due to an improved exception handler.
Microsoft 365 does not have an equivalent feature for Condeco services so when a booking with services is edited in Microsoft 365, the booking will be declined if a service item is no longer available. For example, a lunch service may not available at the new meeting time.
No support for multiple Microsoft 365 aliases on a single mailbox.
Exchange Sync does not support multiple Microsoft 365 aliases on a single mailbox mapped to a single room in Condeco. Furthermore, it also does not support multiple aliases on a mailbox that are mapped to different rooms in Condeco. If such aliases exist, it may result in missed bookings in Condeco or overlapping bookings in Microsoft 365.
Need more help with this?