2026 March Eptura Engage Microsoft 365 Integration Release
General availability: March 29, 2026
Version: 1.84.0
Updates:
General availability: March 8, 2026
Version: 1.83.0
Updates:
- Improved detection and behavior when an instance of a recurring booking is declined by Exchange
- Improved exception handling for multi‑room recurring booking sync
- Room availability check for single-day, multi-room bookings
- Past bookings rescheduled to dates in the future now correctly synchronize
- Exchange Room Mapping now supports multiple room selection across multiple pages
- General maintenance
Updates
General availability: March 29, 2026
Version: 1.84.0
What's new
New 'Add Services' button in the Outlook add-in when editing bookings
When editing a booking from the Eptura Engage Outlook add-in, you can now launch the booking form in the Eptura Engage web app directly from the add-in via the new Add Services button, to add services to your booking.
Previously, adding services to a booking created using the Outlook add-in, required the user to launch the booking form via the 'Add Services' link in the services email notification that is sent when bookings are created via the add-in. If preferred, this services email can now be disabled.
Enable or disable the Services email notification
We've added a new global setting that allows admins to decide whether services notification emails are sent when a booking is made through the Eptura Engage Outlook add-in. With the new 'Add Services' button available when editing a booking directly from the add-in, some customers might find the services email unnecessary.
Enhancements
Detection and behavior when Exchange declines a booking
The previous two product releases included improved detection and behavior when Microsoft Exchange declined bookings due to conflicts. Initially, these enhancements were hidden and not available by default. We have now properly released this enhancement and the following actions are now taken by default when Exchange declines either a single-day booking or an instance of a recurring booking:
- If the Eptura Engage resource is available but the Exchange room is not, the booking is removed from both platforms.
- If both the Exchange room and Eptura Engage resource are unavailable, an alternate resource is assigned (if available) and synchronized with the associated Exchange room.
In both cases, the user's calendar is updated to reflect the correct booking status.
This enhancement only supports single-room bookings.
Room availability check for invited rooms in multi-room series bookings
When creating or updating a recurring series in Eptura Engage that includes multiple rooms, Eptura Engage now checks whether each invited room is available before confirming. Unavailable rooms are handled gracefully - they are removed from the booking without affecting the rest of the series, attendees, or booking detail.
General maintenance
ID |
Description |
|
IN-22433 |
To prevent issues with existing bookings, unsubscribed users who already have Eptura Engage bookings are now prevented from subscribing: When Eptura Engage detects an invite to an Exchange room calendar from a user's calendar that is not yet subscribed, it will now check for existing bookings in Engage before automatically creating a subscription to that user's calendar. If existing bookings are found, the user's calendar is not subscribed - the booking is created in Eptura Engage using the default Admin account. |
|
IN-22540 |
Duplicate email notifications are no longer sent to attendees of recurring bookings: When a recurring event was created or updated in Exchange, attendees were receiving duplicate invitations due to unnecessary calendar patch calls. This issue has now been resolved by suppressing these redundant actions, ensuring attendees receive only the correct, intended notifications. |
|
IN-22503 |
Managed meeting space bookings no longer revert to 'pending' after approval: When a request for a managed meeting space was approved, the booking status intermittently reverted from 'confirmed' to 'Pending on grid'. The issue is now resolved and confirmed bookings now retain the expected status. |
|
IN-20660 |
Outlook event titles containing a plus sign ( + ) now correctly synchronize to Eptura Engage: When an event created in Microsoft Outlook included a plus sign ( + ) in the title, and a meeting space was booked using the Eptura Engage Outlook add‑in, the plus sign was previously converted to a space when the booking synchronized to Eptura Engage. This issue has now been resolved, and booking titles in Eptura Engage are preserved exactly as entered in the original Outlook event. |
|
IN-22734 |
Recurring events spanning midnight now synchronize correctly across all timezones: When a recurring series was created in Exchange with an end time that crossed over midnight (for example, 7:00pm to 9:00pm) in a timezone behind UTC, only a single instance was created in Eptura Engage instead of the full recurring series. This affected daily, weekly, and monthly recurring series'. All instances in a recurring series now synchronize correctly regardless of end time. |
|
IN-22673 |
First occurrence exceptions no longer removed when rooms are added to entire series from Eptura Engage: When the first occurrence of a recurring series had been modified in Exchange - creating an exception instance - and a room was subsequently added to the full recurring series from Eptura Engage, the first occurrence was incorrectly deleted from Exchange. This has now been resolved and the exception instance is preserved correctly when room changes are applied to the entire series. |
|
IN-22601 |
'Smart alternatives' now correctly assigns rooms for conflicting single-instance updates in multi-room series: When a single instance of a multi‑room recurring series was updated to a time slot that conflicted with an existing booking, the booked rooms were removed from both Exchange and Eptura Engage, and no alternate space was booked - resulting in an 'unable to complete' notification for users. This issue has now been resolved and Smart Alternatives now triggers correctly in this scenario, ensuring an available room is automatically booked. |
|
IN-22597 IN-22598 IN-22721 |
Deleting a recurring series or a modified series instance from Eptura Engage now correctly removes all associated rooms from Exchange: When a room had been added to or changed for a specific instance of a recurring series, deleting that instance - or the full series - from Eptura Engage was leaving the rooms behind in the Exchange room calendar. This has been resolved and all associated rooms are now removed from Exchange correctly on deletion. |
|
IN-22361 |
Exception instances after series‑level room updates are now correctly shown in the Outlook add-in and synchronized to Eptura Engage: Previously, when an instance of a single or multi-room recurring booking was deleted in Eptura Engage (creating an exception instance in Exchange) and a room was later added to the entire series in Exchange, the exception instance was not being created in Eptura Engage, nor did the associated meeting space appear in the Outlook add‑in as expected. This issue has now been resolved. |
|
IN-22292 |
Previously conflicting series instances are now correctly assigned rooms in Exchange: When a booking existed in Exchange which had not previously synchronized to Eptura Engage, and a user created a recurring series in Eptura Engage that conflicted with the unsynchronized Exchange booking, only the instances that did not conflict with the existing Exchange booking synchronized correctly - the recurring series was created in Exchange but the room was removed from the conflicting dates and the associated Eptura Engage instances. Then, if an update was made to the series in Exchange - such as a change of time or title - Eptura Engage correctly recreated all instances and booked the meeting space for all dates, however, the associated room was not added to the previously conflicting instances in Exchange. This issue has now been resolved, and both Exchange and Eptura Engage are correctly synchronized. |
Updates
General availability: March 8, 2026
Version: 1.83.0
Enhancements
Improved detection and behavior when an instance of a recurring booking is declined by Exchange
Last month, we released an update that improved the detection and behavior when Microsoft Exchange declined a single-day (single-room) booking due to a conflict. This enhancement now supports recurring bookings.
When Exchange declines a single-day booking or an instance of a recurring booking, the following action is taken:
- If the Eptura Engage resource is available but the Exchange room is not, the booking is removed from both platforms.
- If both the Exchange room and Eptura Engage resource are unavailable, an alternate resource is assigned (if available) and synchronized with the associated Exchange room.
In both cases, the user's calendar is updated to reflect the correct booking status.
This update supports single-room bookings only.
Improved exception handling for multi‑room recurring booking sync
Multi-room recurring bookings with exceptions now synchronize more accurately from Eptura Engage to Microsoft Exchange. For example, if an instance has been deleted or a meeting space resource removed from a specific occurrence, Exchange now correctly reflects those changes - deleted occurrences no longer reappear in Exchange, and any resources removed from individual instances, are now correctly reflected.
Room availability check for single-day, multi-room bookings
When a multi-room booking is created or updated in Eptura Engage and 'Add to Outlook calendar' is enabled, Eptura Engage now checks if each each room is available in Microsoft Exchange before confirming the booking. The following behavior is observed:
- Some rooms are unavailable: Unavailable rooms are quietly removed from both Eptura Engage and Microsoft Exchange. The booking/event is confirmed for the available rooms.
- New booking - no rooms available: The event is created in the Outlook calendar but no rooms are assigned.
- Updated booking - no rooms available: All rooms are removed from Eptura Engage and Microsoft Exchange, but event details, such as title, time, and attendees, are updated in the calendar.
- Adding or swapping a room: If the new room isn't available, it simply will not be added; existing rooms and event details are unaffected.
This update ensures single-day multi-room bookings no longer fail or conflict - Eptura Engage handles the conflicts automatically and keeps the Outlook calendar accurate.
Past bookings rescheduled to dates in the future now correctly synchronize
When a Microsoft Exchange event that was previously synchronized with Eptura Engage, is moved from a date in the past to a date in the future, the update now synchronizes correctly to Eptura Engage. Previously, the system skipped such changes, leaving the event visible in Exchange but not in Eptura Engage. This fix applies to both single-day and recurring series bookings, with either single or multiple rooms. Conflict handling is supported where an alternate resource is assigned if needed.
Exchange Room Mapping now supports multiple room selection across multiple pages
When mapping Exchange rooms in bulk from the Exchange Room Mapping module, admins can now select multiple rooms across multiple pages. The following improvements have been made to the unmapped rooms table:
- Persistent selection: Rooms selected on one page remain selected when navigating to another page.
- Search and filter support: Selections are preserved when using the search and filter functionality.
- Selection counter: A real-time counter displays how many rooms are selected - for example, '3 of 10 spaces selected'.
- Maximum limit indicator: The real-time counter turns orange when the selection limit is reached, and further selections are blocked.
General maintenance
ID |
Description |
|
IN-22358 |
Multi-room recurring meeting updates now sync correctly to Exchange: Fixed an issue where removing or editing a resource in a recurring multi-room booking in Eptura Engage was not reflected in Exchange. Updates now synchronize correctly for new bookings. |
|
IN-21982 |
Rooms no longer send decline emails after an event ends: Fixed an issue where the Exchange room mailbox sent a decline email after an event had finished for bookings made through the Eptura Engage Outlook Add-in. The issue was caused by a case-sensitive mismatch between the room's email address in Eptura Engage and Microsoft Exchange. This has been corrected and users will no longer receive unexpected decline notifications when their event concludes. |
|
IN-22601 |
Series instance conflicts now correctly trigger alternate meeting space assignment: Fixed an issue where moving a single instance of a multi-room recurring series to a conflicting time slot resulted in rooms and resources being removed from Microsoft Exchange and Eptura Engage respectively, with no alternate assigned. The 'smart alternatives' technology that books an alternate meeting space in this scenario, is now correctly triggered. |
|
IN-22602 |
Readiness report missing data for bookings with more than 8 rooms: Fixed an issue where bookings created with more than 8 rooms were not appearing in the Readiness report. Conflict data for these bookings is now generated and included in the report. |
|
IN-22544 |
Recurring series converted to single-day event in Exchange now syncs correctly: Fixed an issue where converting a recurring series to a single-day event in Microsoft Exchange caused both the Exchange event and Eptura Engage booking to be deleted. The event now correctly updates to a single occurrence and is preserved in both systems. |
|
IN-22515 |
Deleting a recurring series now removes exception instances from the Exchange room calendar: Fixed an issue where deleting an entire recurring series from Eptura Engage left exception instances behind in the Exchange room calendar. Now, all instances, including room-change exceptions, are correctly removed from Exchange when a series is deleted. |
|
IN-22495 |
Exchange Room Mapping page refreshes correctly after switching to a different tenant: Fixed an issue where Exchange rooms failed to appear after switching to a different tenant on the Exchange Room Mapping page. Rooms now load correctly for each tenant every time the selection is changed, without requiring a manual cache refresh. |
|
IN-22408 |
Fix for missing instances of a recurrence during initial sync process when exceptions exist: Fixed an issue where some instances of a recurring series, failed to synchronize to the Eptura Engage booking during the initial sync process, when an exception had been created before the room and resource were mapped. Now, all instances, including those with date or time changes, synchronize correctly across daily, weekly, and monthly series. |
|
IN-22366 |
Single-instance booking conflicts are now flagged by the Exchange Room Mapping readiness check: Resolved an issue where conflicts caused by a single-day Eptura Engage booking overlapping with a recurring Microsoft Exchange series, were not flagged by the readiness check that runs prior to rooms and resources being mapped from the Exchange Room Mapping module. The Exchange room and Eptura Engage resource is no longer mapped if this scenario exists. The conflict is flagged in the Readiness Report and mapping is prevented until resolved. |
|
IN-22096 |
Reliable alternate meeting space assignment for large recurring series: Resolved an issue where a Graph API timeout during alternate meeting space assignment resulted in the resource being booked in Eptura Engage but not updated in Microsoft Exchange, causing an out-of-sync state. Processing is now more reliable for series with a high number of conflicting instances. |
|
IN-22044 |
Daylight Saving Time (DST) recurring series times stay intact after update: Resolved an issue where deleting an instance from a recurring series that fell on a non-DST date, and then updating the series, caused the booking time of the remaining instances to shift unexpectedly. The fix ensures that an update does not modify the booking time under any circumstances. |
|
IN-22006 |
Bookings deleted from Eptura Engage are now recreated correctly when updated from Microsoft Exchange: Fixed an issue where updating a booking in Exchange that had already been deleted from Eptura Engage resulted in a synchronization failure. The system now detects the missing booking and recreates it in Eptura Engage, keeping both systems in sync. Applies to single-day, recurring series, and multi-room bookings. |
|
IN-21324 |
Converting a series to a single-day booking in Eptura Engage now syncs correctly to Microsoft Exchange: Resolved an issue where converting a recurring series to a single-day booking in Eptura Engage failed to update the corresponding Microsoft Exchange event, leaving the full recurring pattern intact. Changes now synchronize correctly in both directions for single and multi-room bookings. |
