2026 May Eptura Engage Microsoft 365 Integration Release
General availability: May 10, 2026
Version: 1.86.0
Updates:
Updates
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. |