2025 July Eptura Engage Microsoft 365 Integration Release
Product: Eptura Engage Microsoft 365 Integration
General availability: July 19, 2025
Updates:
Product: Eptura Engage Microsoft 365 Integration
General availability: July 6, 2025
Updates:
Updates
General availability: July 19, 2025
Synchronization improvements
We have implemented a number of improvements to help with synchronization issues that some customers are experiencing.
- In some cases, Microsoft Outlook failed to provide the Eptura Engage Outlook add-in with the correct Event ID. We have implemented a retry mechanism to help ensure that if it fails on the first attempt, it can try again.
- Improved handling of apostrophes ( ' ) in the meeting title, to help prevent errors when storing booking data.
- Improvements to the performance of the processing of Graph notifications, by filtering out unrequired events.
- Fixed live-site logging exceptions that might cause booking synchronization issues.
Enhancements and general maintenance
General maintenance
ID |
Description |
|---|---|
|
IN-20778 IN-20848 |
Booking data currently in a save operation to the database, might cause a read issue when it is being processed by an Exchange event at the same time, which can lead to an out of sync booking. Handling has been introduced to manage this condition. |
|
IN-20978 |
We resolved an issue that caused An Exchange room email address to sometimes be incorrectly removed from an appointment created by a delegate. |
|
IN-20982 |
When the time of a recurring booking was extended which conflicted with some of the instances in the series, an alternative meeting space was incorrectly assigned to the entire recurring series, causing multiple spaces to be added on the conflicted dates. This has been fixed. |
|
IN-21059 |
An alternative meeting space was not booked when a meeting space with a conflict was added to a existing (placeholder) booking. This has been fixed. |
|
IN-20969 |
When an administrator rejected a single meeting space from one instance of a multi-room recurring meeting, all meetings spaces from the instance were canceled. This has been fixed. |
Updates
General availability: July 6, 2025
Enhanced support for Exchange room invites
We now support Exchange room invites from external users and from accounts with calendars that cannot be subscribed to Eptura Engage. In such cases, bookings are created using the default admin account.
Support for Exchange room invites from external users
In some organizations, Exchange resources are set to allow meeting invitations from people outside their Exchange. A common use of this is to support forwarding an invite from an external person to an Exchange room. By default, this setting is turned off for Exchange calendars, so must be enabled in Exchange before it can be supported by Eptura Engage.
As people outside your organization do not have user accounts in Eptura Engage, the booking is created by the default admin account.
Support for Exchange room invites from non-subscribed user calendars
There might be scenarios where an invite to an Exchange room is created by an account whose calendar cannot be subscribed to by Eptura Engage. To ensure that the Exchange room and the Eptura Engage space remain synchronized, Eptura Engage creates the booking using the default admin account.
Good to know
- Recurrences and multi-room bookings from external users are not currently supported.
- The associated booking in Eptura Engage cannot be edited, but can be deleted.
- Bookings are created using the default admin account.
Learn more: Allow Exchange room invites from external senders
Recurrence limits
Recurrence limits for bookings created using the native Exchange journey is now a maximum of 450 instances, which aligns with existing booking journeys. Instances are calculated by multiplying the number of rooms by the number of occurrences in a series. Any bookings which exceed this limit will be declined.
Enhancements and general maintenance
General maintenance
ID |
Description |
|---|---|
|
IN-17720 |
Previously, if an alternate meeting space was booked due to a scheduling conflict, the original space details were not properly removed from the user's calendar appointment. This has been fixed. |
|
IN-17723 |
Recurrences that span over one year were incorrectly being accepted in Exchange but not showing in Eptura Engage. Now Eptura Engage rejects any booking which spans over one year, as per the documented limitations. Learn more: Recurring appointments |
|
IN-20368 |
When a booking was deleted from a room screen, the meeting space was not removed from the user’s Outlook appointment. This has been fixed. |