IT Admin's Guide to Meeting Room Setup (2026) · Lobby

If you have ever inherited a meeting room setup that "mostly works", you know the feeling. Bookings happen. Room Finder shows something. The displays mostly tell the truth. But three rooms have weird capacity, the boardroom keeps double-accepting recurring meetings, and a room in the back is somehow listed twice in two different buildings.

This is the IT admin's hub. The order you would actually do the work, with every deep dive linked through. If you read it end to end and follow the steps, you can take a messy meeting room setup and make it boring. Boring is the goal.

The five layers, in order

Meeting room setup is a stack. Each layer depends on the one below. If a higher layer is misbehaving, the fix is almost always in a lower layer.

Directory and identity. The rooms exist as resources in your tenant or Workspace.
Place metadata. Building, floor, capacity, AV features are correctly labelled.
Calendar processing rules. Auto-accept, booking window, decline rules, delegates.
Client surfacing. Outlook Room Finder, Google Calendar's room suggestion, Room Finder on mobile.
Display layer. The screens outside the doors, the auto-release rules, the check-in flow.

Most of the "weird behaviour" people see at layer 4 or 5 is actually a bug at layer 1 or 2. Start at the bottom.

Layer 1: Directory and identity

The first thing every room needs is to exist properly in the directory. In Microsoft 365 this is a room mailbox. In Google Workspace it is a Calendar resource attached to a building.

The two checklists for the two platforms, written for IT admins who want to do this once and not have to come back:

The biggest mistake at this layer is creating rooms ad-hoc without building hierarchy. Without buildings, Room Finder cannot group rooms, capacity searches fail, and any vendor that uses Place data (Joan, Robin, Lobby) gets weird suggestions.

Layer 2: Place metadata

Once the room exists, the metadata matters more than people realise. The room name is what shows on the door. The capacity is what determines whether Outlook will suggest it. The features (AV, accessibility, whiteboard) drive the smart suggestions in both Outlook and Google.

In M365, this lives in Set-Place. In Google Workspace it lives in the Admin Console under Buildings and Resources. The cheat sheet:

Set-Place -Identity "library@yourdomain.com" `
  -Capacity 6 `
  -Building "HQ" `
  -Floor 2 `
  -AudioDeviceName "Logitech Rally" `
  -VideoDeviceName "Logitech Rally Bar" `
  -DisplayDeviceName "Samsung 55 inch" `
  -IsWheelChairAccessible $true

If Outlook Room Finder is showing nothing, the problem is here, not in the calendar processing. The Outlook Room Finder fix post walks through the eight common causes.

Layer 3: Calendar processing rules

Now the room can be booked. The question is how. Auto-accept on or off. Recurring allowed. Booking window 60 days or 180. Conflicts permitted or not.

For Microsoft 365, this is Set-CalendarProcessing. The full configuration including the eight knobs that matter and the five that look important but usually do not: Room Mailbox Auto-Accept in Microsoft 365: Best Practices.

For Google Workspace, this is configured per-resource in the Admin Console under "Auto-accept invitations" plus the per-resource sharing settings. Less granular than M365 but covers the common cases.

A sensible default for both platforms:

Auto-accept on for most rooms.
Booking window 60 to 90 days.
Maximum duration 8 hours (drop the default 24 hours).
Conflicts not allowed.
Recurring meetings allowed, but capped at 90 days.
Two delegates only for rooms that need a human in the loop.

This configuration handles 95 percent of cases without anyone having to think about it.

Layer 4: Client surfacing

Once rooms are bookable, people need to be able to find them. The two surfaces that matter:

Outlook Room Finder. Driven by Place metadata plus the Microsoft Places directory. If Room Finder is missing rooms or showing the wrong capacities, the fix is upstream (Place metadata, layer 2).
Google Calendar room picker. Driven by building hierarchy plus the resource's "available to the organisation" setting.

A surprising number of "I can't find the room when I create a meeting" tickets resolve to "the resource is shared with only specific people, not the whole organisation". Worth checking when complaints come in.

Layer 5: Display and check-in

The display outside the door is the visible layer. Most of the time, problems here trace back to layers 1 through 3. But the display layer has its own decisions.

Hardware choices, with deep dives:

Setup guides for common tablet platforms:

And the auto-release rules that turn the display from a passive screen into an active part of the booking flow: How to Release a Meeting Room Automatically.

The cross-cutting concern: security

Anything you put on the wall is connected to your network, holding access to your calendar, and possibly visible from outside the room. The security review is the same whether you build your own or buy a vendor:

Network segmentation. Displays go on the IoT VLAN, not the corporate one.
OAuth scopes. The vendor needs read-only calendar access for the rooms it manages. Read-write is required for auto-release and check-in.
MDM enrolment for tablets. Required for some sectors, nice to have for everyone.
Firmware updates for any non-tablet hardware (TRMNL, Joan, Robin Powered devices). Subscribe to vendor security advisories.
GDPR or local equivalent for booking data. Booking metadata (organiser email, subject line) is personal data. Vendor needs a DPA.

The full sysadmin's checklist for displays: Securing Your Meeting Room Displays.

The "I'm starting from a mess" workflow

If you have just inherited a meeting room setup that has been "managed" by three previous IT admins, here is the one-day cleanup that gets you back to a known-good baseline.

Inventory. Pull a list of every room mailbox or resource calendar. Note the building, capacity, AV features, and which displays (if any) are pointing at them. One spreadsheet, an hour of work.
Fix the directory layer. For each room, confirm it is in the right building, has the right capacity, and the right display name. Use Set-Place (M365) or the Admin Console (Google).
Apply a uniform calendar processing policy. Use the M365 PowerShell or Google per-resource setting from the relevant checklist. One policy, applied to every room, with documented exceptions for the boardroom.
Validate from a user account. Open Outlook (or Google Calendar) as a normal user. Open Room Finder. Confirm every room shows with the right capacity and features. This is the single most useful test you will run.
Check the displays. Walk past every meeting room. Confirm the display shows the right room, the right calendar, and the right capacity. Anything wrong is back to step 2.
Set the quarterly cleanup. Put a recurring calendar invite on yourself for the first Monday of every quarter. The operations playbook has the quarterly review checklist.

A day of focused work, and the system is then stable for months. The quarterly review keeps it that way.

The "I'm starting from scratch" workflow

If you are doing this for a new office (or you just got M365 / Google Workspace stood up), the right order is the reverse of the cleanup workflow. Build the layers from the bottom up.

Create the buildings and floors in the Admin Console.
Create the room resources (mailbox or Calendar resource) with the right naming convention. We have a naming framework if you have not decided.
Set the Place metadata (capacity, AV, accessibility) for each room.
Apply the calendar processing policy. Same default for every room, exceptions documented.
Test from a user account. Room Finder should show everything.
Pick a display platform and roll out displays starting with the busiest room.
Document the whole setup in one wiki page or Notion doc. Future you will thank you.

Each step is short. The whole thing is half a day for a 10-room office if you have the right access.

TL;DR

Meeting room IT setup is a five-layer stack: directory, place metadata, calendar processing, client surfacing, displays. Most "weird behaviour" at the display is actually a bug in the directory or metadata. Fix from the bottom up. Use one policy across all rooms with documented exceptions. Apply the appropriate platform checklist (M365 or Google Workspace) end to end. Validate by opening Outlook or Google Calendar as a normal user and confirming Room Finder works. Schedule the quarterly cleanup. Done well, this is half a day of work that you do not have to revisit for months.

The IT Admin's Guide to Setting Up Meeting Rooms (Microsoft 365, Google Workspace, and Everything in Between)