Can Microsoft Bookings book a shared room or resource?

What Bookings does block today#

Staff are protected across services. In the accepted answer to a July 2026 Microsoft Q&A thread, the responder set up two services with the same two staff, both set to Bookable when staff are free, booked one person at 9:00 on the first service, and found 9:00 no longer offered for that person on the second. That's the behaviour most people want for double-booking of people.

What's missing is the same rule for a thing. A 2026 thread describes six staff who share one fingerprint machine: whenever their hours overlap, customers can book two appointments for the same slot. The accepted reply (an AI-generated answer) confirms that Bookings "will not enforce a global 'one booking per time slot across all staff' rule". A Feedback Portal idea asking for exactly this, "Restriction on Duplicate Service Reservations", had 23 votes and was still open in September 2026.

Two related points from Microsoft Learn:

• Group services (Maximum attendees per event above 1) can't help either. The group attendees article lists "Group bookings doesn't support resource bookings at this time" as a known issue.
• The Microsoft Graph bookingStaffMember resource describes staff as people with an email address, working hours and a calendar. There is no separate resource type.

Workaround: book the resource as a staff member#

Add the room or machine to the staff list, then make every service that needs it depend on it.

1. Go to Staff → Add new staff. Give it a clear name ("Fingerprint machine") and an email address. Microsoft says staff can be added "with any email", so a shared inbox that the team reads works. Use the Guest role so it can't open the calendar.
2. Set its hours to the times the resource is usable (untick Use business hours and enter them).
3. Pick one of two service designs:
   • Resource only. Assign only the resource to the service. Each slot can then be booked once, whoever turns up. Staff hours aren't checked, so someone has to cover every slot.
   • Person plus resource. Create one service per staff member, open Assign staff, choose Multiple staff, and assign that person plus the resource. Microsoft documents that a Multiple staff booking can only be created when all assigned staff are free, so the resource is booked once across all of those services. See several staff on one appointment for how that mode behaves.
4. On each service, untick Allow customers to choose a particular staff for booking so customers don't see the resource as a person to pick.
5. For maintenance or closures, use the service's Availability options → Set availability for a different date range → Not bookable, or Add time off for the resource.

Limits of the workaround (as of September 2026)#

• It uses staff slots. A booking page supports up to 100 staff, and each resource counts as one.
• One service per person. The Multiple staff design means customers pick the service named after the person, which gets unwieldy past a few staff. Microsoft also says services should be limited to 50 per page.
• Emails go to the resource address. Every booking and change notifies it. Turn off Notify all staff via email on that entry if nobody reads the inbox.
• Outlook room bookings aren't seen unless Bookings can read that calendar. An address outside your tenant can't share free/busy, and Microsoft doesn't document using a room mailbox as staff. If people also reserve the room in Outlook, test whether those events block Bookings before relying on it.
• Booking pages are separate. Each page is maintained independently. Unless Bookings can read the resource's own calendar, a booking on one page won't block the same resource on another page.

What we saw when testing (September 2026)#

When we called the public booking service directly, it rejected a booking that clashed with another Bookings appointment for the same staff member, while it accepted one over a busy Outlook block (the booking page normally prevents that in the browser). That's why the resource-as-staff approach holds up for clashes between Bookings appointments on one page; Outlook-only reservations are the weak spot. See why Bookings can book over Outlook events.

If you need true resource scheduling (rooms with capacity, equipment pools, one resource across many pages), Bookings isn't built for it, and a dedicated room or resource booking tool is the better fit.

BookingsXP is independent and not affiliated with or endorsed by Microsoft.