Update - May 11, 2021: Updated with floor plan information.
Imagine you could book an office to work anywhere in the world. Now imagine this could be done in Outlook. Well, we have built a feature...
Updated May 11, 2021
Version 9.0
Blog Post
I have a customer using workspaces now, and they think it's great! It's a really nice feature and allows them to come back to work safely...especially since they hired more people in the last year than they actually currently have seats for.
The problem is "booking type". They do have a few permanently assigned seats, but they wanted workspaces created for those places as well (if a user is on extended leave, vacation, gets hit by the IT bus, etc. and that space is available for a period of time, they'd like to use it). So, me being me, I thought I'd set the booking type on those spaces to "reserved" as outlined in the "set-calendarprocessing" Microsoft Doc:
-BookingType
This parameter is available only in the cloud-based service.
The BookingType parameter specifies how reservations work on the resource mailbox. Valid values are:
- Standard: The resource can be reserved based on the other settings in this cmdlet. This is the default value
- Reserved: The resource can't be reserved.
Problem is...it doesn't work. A workspace that has a booking type of "reserved" can still be booked. I opened up a support ticket and after weeks of nothing, I got "expected results were not as per the article". Basically, setting the booking type to "reserved" and still being able to book it is expected behavior and the article is wrong.
We are currently using the workaround of setting the capacity for those spaces to 0 so any requests to those spaces are declined. But that's a **bleep** workaround. Any thoughts on why "booking type" isn't working?