Skip to main content

 

Eptura Knowledge Center

Quick reference - supported and unsupported functionality

  1. Last updated
  2. Save as PDF

Calendar integration at enterprise scale involves multiple platforms that operate and evolve independently. As a result, sync discrepancies are expected and are proactively managed through continuous monitoring. 

Use this guide as a quick reference for supported and unsupported functionality with the Eptura Engage Microsoft 365 integration. It covers booking methods, synchronization behavior, supported booking types and features, common limitations, known issues, user actions that can cause synchronization issues, and recommended configuration settings. More detailed information about behaviors and limitations can be found on the following pages:

What's not covered - This guide focuses on making and managing bookings after Exchange rooms have been mapped to Eptura Engage resources. It does not cover issues or conflicts that can occur during the initial room mapping and synchronization process. For information about initial synchronization and room mapping, see: Exchange Room mapping

Understanding 👤User as Organizer and 🏢Room as Organizer events

It is important to understand the difference between User as Organizer and Room as Organizer events, how each event type is created, and how they affect synchronization behavior and available Eptura Engage functionality.

Depending on how a booking or event is created, the associated Outlook event might save the user as the organizer (UAO) or the room as the organizer (RAO): 

    • 👤User as Organizer
      User as Organizer (UAO) events are created in the user's calendar (either directly or by Eptura Engage), with the associated Exchange room either invited or added to the location field. 

    • 🏢Room as Organizer
      Room as Organizer (ROA) events are created directly in the Exchange room calendar by Eptura Engage. 

    Where relevant, the tables below indicate whether a scenario applies to 👤User as Organizer, or 🏢Room as Organizer events

    Some organizations use a service account* to improve compatibility with third-party room screens. Bookings created through the service account generate a 👤User as Organizer event, with the service account as the organizer and the Exchange room (and attendees) invited to the event.

    *A service account is an Exchange mailbox that acts as the organizer for bookings when Add to Outlook is not selected or when the user's calendar is not subscribed. Learn more: Service account for User as Organizer events

    Booking methods

    1. Where can users book Exchange rooms from?
    Learn more...

    Unless otherwise stated, the following assumes the user's Outlook calendar is subscribed

     
    Method
    Status
    Capability
    1.1 Eptura Engage Outlook add-in ✅ Supported

    Book meeting spaces directly from Outlook calendar events using the Eptura Engage  Outlook add-in.

    💡The add-in shows all available Eptura Engage spaces, including those that are not mapped to Exchange rooms. Booking an unmapped meeting space adds it to the event's location field, and any changes are synchronized.
    1.2 Native Exchange booking ✅ Supported Book directly from Outlook by simply inviting an Exchange room to an Outlook event - no add-in required
    1.3 Outlook Web App (OWA) ✅ Supported

    Book meeting spaces from Outlook Web App (OWA) using the Eptura Engage Outlook add-in.

    💡The add-in shows all available Eptura Engage spaces - including those that are not mapped to Exchange rooms. Booking an unmapped meeting space adds it to the event's location field
    1.4 Eptura Engage web app ✅ Supported Book directly through the Eptura Engage application with the 'Add to Outlook' option
    1.5 Eptura Engage mobile app ✅ Supported Book mapped resources through the Eptura Engage mobile app
    1.6 Microsoft Outlook mobile app ✅ Supported Book a meeting space directly from the Outlook mobile app by inviting the Exchange room to the Outlook event (Native Exchange booking)
    1.7 Microsoft Teams calendar ✅ Supported Book meeting spaces from the Teams calendar by inviting Exchange rooms to events
    1.8 Microsoft Teams Chat/Channel ✅ Supported Book meeting spaces from Teams chats or channels using the Eptura Engage chatbot
    1.9 Room screens ✅ Supported

    An event is automatically created when the booking is created and authenticated from either an Eptura, Condeco, or third-party room screen

    Some limitations might apply - check the following sections for more information about behaviors and limitations when using specific booking methods.

    2. Synchronization behavior by booking method
    Learn more...

    Unless otherwise stated, the following assumes the user's Outlook calendar is subscribed

     
    Booking Method
    Status
    Synchronization behavior
    2.1 Booking from the Engage web app with 'Add to Outlook' set

    ✅ Supported

    Fully supported two-way synchronization between Exchange and Eptura Engage. Event created in the user's Outlook calendar with the Exchange room added to Required attendees

    Creates 👤UAO event
    2.2 Booking from the Engage web app with 'Add to Outlook' not set

    ⚠️ Partially supported

    Event is created directly in the Exchange room calendar to maintain synchronization with the room 

    Creates 🏢RAO event
    2.3 Booking from Outlook - room invited by user

    ✅ Supported

    Fully supported two-way synchronization between Exchange and Eptura Engage. Event created in the user's Outlook calendar with the Exchange room added to Required attendees

    Creates 👤UAO event
    2.4 Booking from Exchange/Outlook - created in room calendar ⚠️ Partially supported

    Booking is created in Eptura Engage using the default Admin account to maintain synchronization

    Creates 🏢RAO event
    2.5 Editing a booking from Eptura Engage ✅ Supported

    Changes are synchronized with the Exchange event
    2.6 Editing an event in Outlook ✅ Supported

    Changes are synchronized with the Eptura Engage booking
    2.7 Organizer deletes booking from Eptura Engage (not from Today page) ✅ Supported

    An option lets the organizer choose whether to cancel or retain the associated Outlook event. This option is not shown if the booking is deleted via the Today page - see 2.8

    Applies to 👤UAO events
    2.8 Organizer deletes booking via the Eptura Engage Today page   ✅ Supported

    Room removed from the Outlook event but the event is retained

    Applies to 👤UAO events
    2.9 Booking deleted from Eptura Engage (not by organizer) ✅ Supported

    Room removed from the Outlook event, but the event is retained
    2.10 Event deleted from Outlook ✅ Supported

    Booking deleted in Eptura Engage
    2.11 Outlook event is forwarded to the Exchange room, and the organizer is an internal user ⚠️ Conditional

    If the organizer is internal and Eptura Engage has access to the user's calendar, the event is synchronized with Eptura Engage

    Creates 👤UAO event.
    2.12 Outlook event is forwarded to the Exchange room, and the organizer is external ⚠️ Conditional

    If the organizer is external and the Exchange parameter  ProcessExternalMeetingMessages = TRUE, the event is synchronized with Eptura Engage using the default admin account. (Single-day, single-room events only).

    Creates 🏢RAO event.
    2.12 Booking created in Eptura Engage but the Exchange room is unavailable ✅ Supported

    The booking is initially created in Eptura Engage, but then automatically canceled when the Exchange room declines the event (due to a conflict).

    💡If notifications were requested by the user, they will first receive a confirmation email, followed by a cancellation email.  

    Making and managing bookings

    3. What booking types are supported?
    Learn more...

    Unless otherwise stated, the following assumes the user's Outlook calendar is subscribed

     
    Booking type
    Status
    Capability
    3.1 Single-day bookings  ✅ Supported

    Fully supported with two-way synchronization between Exchange and Eptura Engage

    👤UAO events
    3.2 Bookings - non-subscribed users ⚠️ Partially supported

    Supported for single-room bookings only. Bookings are created under the default Eptura Engage Admin account
    3.3 Recurring bookings  ⚠️ Known limitation

    Supported with a defined end date and up to 450 total instances (recurrences × rooms)
    3.4 Recurring booking patterns ⚠️ Known limitation

    Standard daily, weekly, and monthly recurring bookings are supported, provided an end date is set.

    ❌ Exchange 'yearly' recurring events are not supported. Yearly recurring events are booked as individual bookings in Eptura Engage, and not saved as a series.

    ❌ Eptura Engage 'Specific' recurring bookings are not supported.
    3.5 Multi-room bookings ⚠️ Partially supported

    👤UAO events - The integration supports up to 8 meeting spaces per user calendar event

    🏢RAO events - ❌ Multi-room bookings are not supported when created directly in an Exchange room calendar.
    3.6 Bookings within advanced booking period ✅ Supported

    A booking must be created within the Eptura Engage group's advanced booking period; otherwise, it will be declined
    3.7 Booking requests within required notice period ('managed' meeting spaces) ✅ Supported

    A request to book a managed space must fall within the Eptura Engage group's notice period; otherwise, it will be declined
    3.8 Bookings within business hours ✅ Supported

    A booking must be within the business hours defined for the Eptura Engage group; otherwise, it will be declined
    3.9 Bookings up to 3 years in the future ✅ Supported

    If no advanced booking period is set for the Eptura Engage group, a booking can be made up to 3 years in advance.

    ❌ Events created more than 3 years in the future are not supported by the integration and are declined 
    3.10 Private bookings ⚠️ Partially supported

    Eptura Engage 'private' bookings synchronize with Exchange; however, any changes to the title must be made from the Eptura Engage booking

    4. What booking types are incompatible or conditional?
    Learn more...

    Unless otherwise stated, the following assumes the user's Outlook calendar is subscribed

     
    Scenario
    Applies to
    Status
    What happens and what to do
    4.1 Recurrences with more than 450 instances Native Exchange booking

    ❌ Not supported 

    Eptura Engage declines the booking, which removes the room from the user's event

    💡Set an end date that ensures the total number of instances (recurrences × rooms) does not exceed 450 
    4.2 Recurrences with no end date Native Exchange booking ❌ Not supported 

    Eptura Engage declines the booking, which removes the room from the user's event

    💡Set an end date
    4.3 'Specific' recurrence patterns Eptura Engage  ❌ Not supported 

    The 'specific' recurrence option is disabled when the Microsoft 365 Integration is enabled, even for resources not mapped to Exchange

    💡️Create individual bookings or a daily, weekly, or monthly recurrence
    4.4 Daily recurrence - excluding weekends Eptura Engage ❌ Not supported 

    Exchange does not support the option to exclude weekends from daily recurring events, so this option is disabled in Eptura Engage 

    💡Select all days from Monday-Friday as the recurrence pattern
    4.5 Changing the meeting space of a recurring booking that has instances in the past Recurrences with past instances ⚠️Known limitation Eptura Engage updates only future bookings, but Exchange updates the entire series, including past instances
    4.6 Editing recurring bookings from the mobile app Eptura Engage mobile app ❌ Not supported

    Recurring bookings behave as single events in the Eptura Engage mobile app. Editing a single instance of a recurring booking from the Eptura Engage mobile app will update only that instance

    💡️Edit recurring bookings from Outlook or the Eptura Engage web app
    4.7 Changing the private flag for a single instance of a recurring series Recurrences and the private flag ⚠️Known limitation Exchange only supports one private flag for an entire series; therefore, changing the private flag on a single Eptura Engage booking has no impact on the recurring Exchange event
    4.8 More than 8 rooms Native Exchange booking ❌ Not supported by the integration

    Eptura Engage declines the booking, which removes the room from the user's event

    💡️Include 8 or fewer rooms
    4.9 All-day events Native Exchange booking ❌ Not supported 

    Eptura Engage declines the booking, which removes the room from the user's event

    💡️Set a start and end time
    4.10 More than 3 years in the future Native Exchange booking ❌ Not supported by the integration Exchange declines the event, and the booking is removed from Eptura Engage
    4.11 Outside of the advanced booking period Eptura Engage group settings ❌ Booking declined

    Eptura Engage declines the booking, which removes the room from the user's event
    4.12 Outside the required notice period (managed spaces) Engage group settings ❌ Booking declined

    Eptura Engage declines the booking, which removes the room from the user's event
    4.13 Outside business hours Engage group settings ❌ Booking declined Eptura Engage declines the booking, which removes the room from the user's event
    4.14 Linked meeting space booking Eptura Engage  ❌ Not supported

    Individual events are created in the mapped Exchange rooms. Changes to the linked booking are not correctly synchronized to the Exchange room calendars, which can cause out-of-sync issues

    ❌ We recommend Admins do not map Exchange rooms that are part of a linked room setup in Eptura Engage
    4.15 Forwarded single-day, single-room invite to an Exchange room, where the organizer is external. Native Exchange booking 🛠️Configuration required

    Exchange declines the event, and the booking is removed from Eptura Engage, unless ProcessExternalMeetingMessages = TRUE

    💡 Admins can set the Exchange parameter  ProcessExternalMeetingMessages = TRUE to allow external events to be forwarded to a room (single-day, single-room only)
    4.16 Forwarded recurring invite to an Exchange room, where the organizer is external. Native Exchange booking ❌ Not supported

    Eptura Engage declines the booking

    💡Only single-day, single-room invites forwarded from an external organizer are supported
    4.17 Forwarded multi-room invite where the organizer is external. Native Exchange booking ❌ Not supported

    Eptura Engage declines the booking

    💡Only single-day, single-room invites forwarded from an external organizer are supported
    4.18 Managed meeting space booking approvals Exchange and Engage ⚠️Conditional

    Depending on settings, booking requests might need to be approved in both Exchange and Eptura Engage, or only in Engage

    💡Admins can set the Exchange parameter AutomateProcessing to AutoUpdate (dual approval) or AutoAccept (Engage approval only) 
    4.19 Blind-managed meeting space Eptura Engage ❌ Not supported Blind-managed meeting spaces are not shown in search results from the Eptura Engage Outlook add-in. 
    4.20 Attendees added to event  Native Exchange booking ⚠️Partially supported

    Attendees are considered ‘remote’ and therefore do not appear on the Eptura Engage booking form attendee list. See also: 5.4

    💡Attendees can be marked as 'on site' from the Eptura Engage Outlook add-in and will then be automatically added to the Engage booking form
    4.21 Eptura Engage 'Smart alternatives' technology  Native Exchange booking ⚠️️Partially supported

    Only limited search details can be determined, such as the location and floor of the original meeting space. See also: 5.1a / 5.2b

    💡For full 'smart alternatives' technology when moving a booking or creating a recurring booking, use the Eptura Engage Outlook add-in or web app
    4.22 Waitlist Eptura Engage ❌ Not supported

    When a request is moved to the waitlist, the booking is removed from Engage as expected, but the Exchange room is not removed from the event, causing out-of-sync issues
    4.23 Activity detected by occupancy sensors Eptura Device Hub ❌ Not supported Check-in and release responses from occupancy sensors are not supported.
    4.24 Personal spaces Eptura Engage ❌ Not supported The Eptura Engage Microsoft 365 integration only supports bookings for Engage meeting space resources
    4.25 Delivery points Eptura Engage ❌ Not supported The Eptura Engage Microsoft 365 integration only supports bookings for Engage meeting space resources

    5. What booking features and functionality are supported?
    Learn more...

    Unless otherwise stated, the following assumes the user's Outlook calendar is subscribed

     
    Feature
    Method
    Status
    Capability
    5.1a Smart alternatives - self-healing bookings Eptura Engage Outlook add-in  ✅ Supported Automatically finds an alternative space using the original search parameters when a booking is moved to a conflicting time
    5.1b Native Exchange booking ⚠️Partially supported Only limited search details can be determined, such as the location and floor of the original meeting space. See also: 4.21
    5.2a Smart alternatives - smart recurrences Eptura Engage Outlook add-in  ✅ Supported Automatically finds an alternative space using the original search parameters when the booked room is unavailable for some instances of a recurring booking
    5.2b

    Native Exchange booking

    		 ⚠️Partially supported

    Only limited search details can be determined, such as the location and floor of the original meeting space. See also: 4.21
    5.3 Capacity

    Eptura Engage Outlook add-in

    		 ✅ Supported

    Searches for spaces suitable for the number of attendees added to the event
    5.4 Attendee estimates (Intelligent attendees)

    Eptura Engage Outlook add-in

    		 ✅ Supported

    The number of on-site and remote attendees is estimated based on attendees' in-office statuses 

    ❌ Not supported when events are created natively in Exchange - all attendees are assumed to be remote. See also: 4.20
    5.5 Attributes

    Eptura Engage Outlook add-in

    		 ✅ Supported

    Search for spaces that offer specific attributes - such as a television or whiteboard, etc.
    5.6 Workspace types

    Eptura Engage Outlook add-in

    		 ✅ Supported

    Search for a specific workspace type - such as a conference room or meeting room, etc.
    5.7 Outlook delegates

    All

    		 ⚠️ Conditional

    Only Microsoft Outlook delegate permissions are required to update bookings from the owner’s calendar, but Eptura Engage delegate permissions are also required to update bookings and request services from Eptura Engage 
    5.8 Services

    All 

    		 ✅ Supported

    Services such as catering and equipment can be requested via a direct link to the Eptura Engage web app booking form, sent by email

    6. What user actions can cause synchronization issues?
    Learn more...

    This lists the most common user actions that can cause synchronization issues or require consideration; the list is not exhaustive.

     
    Scenario
    Applies to
    Status
    What happens and what to do
    6.1 When the User is the Organizer, events must not be edited or managed directly from the Exchange room calendar Exchange room calendar
    ❌ Not supported

    ⛓️‍💥Editing events directly from the room calendar can cause out-of-sync errors for 👤UAO events

    💡Edit events from the user's calendar or from Eptura Engage 
    6.2 Deleting in-progress bookings from Outlook Outlook event ❌ Not supported

    ⛓️‍💥Deleting events from Outlook that are in progress can cause out-of-sync errors.

    💡End the booking early from Eptura Engage
    6.3 Room removed from event location field but not from the list of attendees (or vice versa) Outlook event ⚠️Known limitation

    If the room is not removed from both fields, the Eptura Engage booking is removed, but the Exchange event might remain. Although this does not create out-of-sync errors, it can be confusing.

    💡Remove room from both the location field and the attendees list
    6.4 Closing an Eptura Engage meeting space Eptura Engage Resource admin ❌ Not supported ⛓️‍💥When a meeting space resource is closed, existing bookings are removed from Eptura Engage but not from Exchange, causing out-of-sync errors
    6.5 Moving a request for a managed space to the Waitlist Eptura Engage managed spaces ❌ Not supported ⛓️‍💥If a request is moved to the waitlist, the booking is removed from Engage as expected, but the Exchange room is not removed from the event, causing out-of-sync errors

    7. What limitations apply when Eptura Engage has no access to the calendar (user is not subscribed)?
    Learn more...

    When Eptura Engage detects an invite to an Exchange room calendar from a user's calendar that is not yet subscribed, it will attempt to automatically create a subscription to that user's calendar and then book the associated resource in Eptura Engage. If a subscription is not possible, then the following limitations apply:

     
    Scenario
    Status
    Impact when a user is not subscribed
    7.1 Inviting a mapped room from an Outlook event ⚠️Partially supported

    Booking is created in Eptura Engage using the default Admin account to maintain synchronization
    7.2 Editing a booking ⚠️Known limitation

    Bookings created by non-subscribed users can only be deleted from Eptura Engage; they cannot be edited. 

    💡Edit events from Outlook.

    7.3

    Create only single-day, single-room  Outlook events. 

    ⚠️Known limitation

    		 Eptura Engage automatically declines recurring and multi-room bookings when the user is not subscribed
    7.4 Recurring events created in Outlook  ❌ Not supported Recurring bookings are declined by Eptura Engage when a user is not subscribed.
    7.5 Multi-room events created in Outlook ❌ Not supported Multi-room bookings are declined by Eptura Engage when a user is not subscribed.

    7.6

    Subscription is prevented when existing bookings exist.

    ❌ Not supported

    Users who have bookings already created via the non-subscribed user journey are prevented from subscribing. See also: 8.2

    7.7

    Making a booking from the Eptura Engage web app

    ⚠️Partially supported

    When a user's calendar is not subscribed, the 'Add to Outlook' option is not shown when making bookings from the Eptura Engage web app, however, an 🏢RAO event is created directly in the Exchange room calendar.

    Configuration and settings

    8. What configurations or settings can cause issues?
    Learn more...
     
    Scenario
    Applies to
    Status
    What happens and what to do
    8.1 Exchange organizer does not have permission to book Eptura Engage resource Native Exchange booking ❌ Not supported

    Room booked in Exchange but Eptura Engage then rejects the booking, resulting in the room being removed from the user's event and the room calendar

    💡Grant the organizer booking access to the resource or resource group
    8.2 Eptura Engage does not have access to the organizer's Exchange calendar User is not subscribed ⚠️ Partially supported

    Engage attempts to subscribe to the user's calendar, and if unsuccessful, the non-subscribed user journey is followed; the booking is created in Eptura Engage using the default Admin account to maintain synchronization

    💡If the user's calendar cannot be subscribed, it might be because the user has existing bookings in Engage. These bookings must be cleared before the user's calendar can be subscribed. See also 7.6
    8.3 Single-day event sent from external organizer to Exchange room mailbox  Native Exchange booking 🛠️Configuration required

    Booking is declined unless ProcessExternalMeetingMessages = TRUE

    Set the Exchange parameter  ProcessExternalMeetingMessages = TRUE to allow external events to be forwarded to a room (single-day, single-room only)
    8.4 Providing then revoking calendar subscriptions (or vice versa) Eptura Engage - subscribe to user calendar ❌ Not supported

    Causes synchronization issues that prevent bookings from being tracked or updated in Exchange

    💡We recommend a user’s calendar is subscribed for the entire lifetime of the integration
    8.5a Exchange primary address and Eptura Engage email address do not match Native Exchange bookings ❌ Not supported See 8.1
    8.5b Eptura Engage bookings ❌ Not supported See 8.2
    8.6 Booking a space with set-up and clean down buffer times configured Eptura Engage Outlook add-in

    ⚠️Known limitation

    The add-in respects buffer times when finding and booking an Eptura Engage resource. However, the associated Exchange room is only booked for the meeting duration and does not include the buffer time.

    💡Remove buffer times from Engage resource OR hide the mapped Exchange room from the Global Address List (GAL) so it cannot be added natively to an event
    8.7 Exchange mailbox not set as 'room' type Eptura Engage -Exchange room mapping ❌ Not supported

    Does not appear on the Exchange room mapping page

    💡Set Exchange mailbox type as 'room' 
    8.8 Multiple rooms mapped to a single Eptura Engage resource Eptura Engage  -Exchange room mapping ❌ Not supported It is not possible to map more than one Exchange room to an Eptura Engage resource
    8.9 Updating an Exchange room email address when mapped to an Eptura Engage resource Exchange room ❌ Not supported

    Will cause existing bookings to become out of sync

    ❌Updating the email address of an Exchange room that is already mapped to an Eptura Engage resource is not supported. If required, Contact Support 
    8.10 Custom fields on booking form Eptura Engage meta admin fields ⚠️Conditional

    Custom fields set to mandatory might cause a booking to be rejected

    ❌Custom fields must not be set to mandatory
    8.11 Closed meeting space resources Eptura Engage ⚠️Known limitation

    Does not prevent the Exchange room from being booked

    💡Create a placeholder event in Exchange for the duration of the closure
    8.12 User deleted from Eptura Engage Eptura Engage ⚠️Known limitation

    Future Eptura Engage bookings and associated Exchange room events are deleted

    💡Events remain on the user's calendar and must be canceled separately if required
    8.13 Linked meeting space bookings Eptura Engage ❌ Not supported

    Individual events are created in the Exchange room calendars. Changes to the Engage linked booking are not correctly synchronized to the Exchange room calendars, which can cause out-of-sync issues

    ❌Do not map Exchange rooms that are part of a linked room setup in Eptura Engage
    8.14 Blind-managed meeting space bookings Eptura Engage ❌ Not supported

    Allows users to directly invite the Exchange room via a calendar event and book the Eptura Engage resource, bypassing the blind-managed booking process. 

    ❌Do not map an Eptura Engage blind-managed resource to an Exchange room

    9. When Exchange parameters are not aligned with Eptura Engage settings
    Learn more...
     
    Exchange parameter
    Required value
    What it does
    Outcome if value is not aligned
    9.1 AllowConflicts FALSE Prevents the Exchange room from accepting conflicts for single-day bookings Eptura Engage does not manage conflicts, and Exchange room accepts conflicting bookings.
    9.2 ConflictPercentageAllowed 100 Allows entire recurring series to be accepted with instance-level conflict handling
    		 Recurring series might be rejected instead of accepting the series and declining only conflicting instances
    9.3 MaximumConflictInstances 450 Enables large recurring series while declining only conflicting instances
    		 Large recurring series with conflicts might be entirely rejected
    9.4

    AutomateProcessing 

    For self-managed rooms

    		 AutoAccept Self-managed rooms automatically accept valid bookings
    9.5

    AutomateProcessing

    For managed rooms

    		 AutoAccept or AutoUpdate AutoAccept - approval required from Eptura Engage only
    AutoUpdate - approval required from both Eptura Engage and Exchange
    9.6 BookingWindowInDays

    Align with Eptura Engage group setting

    Max value is 1080

    		 Prevents events from being created outside of the advanced booking period Events might be created in Exchange that are rejected by Eptura Engage if outside of the advanced booking period
    9.7

    MaximumDurationInMinutes

    Align with Eptura Engage group setting

    		 Prevents events from being created that exceed the maximum duration allowed Events might be created in Exchange that are rejected by Eptura Engage if the duration exceeds the allowed time
    9.8 EnforceSchedulingHorizon
    		 TRUE Prevents events from being created outside of the defined booking window Events might be created in Exchange that are rejected by Eptura Engage if outside of the booking window
    9.9 ScheduleOnlyDuringWorkHours
    		 Align with Eptura Engage group setting Prevents events from being created outside of business hours Events might be created in Exchange that are rejected by Eptura Engage if outside of working hours
    9.10

    WorkingHoursTimeZone

    		 Align with the location's time zone Prevents conflicts between Exchange and Eptura Engage Conflicts might cause booking failures

    Learn more

    For administrators

    For users