Microsoft 365
Who Can Book This Room?
Permissions and Delegation Explained
Microsoft 365 room mailbox booking permissions explained — AllBookInPolicy, restricted booking, and delegate approval — and how they affect instant booking.
Short answer: every Microsoft 365 room mailbox has a booking policy that decides who can reserve it and whether requests are auto-accepted or need approval. By default AllBookInPolicy is $true, so anyone in the org can book and the room accepts automatically. You tighten this with BookInPolicy (an allow-list) or delegate approval. Instant booking from a display works cleanly with auto-accept rooms; approval-gated rooms will queue those bookings instead of confirming them.
Room permissions confuse people because there are two separate questions hiding in one. First: who is allowed to book? Second: does the booking get accepted automatically, or does a human approve it? Microsoft 365 answers both through the room's calendar processing settings, not through mailbox file permissions.
Get this right and rooms book themselves. Get it wrong and either everyone double-books your boardroom or nobody can reserve anything.
The two layers of room permission
| Layer | Cmdlet setting | What it controls |
|---|---|---|
| Who can book | AllBookInPolicy / BookInPolicy |
Which users' requests are eligible |
| How it's accepted | AutomateProcessing |
Auto-accept vs. delegate approval |
These combine. A room can be "anyone can book, auto-accepted" (the default open room) or "only the leadership team can book, and even they need the EA to approve" (a restricted boardroom).
Default behavior: open and automatic
Out of the box a room mailbox is maximally permissive:
Get-CalendarProcessing -Identity boardroom@yourcompany.com |
Select AutomateProcessing, AllBookInPolicy, AllRequestInPolicy
You will typically see AutomateProcessing: AutoAccept and AllBookInPolicy: $true. That means any internal user who invites the room gets an instant confirmation if the slot is free. For most everyday meeting rooms, this is exactly what you want — leave it alone.
Restricting who can book
To limit a room to a specific group — say only the sales team may book the demo suite — turn off the blanket policy and specify who is in-policy:
Set-CalendarProcessing -Identity demo-suite@yourcompany.com `
-AllBookInPolicy $false `
-BookInPolicy "sales-team@yourcompany.com"
Now requests from the sales distribution group are auto-accepted; everyone else is declined (or routed to approval, depending on the request settings). You can list multiple users or groups in BookInPolicy.
Delegate approval workflows
For high-value rooms — executive boardrooms, client spaces, all-hands rooms — you often want a person in the loop. Assign resource delegates and route requests to them:
Set-CalendarProcessing -Identity boardroom@yourcompany.com `
-AutomateProcessing AutoAccept `
-AllBookInPolicy $false `
-AllRequestInPolicy $true `
-ResourceDelegates "exec-assistant@yourcompany.com"
With this in place, in-policy requests may auto-accept while everything else lands in the delegate's inbox for approval. The delegate accepts or declines, and the requester gets the response. This is the right pattern when a room's calendar needs judgment, not just conflict-checking.
In-policy vs. out-of-policy requests
Two settings govern the edges:
AllRequestInPolicy— should out-of-policy requests (from people not on the allow-list) be forwarded to delegates rather than flatly declined? Set$trueto give non-privileged users a path to ask.ForwardRequestsToDelegates— controls whether requests are handed to delegates at all.
The mental model: in-policy requests can be auto-handled; out-of-policy requests can be declined outright or escalated to a human. You choose which.
How this interacts with display booking
This is where it gets practical. The Room Display lets people book a room right at the panel — Book Now, or a 15/30/60-minute quick button. That instant booking is only truly instant when the room auto-accepts.
- Auto-accept rooms: a tap at the display confirms the booking immediately and the panel flips to red. This is the ideal walk-up experience.
- Approval-gated rooms: a booking from the display becomes a request. The room will not confirm until the delegate approves, so the panel should not be treated as a guaranteed reservation for those rooms.
For that reason, we recommend approval workflows for a small number of special rooms and auto-accept for everything people walk up to. If you want instant booking to feel instant, keep your walk-up rooms on AutoAccept. For the deeper mechanics of walk-up reservations, see walk-in booking from the display.
The display account's own permissions
Separate from who can book, the account your displays sign in with needs to read the room calendar — and, for the snappiest instant booking, Full Access to the mailbox:
Add-MailboxPermission -Identity boardroom@yourcompany.com `
-User display-service@yourcompany.com `
-AccessRights FullAccess -InheritanceType All
The Room Display connects to Microsoft 365 over the Microsoft Graph API using OAuth (there is no Microsoft service-account option — that is a Google Workspace feature). Full Access lets a booking made at the panel write directly to the calendar instead of going through an invitation round-trip.
A sensible default policy
For most offices:
- Everyday rooms:
AutomateProcessing AutoAccept,AllBookInPolicy $true. Open, instant, no friction. - Restricted rooms:
AllBookInPolicy $falsewith aBookInPolicygroup. - Executive/client rooms: delegate approval via
ResourceDelegates. - Everywhere: cap
MaximumDurationInMinutesandBookingWindowInDaysto stop hoarding.
Frequently asked questions
What's the difference between AllBookInPolicy and BookInPolicy?
AllBookInPolicy $true means everyone in the org is in-policy. Setting it $false and populating BookInPolicy with specific users or groups restricts eligibility to just those members.
Can someone book a room from the display if it requires approval?
They can submit the booking, but it becomes a request, not a confirmed reservation. The room only turns "in use" once the delegate approves. Use auto-accept for walk-up rooms.
Do delegates need to be in the office to approve bookings?
No — approvals arrive as email in the delegate's inbox and can be actioned from Outlook anywhere. Just be aware that response time gates the booking.
Does restricting a room affect how it shows on the display?
No. The display always shows real-time availability regardless of who is allowed to book. Permissions only affect whether a given person's booking succeeds.
Where do I set all this?
In Exchange Online PowerShell via Set-CalendarProcessing. Some settings are also exposed in the Microsoft 365 admin center, but PowerShell gives you the full set of options.
Related guides
- How to Set Up Microsoft 365 Room Mailboxes
- Migrating Room Mailboxes from Exchange to Microsoft 365
- Walk-In Meeting Room Booking from the Display