Skip to main content

 

Eptura Knowledge Center

2026 June Eptura Engage Microsoft 365 Integration Release

General availability: June 21, 2026

Version: 1.88

Updates:

Updates


Enhancements and general maintenance

Enhancements
ID
Description

IN-23182

Exchange room mapping - Admins can now stop the calendar sync for a mapped room without removing its mapping history. The 'Unmap' button on the Exchange room mapping dashboard has been renamed Stop Sync to better reflect its function. Stopping a sync grays out the room and meeting space resource on the mapping page and preserves the room-to-space mapping for re-activation* later, without the room or meeting space reappearing in the unmapped list. 

*Contact Eptura Support to reactivate a room and resource that has been stopped.

General maintenance
ID
Description

IN-23153

Fix for multi-room booking deletion not removing all Exchange calendar entries - Fixed an issue where deleting a multi-room booking that included both mapped and unmapped rooms did not remove all corresponding meetings from Exchange calendars. Only the mapped room calendar was updated, leaving orphaned entries in unmapped room calendars.

IN-22986

Fix for intermittent booking conflicts in Exchange when updating bookings - Fixed an issue where bookings were intermittently cancelled and marked as conflicts in Exchange when users made updates via the web app, such as adding catering or notes. Concurrent sync notifications were processed simultaneously, causing a duplicate notification to incorrectly detect a conflict against the booking already created by the initial sync.

IN-22855

Fix for room decline emails sent after booking end time - Fixed an issue where users were receiving a room decline notification email after their booking had already ended. The system now checks whether a booking is in the past before making any update to Exchange, preventing late-triggered notifications from being sent.

IN-22769

Fix for non-Exchange rooms being removed from recurring Outlook series - Fixed an issue where non-Exchange rooms were being silently removed from the location field of an Outlook recurring series without any user action. This was caused by an invalid recurrence end date, which led the system to incorrectly process the series and strip non-Exchange room location data.