Workplace Reservation With Azure Sync Failing for a Particular Room
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-09-2023 05:30 AM
We are very new to the sync of Reservations betweeN SN and Azure for conference room calendar syncing. Its generally working fine, but we have a particular room that does not seem to sync reservations made out to Azure... sits there in a pending state and never does anything. We are not even sure where to check as it appears the same configuration as the other rooms, but we continue to have trouble. Any tips on where to start looking?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-18-2023 01:22 AM
Subcription being field in after Activation means the room is in sync.
In case it still does not produce reservation when you book there are few places you can check.
In case the booking originates from Outlook you can check if event is created in here:
Microsoft Exchange Online Spoke-->Events
In case the booking originates from ServiceNow you can check if event is created in here:
Workplace Calendar Synchronization-->Events
Review those events and see what status you have, in case not 200 check the error in the payloads.
You can also check the below article and make sure your AD side of set up is fine. I mean permissions and so on:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-30-2024 06:59 AM
Can you check what is the error.
Go to Workplace Calendar Synchronization --> Synchronization --> Events
Open the event related to your reservation and check the Response section.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-13-2023 05:53 AM
Some additional detail we have figured out:
This seems to be a problem with recurring meetings over more than one day. A "Recurring Parent" reservation gets created and then an "Occurrence" for each meeting. The parent gets a sync state of SYNCHRONIZATION NOT REQUIRED, and never gets sent out to Azure. So SN thinks the time is blocked and shows it if you try and reserve from the SN portal, but Azure does not.