Skip to main content

 

Eptura Knowledge Center

2026 February Eptura Engage Microsoft 365 Integration Release

  1. Last updated
  2. Save as PDF

General availability: February 15, 2026

Updates:

Updates

Improved detection and behavior when bookings are declined by Exchange

We've improved the detection and behavior when Exchange declines a booking due to a conflict - either during regular synchronization when a resource is booked, or during the initial synchronization process that runs when Exchange rooms and Eptura Engage resources are mapped. 

When Exchange declines a booking, the following action is now 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 relates to single-day, single-room bookings, and helps to ensure such bookings stay aligned between Exchange and Eptura Engage without manual intervention.

Improved conflict detection recorded in the Readiness report

The Readiness report - which provides details for each conflicting or incompatible event and booking when mapping Exchange rooms and Eptura Engage resources - now provides more comprehensive insights:

  • All-day events in Exchange rooms are flagged as incompatible since they cannot be synchronized with Eptura Engage.
  • Conflict detection during the initial synchronization process that runs when Exchange rooms and Eptura Engage resources are mapped, now considers the setup and clean-down times configured for Eptura Engage resources. If the time of an event overlaps with the configured setup or clean-down period, this is now flagged in the Readiness report.

These improvements help identify potential synchronization issues and allow admins to take corrective action before the room and resource are mapped.

General maintenance

ID
Description
IN-21793

Multi-room booking time zone inconsistency: Fixed an issue where updating multi‑room bookings - containing rooms in different time zones - via an email deep link (such as one used to add services to a booking) caused an incorrect time‑zone adjustment on the Exchange event, while the Eptura Engage booking remained unchanged. Booking times now remain consistent across both platforms when updated through deep links, regardless of time zone differences. 
IN-22285

Incomplete series deletion for bookings with exceptions: Fixed an issue where deleting an entire recurring series from the Exchange room calendar did not remove instances with exceptions from Eptura Engage. All instances, including those with modifications, are now correctly deleted when the full series is removed.
IN-22372 Modifying multi-room exception Instances incorrectly removed rooms: Fixed an issue where updating a recurring series from Eptura Engage (title or resource changes) incorrectly removed rooms from instances with exceptions in Exchange. Rooms added to individual instances now remain intact when the series is updated, and bookings remain on the room calendar as expected.
IN-22130 Re-sync failure when updated recurring date range extends beyond original end date: Fixed an issue where bookings failed to re-synchronize when the last instance of a recurring series was rescheduled beyond the original end date for the series. Rescheduled instances now synchronize correctly, regardless of whether they fall outside of the original date range.
IN-22087 Conflicting bookings not deleted when created by new users: Resolved an issue where bookings created by newly added users were not deleted from Eptura Engage when a conflict was detected in the Exchange room calendar. Conflicting bookings are now correctly removed, regardless of when the user was created.