2026 May Eptura Engage Microsoft 365 Integration Release
General availability: May 10, 2026
Version: 1.86.0
Updates:
Updates
General availability: May 31, 2026
Version: 1.87.0
Enhancements and general maintenance
Enhancements
ID |
Description |
|
IN-22440 / IN-22441 / IN-22442 |
Individual room tracking for declined occurrences - For recurring bookings with multiple mapped rooms, the system now tracks decline statuses at the individual room and instance level. When a series is created, updated, or a single occurrence is modified, each room is evaluated independently. If Exchange declines a room for a specific occurrence, the system reflects this accurately in Engage - either by assigning an alternative or marking the room as declined - without impacting other rooms or instances in the series.
|
|
IN-22975 |
Conflicts with overlapping setup or clean-down buffers in recurring bookings now flagged in readiness report - Series bookings that conflict due to overlapping setup or clean-down buffers are now correctly identified in the readiness report. Previously, these conflicts were not flagged, which could allow issues to go unnoticed before room mapping. |
General maintenance
ID |
Description |
|
IN-22878 |
Multi-room recurring booking conflicts now handled per instance - Fixed an issue in multi-room recurring bookings which caused all rooms to be removed from the entire series and an exception to be logged when the series time was updated, which conflicted with all the rooms on a single instance. Conflicts are now handled at the individual instance level, ensuring only the affected occurrence is impacted. |
|
IN-22864 |
Placeholder series fix: Microsoft fixed an issue with 'placeholder series'* bookings where adding a second room to the whole series caused the first room to be unexpectedly removed from the attendee list, leaving the event with only the newly added room. |
|
IN-22677 |
Fix for rooms being removed after updating placeholder series bookings - When a room was added to an individual instance of a recurring event that previously did not have a room added, and then another room was added to the full series (creating a 'placeholder series'*), updating the booking for the series in Eptura Engage caused the room added at the series level to be removed from the calendar for instances that were previously exceptions or for the entire series, depending on the changes made. This has been fixed. |
|
IN-21817 |
Deletions of single-room bookings now reliably synced to Exchange - Fixed an intermittent issue where deleting a single-room, single-day booking in Eptura Engage was not consistently reflected in the Exchange room calendar. A retry mechanism has been introduced to handle cases where booking data is not yet available when the delete event is first processed, ensuring the change is successfully synced.
|
|
IN-21369 |
Final instance exceptions now synced during initial sync - Fixed an issue during the initial synchronization process where an exception created on the last instance of a recurring booking was not synced to the Exchange room calendar, leaving the 'IsSynced' flag set to false and the instance permanently out of sync. This has been resolved to ensure all instances, including the final occurrence, are correctly synchronized. |
*A placeholder series describes a recurring Microsoft event that was initially created without a room, and a room is later added to a single instance (creating an exception in Exchange and a single booking in Eptura Engage), and then a second room is added to the entire series. Engage creates a recurring booking for the new room while retaining the original single booking as an exception.
Updates
General availability: May 10, 2026
Version: 1.86.0
Exchange room mapping - queued room processing
You can now submit any number of room mapping requests at the same time, allowing all Exchange room and Eptura Engage resource pairings to be submitted for mapping in a single action. Previously, only 10 pairings could be submitted at a time and admins had to wait for each batch to complete before submitting more. Now, mapping requests are automatically processed in batches, with any requests above the batch limit queued and completed in the background.
The Exchange Mapping module has also been refreshed to show three new filter buttons - Unmapped, Queued, and Mapped - replacing the previous 'Unassigned spaces' and 'Mapped spaces' radio buttons. The Queued tab shows which rooms are waiting to be processed and their current queue status, giving admins full visibility over large-scale mapping operations at a glance.
Learn more: Exchange room mapping
Enhancements and general maintenance
Enhancements
ID |
Description |
|
IN-22888 |
Managed room request notifications - Room resource admins now receive an email notification when a booking request is made for a managed room via the Eptura Engage Outlook add-in. This allows admins to log into Eptura Engage web app to approve or reject the request without having to monitor the dashboard. Notifications are sent per managed room and respect auto-approve settings defined for the group. These notifications are suppressed during the initial synchronization process that runs when rooms and resources are mapped. Managed room request notifications are disabled by default - to enable the option for your organization, contact support. |
|
IN-22982 |
Exchange event IDs are now created only when bookings are completed - The Eptura Engage Outlook add-in no longer generates an Exchange Event ID when it is launched. The ID is now only created when the user actively clicks the Book button. This prevents orphaned or unintended calendar events from appearing in a user's Outlook calendar when they open the add-in but close the appointment without completing a booking. |
General maintenance
ID |
Description |
|
IN-22986 |
Booking updates via the booking grid no longer cause unintended cancellations - Fixed an issue where a booking was intermittently canceled and removed from both Eptura Engage and Microsoft Exchange when a user performed an update via the Eptura Engage booking grid - such as extending the booking duration, or changing the meeting space using drag and drop on the grid. The cancellation was caused by concurrent sync notifications being processed simultaneously, where the second notification incorrectly detected a conflict against the booking already created by the first, triggering an unintended deletion. |
|
IN-22959 |
Duplicate recurrence entries created when extending recurring bookings - Fixed an issue where extending the end date of a recurring booking multiple times resulted in duplicate recurrence entries in Eptura Engage. The old recurrence was not being cleaned up correctly on the second and subsequent extensions, causing orphaned bookings to persist alongside the updated series. |
|
IN-22943 |
Booking updates now fully sync to Exchange when the room is unavailable - When a booking in Eptura Engage is updated and the requested Exchange room is unavailable, all other changes - including the booking title, time, and attendees - are now applied correctly in Exchange. Previously, only the room removal was processed, leaving the rest of the booking details out of sync.
|
|
IN-21007 |
Missing room decline notifications when inviting more than eight rooms - Fixed an issue where room decline notifications were not sent by Exchange when more than eight mapped Exchange rooms were invited. Users were not informed that their booking could not be fulfilled, leaving rooms in an inconsistent state. |