Calendar Problems

Fix Calendar Delegate Not Receiving Booking Requests in Exchange

Camila MilosovichCamila Milosovich Oct 22, 2026 868 views

Question details

A newly assigned Exchange calendar delegate does not receive booking requests, causing incoming appointments to remain stuck in a pending state.

How to Fix Calendar Delegate Not Receiving Booking Requests
Product
Microsoft Exchange / Microsoft Bookings
Device & OS
not provided
Scenario
A user recently changed the calendar delegate for an Exchange resource mailbox and is trying to process new bookings and meeting requests.
Observed behavior
The new delegate does not receive booking requests. Message tracing indicates that no requests are being sent or received on behalf of the resource mailbox, and appointments stay pending.
Before you start

Ensure you have Microsoft 365 administrator privileges, as resolving this issue requires access to the Exchange Admin Center and resource mailbox settings.

Solution 1Recommended

Verify Delegate Permissions and Mailbox Processing Settings

Check the Exchange Admin Center to ensure the new delegate has the correct permissions and the resource mailbox is configured to properly route meeting requests.

When a delegate is replaced, the permissions may not inherit correctly, or the resource mailbox processing rules might fail to update. Verifying these settings forces the system to recognize the new delegate.

1
Log in to the Admin Center

Navigate to the Microsoft 365 admin center and sign in using your administrator credentials.

2
Access Exchange Settings

Go to the 'Exchange admin center' and locate the specific resource mailbox experiencing the routing issue.

3
Check Delegation Permissions

Open the mailbox properties, select the 'Delegation' settings, and ensure the new delegate is listed with 'Send on Behalf' or 'Full Access' permissions.

4
Verify Booking Policies

Check the resource mailbox's processing settings to confirm it is actively set to forward meeting requests to delegates rather than auto-accepting or declining them.

Verify Delegate Permissions and Mailbox Processing Settings
Synchronization Delay: Changes to Exchange delegate permissions can sometimes take up to 24 hours to fully propagate across Microsoft 365 services.
Free Microsoft Office alternative

Switch to WPS Office for a Seamless and Lightweight Experience

Dealing with complex administrative settings and synchronization errors in Microsoft 365 can be overwhelming. If you are looking for a straightforward, local solution for your daily tasks, WPS Office offers a free, lightweight, and highly compatible alternative for your document, spreadsheet, and presentation needs.

  1. 1. Download the Installer: Visit the official WPS Office website and download the free installer for your operating system.
  2. 2. Install the Software: Run the downloaded setup file and follow the simple on-screen instructions to install the suite.
  3. 3. Open Your Files: Launch WPS Office and immediately open your existing Microsoft Word, Excel, and PowerPoint files with perfect formatting preservation.
Highly compatible with Microsoft Office formats including DOCX, XLSX, and PPTX.Free and lightweight, requiring minimal system resources for fast performance.Familiar user interface ensuring zero learning curve for new users.Reliable offline access without relying on complex server-side configurations.
microsoft office alternative - wps office

Frequently Asked Questions

Why are my Microsoft Bookings appointments stuck on pending?

Appointments remain pending because the calendar is configured to require manual delegate approval, but the new delegate isn't receiving the requests to approve them due to permission or synchronization errors.

How long does it take for a new calendar delegate to take effect?

Changes to Exchange calendar delegates can sometimes take up to 24 hours to fully synchronize across Microsoft 365 servers and propagate to connected services like Microsoft Bookings.

What does it mean when message tracing shows no requests sent?

This indicates that the Exchange transport rules or mailbox processing settings are failing to generate the forwarding email to the new delegate, often pointing to a misconfigured resource mailbox policy or corrupted permission assignment.