Features, prerequisites & limitations

Audience: Facility managers, IT, project teams

This page lists what Reservation Sync supports today for Microsoft Exchange and Google Calendar, what must be in place, and what is not supported.

Features

The following features are included:

  • Single reservations: created in any Workplace touchpoint or in Outlook/Google Calendar, synchronized with date, time, duration and attendees.
  • Recurring reservations: created in Workplace or Outlook/Google Calendar; all occurrences are synchronized.
  • Multi-room reservations: several rooms in one reservation (single or recurring), created in Outlook/Google Calendar or in Asset.
  • Several Exchange environments can be connected to one Spacewell environment.

Feature overview

Area

Feature

Exchange

Google

Scope and notes

Real-time sync

Create reservations (both directions)

YES YES
  • Single and recurring, single and multi-room (max. 100 rooms per reservation).
  • Exchange: recurring series without an end date are not supported.

Real-time sync

Update reservations: subject, reschedule, relocate (both directions)

YES YES
  • Single and recurring (whole series and single occurrences), single and multi-room.
  • Updates are made in the system where the reservation was created.
  • Removing the last room cancels the reservation.

Real-time sync

Cancel reservations (both directions)

YES YES
  • Single and recurring (whole series and single occurrences), single and multi-room.
  • Exchange: declining a Workplace-created reservation in Outlook does not release the room.

Room actions

Cancel a calendar-created reservation in Asset (reservation coordinator)

YES NO

Exchange: the room declines and is released; the meeting stays in the organizer’s calendar without the room.

Room actions

Release a room early: end early and no-show (Workplace to calendar)

YES NO
  • Exchange: the room calendar is updated and the room becomes available.
  • No-show needs an automation and occupancy sensors.

Services & equipment

Add or update services and equipment in Workplace on a reservation created in Outlook

UPCOMING NO

Google: no support currently planned.

Conflict handling

Real-time conflict resolution

YES NO
  • Single-room single reservations; the reservation created first is kept. On by default. Planned: single-room recurring (upcoming release).
  • Not supported: multi-room conflicts and conflicts caused by a room change.

Reconciliation

Scheduled reconciliation run

YES NO

Configurable overnight schedule. Only reservations within the reconciliation window (10–90 days ahead) are checked. Results are visible after the next run.

Reconciliation

Reconciliation report (e-mail to administrators for manual follow-up)

YES NO

Off by default. Also reports conflicts caused by Exchange or Workplace being configured to allow double reservations (these are not fixed).

Reconciliation

Automatically fix conflicts and sync issues

YES NO
  • Off by default. Single-room single reservations. Planned: single-room recurring (upcoming release).
  • Not supported: multi-room and room-change conflicts; these are included in the report e-mail.

Reconciliation

Out-of-sync recovery

YES NO

Single and recurring, single and multi-room, within the reconciliation window.

Diagnostics

Reservation Sync diagnostics (RCA tool)

UPCOMING NO

Google: no support currently planned.

Add-in

Room Finder Add-in

YES NO

Google: not planned.

Project

Moving existing reservations (in bulk)

YES NO

Google: no support currently planned.

For more information what is possible, see Room-centric synchronization explained

For example scenarios, see Room-centric calendar integration: example scenarios

Prerequisites

  • Access to the room calendars (not to personal calendars – people are invited to the meeting as participants).
  • Rooms set up the same way in both systems. Room and workplace names and capacity are not updated automatically between Asset and Exchange/Google Workspace; change them manually in Asset too. Settings such as "reserve the meeting room in advance until X" and regimes in Asset must match the working hours and reservation settings in Exchange, to avoid conflicts.
  • Every room (and workplace, if applicable) in Exchange belongs to at least one room list.
  • Configuration aligned between Asset and Exchange/Google: authorization levels, regimes, maximum number of recurring occurrences, etc.
  • Reservations in the past are not taken into account when Reservation Sync is activated.
  • Users can keep their local time zone in Outlook; no UTC setting is needed.

Info

Set-up and clean-up times do not exist in Exchange. Do not configure them in Asset for synchronized rooms.

Limitations

General

  • The organizer must be a real user in the synchronized Exchange environment, not an external e-mail address (Microsoft Graph API limitation).
  • Services (e.g. catering) and equipment (e.g. a flipchart) cannot be added via Outlook/Google Calendar. They also cannot be added in Workplace to a reservation created in Outlook, although this feature will be supported soon. 
  • When a meeting is forwarded, the new people are not added as participants in Asset. Add them as attendees and send an update to all (Microsoft Graph API limitation).
  • Reservations with status Draft in Asset are not synchronized; reservations with status Requested are. That is why approval workflows are not supported: if a reservation stays in Draft for too long, the organizer may think the room is booked while it is not.
  • Meetings set up as "delegated" in Exchange are ignored.

Asset features not supported for synchronized rooms in 3rd party tools

  • Composed meeting rooms and room compositions
  • Blocked dates, regimes
  • Set-up and clean-up times before and after a meeting
  • Reserving a meeting room in advance from a pre-defined period
  • Conflict tolerance policy

Recurring reservations

  • Series without an end date are not supported.
  • Maximum 360 occurrences per series. In the Integration Platform, Max Occurrences is a Sync Setting with default 180. Longer series are not synchronized.
  • Outlook "day 31" is not supported; use "last day of the month".

Multi-room reservations

  • Maximum 100 rooms per reservation.
  • Removing the last room from a meeting cancels it.

SLA - Synchronization timing

Reservations don't always sync instantly between Workplace and Outlook. Depending on the direction, a change can take a short time to appear in the other system.

Microsoft does not give SLAs for the time it takes between an event (e.g. a new or update reservation) to occur in Outlook and the Graph API delivering the change notification. However, as mentioned below, we noticed it can take up to 3 minutes for the change to be available in the Graph API message towards Spacewell.

For details, see Sync timing & delays