Skip to main content

 

Eptura Knowledge Center

2025 December Eptura Engage Microsoft 365 Integration Release

  1. Last updated
  2. Save as PDF

Product: Eptura Engage Microsoft 365 Integration

General availability: December 14, 2025

Updates:

Updates

Room mapping in-progress check

We've added a check that prevents another room mapping process from being started when an existing room mapping and synchronization is already in progress. The 'Map' buttons are disabled until the existing process is complete.

Learn more: Exchange room mapping

Enhancements and general maintenance

General maintenance
ID
Description
IN-21873

Exchange room mapping and the readiness check: An issue has been fixed in which the Readiness check (that identifies conflicts during the Exchange room mapping process) failed to detect any conflicts for a recurring series that had a start date in the past.

Learn more: The readiness check
IN-21084

Moving recurring bookings: We fixed an issue that caused multiple instances to be created on the same day, when a recurring booking was moved and some instances of the series conflicted with existing bookings.

Learn more: Moving appointments
IN-21331 Multi-room bookings: When adding an additional meeting space to an existing booking that was created in Eptura Engage, the original meeting space would sometimes be removed from the booking, leaving only the newly added space. This issue has been resolved - both the original and newly added meeting spaces are now retained, accurately reflecting a multi-room booking.
IN-21704

Faster load times for the Eptura Engage Outlook add-in: The caching policies of the Eptura Engage Outlook add-in have been adjusted to improve performance when the add-in is loaded. 

Learn more: Eptura Engage Outlook add-in for Microsoft 365
IN-21842 Extending booking durations: We fixed an issue where extending the duration of an existing booking in Eptura Engage did not update the corresponding Exchange event. The event now reflects the updated duration accurately.
IN-21963 Rescheduling recurring bookings: We fixed an issue where moving the first instance of a recurring series to a date earlier than the original start date, caused the booking to fall out of sync with the corresponding Exchange event.