2026 January Eptura Engage Microsoft 365 Integration Release

IN-22002

Monthly recurring meeting date alignment: Fixed an issue where monthly recurring meetings scheduled on the 29th, 30th, or 31st, incorrectly shifted to an earlier date in Eptura Engage after passing through a shorter month (such as February) causing a discrepancy between Eptura Engage and Microsoft Exchange. Subsequent dates are now set according to the originally selected day of the month, and Engage and Exchange are now properly aligned. For example, a recurring booking set on 30th day of the month, is set to February 28 (or 29) and now correctly reverts to the 30th day for the remaining months.

IN-22112

Managed meeting spaces unavailable to book from the add-in: An issue has been resolved where managed meeting spaces were not available for admins to book during the notice period set for the group when using the Eptura Engage Outlook add-in. The same meeting spaces were correctly shown as available from the Eptura Engage web app. Now both platforms correctly show the meeting spaces as available. 

IN-22214

Exchange room mapping now ignores canceled Exchange bookings: Resolved an issue where bookings with a canceled status in Exchange were being pulled into Eptura Engage during the initial sync process that runs when Exchange rooms and Engage resources are mapped. Canceled bookings in Exchange are now filtered out during the initial sync process.

Learn more: Exchange room mapping

IN-22065

Recurring series stability: Resolved an issue where certain updates to a recurring series in Microsoft Exchange, caused some instances to be unexpectedly removed from Eptura Engage. Changes to a recurring series now correctly preserve all instances across both platforms.

IN-22055

Synchronizing out-of-sync bookings: When synchronizing out-of-sync bookings, some bookings failed due to an incorrect user subscription verification. This has been fixed, and valid user subscriptions are now correctly recognized during the process.

IN-22000

Invalid room ID handling when synchronizing recurring bookings: Resolved an intermittent failure when synchronizing recurring bookings, caused by invalid room reference data. These scenarios are now gracefully handled, ensuring bookings are synchronized correctly without manual intervention.

IN-21857

IN-21804

Improved reconciliation of out-of-sync bookings: Issues have been fixed that affected the reconciliation of out-of-sync bookings. Existing booking data is now correctly handled and recurring series updates are properly validated, ensuring a reliable synchronization between Eptura Engage and Microsoft Exchange calendars.

IN-22203

Synchronizing recurring series with exceptions: During the initial sync process that runs when Exchange rooms and Engage resources are mapped, recurring bookings were not imported from Microsoft Exchange when all instances in the series had been modified (exceptions). This is now fixed and recurring bookings synchronize to Eptura Engage, regardless of how many instances have been individually updated.

IN-22133

Improved conflict detection in Readiness Report: Fixed an issue where the Readiness Report was not capturing conflict data for overlapping multi-room bookings in certain scenarios. The report now correctly identifies and displays conflicts for all rooms involved in both single-day and recurring series bookings.

Learn more: Exchange room mapping and the Readiness check

IN-22089

Daylight Saving Time (DST) handling during initial synchronization: Resolved a time zone handling issue where a recurring series that was created before the Exchange room mapping process was run, appeared with a one-hour offset in Eptura Engage after the initial synchronization. Bookings that cross DST transitions now synchronize with the correct times.

IN-22086

IN-21991

Improved synchronization for bookings containing mapped and unmapped rooms: Fixed an issue where multi-room bookings containing both mapped and unmapped Exchange rooms, failed to synchronize to Microsoft Exchange when the unmapped room was listed first. All mapped rooms in a booking now synchronize correctly, regardless of their position in the room list.

IN-22075

Improved handling of bulk booking notifications: Resolved an issue where batch booking notifications (such as bumped bookings) stopped processing after encountering a validation failure. The system now continues to process all remaining bookings in the batch.

IN-21823

Setup/clean-down conflict handling during initial synchronization: Fixed an issue where recurring bookings were declined for the entire series, when only individual instances conflicted with the setup or clean-down times for a resource. The system now correctly declines only the conflicting instances, while keeping the remaining occurrences booked.

IN-21788

Updating title and time of a recurring booking: The first instance of recurring booking was incorrectly deleted when the title and time were updated for the series in Eptura Engage. This has been fixed and now the series is correctly preserved in both Eptura Engage and MIcrosoft Exchange when the title and time are updated for the series.

IN-21199

Series deletion now correctly removes instances with exceptions: Fixed an issue where recurring instances with exceptions (time changes) were not deleted from Microsoft Exchange when the series was removed from Eptura Engage with the 'Also delete from Outlook calendar' option selected. Instances with exceptions are now correctly deleted from both platforms.

IN-21953

Only future instances counted by the Readiness report: Fixed an issue where the readiness report incorrectly flagged recurring series' starting in the past as exceeding the 450-instance limit. Now only instances in the future are calculated when determining compatibility, preventing false conflict reports for valid bookings.

Learn more: Exchange room mapping and the Readiness check