Skip to main content

 

Eptura Knowledge Center

2026 September Eptura Engage Microsoft 365 Integration Release

General availability: September 12, 2026

Platform services release: September 16, 2026

Version: 1.92.0

Updates:

  •  Enhancements and general maintenance

Updates


Enhancements and general maintenance

Enhancements
ID
Description

IN-23579

Improved repair and resynchronization handling for service account bookings - When a booking created without Add to Outlook selected is repaired or resynchronized, the system now recreates the Exchange event as a 👤User as Organizer (UAO) event using the service account, rather than allowing it to revert to a 🏢Room as Organizer (RAO) event. This helps maintain correct synchronization with third-party room screens throughout the booking lifecycle.

Learn more: Service account for User as Organizer events

General maintenance
ID
Description

IN-23747

Unsupported recurring Exchange events are now correctly declined - Recurring events created directly in Exchange by non-subscribed users are not supported by the Microsoft integration and should be automatically declined by Eptura Engage. An issue prevented these events from being declined, leaving unprocessed events in room calendars that could become out of sync. This has been fixed, and unsupported recurring events are now correctly declined.

IN-23659

Resolved incorrect booking status for conflicting multi-room series updates - Fixed an issue where updating a multi-room series to a set of rooms blocked by an existing conflicting series did not correctly set the booking to the declined state. The 'deleteBooking' flag was not being applied, leaving the booking in an ambiguous state rather than correctly reflecting the room conflict.

IN-23553

Resolved incorrect cancellation when updating recurring booking occurrence - Fixed an issue where updating a single occurrence of a recurring series caused the entire booking to be unexpectedly canceled, with users receiving a 'booking operation cannot be completed' cancellation email. The root cause was a booking source mismatch between Engage and Exchange. A recovery mechanism has been introduced to detect and handle this mismatch, allowing the update to complete correctly.

IN-23549

Duplicate notifications causing bookings to be incorrectly deleted are no longer generated - Fixed an issue where duplicate booking creation notifications were incorrectly and simultaneously processed for the same booking, causing the second notification to detect a self-conflict and delete the original booking. Users would see the booking disappear from both Eptura Engage and the room calendar shortly after creating it.

IN-23322

Resolved incorrect host email addresses in resynchronized bookings - Fixed an issue where an incorrect host email address could be stored when the resync endpoint created a single-day, single-room booking for a user who exists in Eptura Engage but not in Exchange.

What's next?


Keep an eye on What's Next to see what we're working on.