Book a workspace in Outlook

The issue described by Ben_Phung does still exists (https://techcommunity.microsoft.com/t5/exchange-team-blog/book-a-workspace-in-outlook/bc-p/1719199/highlight/true#M28907).
A minimal setup for showcase the issue would be:

Setup:
Create a workspace with capacity 2.
E.g.
1. New-Mailbox -Room "dev-desk-01" | Set-Mailbox -Type Workspace
2. Set-Place -Identity "dev-desk-01" -Capacity 2
3. Set-CalendarProcessing "dev-desk-01" -EnforceCapacity $True -MinimumDurationInMinutes 180

Steps:

1. From outlook create the event "Working during morning", use RoomFinder to add "dev-desk-01", with a duration from 08:00 - 12:00
   1. A mail response about the request being accepted is received: 
      'dev-desk-01' has enough capacity for your request. Total capacity: 2. Available: 2. Attendees in this request: 1. Remaining: 1
2. From outlook create the event "Working all day", use RoomFinder to add "dev-desk-01", with a duration from 08:00 - 17:00
   1. A mail response about the request being accepted is received: 
      'dev-desk-01' has enough capacity for your request. Total capacity: 2. Available: 1. Attendees in this request: 1. Remaining: 0.
3. From outlook create the event "Working Afternoon", use RoomFinder to add "dev-desk-01", with a duration from 13:00 - 17:00
   1. A mail response about the request being denied is received: 
      Your request was declined because there are conflicts.
      

      The conflicts are:  Organizer and Time of Conflicting Meeting
      <users name redacted> - Friday, March 19, 2021 8:00:00 AM to Friday, March 19, 2021 5:00:00 PM

This makes no sense, since only one user is attending the workspace during the afternoon.

Expectation:

The event for "Working Afternoon" is accepted, with the capacity droping down to 0 afterwards between 13:00 and 17:00.

Notes:
As noted in the referenced issue, if the order of the bookings where different it does work as expected.

If the order would be: 2 -1 - 3 instead, then the afternoon booking works. It is however the only case where it works as expected.

This isn't feasible, since you aren't able to syncronize the order you do your bookings in an organization to that level, as from what the blod post describes, one would think Workspaces have set out to solve the issue, not be dependent on something else solving it for it.