Two teams arrive for the same meeting room. Both organisers can show an appointment, yet nobody can explain which reservation the room accepted. Before buying another booking tool or changing every calendar setting, check the actual request path and the Microsoft 365 rules that process it.

A meeting on an organiser's calendar, an invitation sent to a room and an accepted room reservation are different pieces of evidence. This guide proposes a focused review for UAE offices using Exchange Online. It does not diagnose a particular tenant or prescribe one policy for every room.

The artwork is a concept illustration of conflicting reservations, not a Microsoft interface or an ITZ client installation.

Start with one conflicting example

Collect the room address, organisers, meeting dates, time zones and the room's responses. Check whether the invitations targeted the same room, whether one was a recurring series and whether anyone edited a calendar directly. Remove private meeting content from the evidence shared with a supplier.

Ask what each person means by “booked”. A receptionist's note, a tentative calendar item and an acceptance from the resource are not interchangeable. Reconstruct the sequence before deciding that Outlook is at fault.

Confirm that the resource is configured for its purpose

Microsoft's Exchange Online resource-mailbox guidance distinguishes room and equipment mailboxes and describes booking and delegation settings. Have an authorised administrator confirm the resource type, address, processing mode and who owns its policy.

Then agree the business rule in ordinary language. Can any employee reserve the room when it is free? Does an administrator approve every request? Are certain teams allowed to book automatically? Who handles an exception? These choices should be explicit before technical settings change.

A scoped Microsoft 365 administration review of room mailboxes and booking policies can turn that discussion into an implementation brief. Request a Meeting Room Booking Review with the room address and a description of the problem.

Read the current policy before replacing it

Get-CalendarProcessing lets an appropriately authorised administrator inspect a resource's processing options. Save the current settings for comparison and rollback. Avoid applying a copied configuration to all rooms while investigating one example.

Microsoft's Set-CalendarProcessing reference explains automatic processing, eligible bookers, approval delegates and conflict handling. The AutoAccept mode still evaluates policies; its name does not mean every request must be accepted. Recurring conflicts also involve the configured conflict-count and percentage thresholds, so inspect the whole policy rather than changing only AllowConflicts.

Review booking eligibility and direct calendar-editing permissions as separate questions. Ask the administrator to demonstrate the intended request route using an ordinary staff account, and explain any privileged exception process. Give the receptionist a clear procedure for overrides rather than relying on undocumented edits.

Agree a small acceptance-test matrix

Use harmless test subjects, a quiet period and designated test accounts. Record the expected outcome before submitting requests. A suggested matrix is:

  • Available slot: an eligible employee receives the expected acceptance or approval-pending response.
  • Occupied slot: a second request produces the agreed conflict outcome.
  • Recurring series: one occurrence conflicts; check the response for the series and the affected occurrence.
  • Outside policy: a request beyond the allowed duration, booking horizon or working hours follows the intended rule.
  • Delegate route: the responsible person receives a request when approval is required and the organiser receives the final decision.
  • Cancellation and change: cancelling or moving the test meeting produces the expected room availability.

These are proposed acceptance cases, not claims about your current configuration. Remove test reservations afterwards and retain a short outcome log.

Check time, privacy and the human handover

For a Dubai office working with overseas teams, include the organiser's and resource's time-zone settings in the review. If the room is restricted to working hours, verify the resource's configured hours instead of assuming they match an employee's calendar.

Decide what colleagues should see about a reservation. Facilities staff may need a contact name while confidential meeting details need different treatment. Confirm the chosen permissions and processing settings with the business owner, and inspect the actual resulting calendar display.

If a request has no visible response, investigate delivery rather than immediately weakening booking rules. The missing-email investigation guide explains how to approach that separate problem. A booking review also does not prove the room's conferencing equipment works; test that independently.

Make the final policy understandable

The useful handover is a short booking instruction, a named policy owner and evidence that the agreed cases passed. It should explain how staff reserve a room, recognise confirmation and request an exception. Recheck relevant cases after a booking-policy or delegate change.

Request a Meeting Room Booking Review to discuss your room mailboxes, recurring-meeting conflicts and approval responsibilities. Use the form below; provide a redacted example rather than passwords or confidential meeting invitations.

Microsoft documentation reviewed 21 October 2026. The review sequence and test matrix are editorial recommendations, not a tenant-specific assessment.