Take Care of Your Scheduling Needs with Microsoft Bookings and Scheduler in Microsoft 365

The bookings system app shows promise but the rest of this post is not going to be pretty - sorry to rain on your day Sally_Richardson but this is past frustrating.

The Graph API behind it is terrible. 

• Missing or blank fields in Graph
• Significant Elements that can be added by the UI but not added or retrieved via Graph (i.e. the new Customers array, Service notes field,  Timezones, and + many more)
• No search of filtering other than a non O-Data date action (calendarView) for date filtering (why?  why???).
• Had to write an "available appointments" api because the one in the UI is not exposed in Graph.
• The beta and the V1 release are on different end points - no explanation of what "solutions" will be.
• No release notes for any beta versions and we don't know what you are working on.
• No sensible single place to provide developer feedback, see others feedback and where there is a location, no response from msft to virtually any of it.  You'd think this was a dead-end product on life support.
• + more

I don't understand how the Graph APi for bookings got released to V1 in December (unless someone's performance review depended on it of course).  It is nowhere near a release feature level or quality bar.

I have spent 5 weeks on this building a solution for scheduling service installations and thinking all the time "I am not getting it, it must be me" but just coming to the realization that the Graph API implementation is unusable.  It would have taken me less time to build a scheduling database and rest api.  Grrr.

Please do something with BookingsBusiness Graph - take it down or make it usable.  I hope people see this post and save wasting their time until MSFT is ready to release something usable by developers.

Thanks, Mark.