Microsoft Teams Admin Centre: Room Resource Management Guide
Managing meeting rooms through the Microsoft Teams admin centre room resources configuration is one of the more confusing aspects of Microsoft 365 administration – partly because room management spans multiple admin centres (Exchange, Teams, Entra ID) and partly because the documentation assumes a level of Exchange familiarity that not all IT administrators have. This guide consolidates the practical steps for configuring and managing meeting rooms in a Microsoft 365 environment from an IT administrator’s perspective.
Quick verdict
Room management in Microsoft 365 is handled primarily through Exchange Online resource accounts, not through the Teams admin centre itself. The Teams admin centre is where you manage Teams Rooms devices (the hardware running Microsoft Teams Rooms); the Exchange admin centre and Entra ID are where you manage the room mailboxes and resource accounts that calendar booking relies on. Understanding which admin centre handles which layer prevents a lot of the confusion that comes from searching in the wrong place.
The three layers of Microsoft room management
Layer 1: Room mailboxes (Exchange Online / Exchange admin centre)
A room mailbox is the Exchange object that represents a meeting room from a calendar perspective. When someone books “Conference Room B” in Outlook or Teams, they are sending a meeting invite to the room mailbox email address. The room mailbox auto-accepts or auto-declines the invite based on its booking policy configuration.
Key room mailbox settings (configured in Exchange admin centre or via PowerShell):
- AutoAccept: Whether the room automatically accepts booking requests without a human approval step. Usually set to true for standard rooms.
- MaximumDurationInMinutes: Maximum booking duration (default 1440 minutes / 24 hours). Set this to match your policy – a common setting is 480 minutes for standard rooms.
- BookingWindowInDays: How far in advance rooms can be booked. Default is 180 days; many organisations reduce this to 30-90 days.
- AllowConflicts: Whether double-bookings are allowed (should be false for standard rooms).
- RequestOutOfPolicy: Whether out-of-policy booking requests (outside the booking window, exceeding max duration) go to a delegate for approval or are auto-declined.
Layer 2: Resource accounts (Entra ID / Microsoft 365 admin centre)
For rooms running Microsoft Teams Rooms hardware, a resource account is required. A resource account is an Entra ID (formerly Azure AD) account paired with the room mailbox, specifically for device authentication. The Teams Rooms device signs in with the resource account credentials.
Resource account requirements:
- A Microsoft 365 account with a Teams Rooms licence assigned (Teams Rooms Basic is free for up to 25 rooms; Teams Rooms Pro is the paid tier for advanced features)
- The account must have a valid Exchange Online mailbox (either directly or via the room mailbox pairing)
- Password must not expire, or a rotation process must be in place for device re-authentication
- Multi-factor authentication must be excluded from the resource account (MFA blocks the device sign-in flow) – use a conditional access policy exclusion for resource accounts
Layer 3: Teams Rooms devices (Teams admin centre)
The Teams admin centre (admin.teams.microsoft.com) is where you manage Teams Rooms hardware after it has been provisioned. Functions available in the Teams admin centre for rooms:
- Device inventory and health status for all enrolled Teams Rooms devices
- Remote restart and configuration push
- Software update management (Teams Rooms app version, Windows/Android updates)
- Call quality diagnostics and analytics per room device
- Rooms Pro Management portal (if Teams Rooms Pro licences are assigned) – advanced monitoring, alerts, and analytics
Room lists: organising rooms for end users
Room lists are distribution groups in Exchange that group related room mailboxes (e.g. “Floor 3 Rooms” or “London Offices”). When a user books a room in Outlook or Teams, room lists are how they browse available rooms by location or floor. Creating room lists significantly improves the booking experience compared to manually searching for individual room mailbox addresses.
To create a room list via PowerShell:
New-DistributionGroup -Name "Floor 3 Rooms" -RoomList
Add-DistributionGroupMember -Identity "Floor 3 Rooms" -Member "room-floor3-a@yourdomain.com"
Add-DistributionGroupMember -Identity "Floor 3 Rooms" -Member "room-floor3-b@yourdomain.com"Room list membership should mirror your physical room layout. Adding all rooms to a single list defeats the purpose – users should be able to find rooms near their location quickly.
Common configuration issues and fixes
Room not appearing in the room finder
The room finder in Outlook and Teams only shows room mailboxes that are members of a room list. If a room is not in any room list, it will not appear in the room finder (though it can still be booked by entering its email address directly). Fix: add the room mailbox to an appropriate room list.
Booking request stuck as tentative
If meeting invites to a room appear as tentative rather than accepted, check that the room mailbox AutoAccept setting is enabled. If the room has a booking delegate configured (a human approver), invites queue as tentative pending delegate action. Verify the delegate configuration in Exchange admin centre: Rooms and equipment > select room > Booking delegates.
Teams Rooms device showing wrong room name
The room name displayed on the Teams Rooms touch panel comes from the Exchange resource account display name. If the display name on the resource account is incorrect or uses a different naming convention from the physical room signage, update the display name in Entra ID or the Microsoft 365 admin centre.
Teams Rooms device cannot sign in
The most common cause is a conditional access policy blocking the resource account sign-in. Check that the resource account is excluded from MFA-requiring conditional access policies. Also verify that the Teams Rooms licence is assigned and that the resource account password has not expired.
Integration with third-party room booking platforms
Third-party room booking platforms (Joan, Evoko, Logitech Tap Scheduler, Condeco, Robin, Skedda) integrate with Microsoft 365 room mailboxes via the Exchange API. Room bookings made in the third-party platform appear as accepted meetings in the room mailbox calendar; bookings made in Outlook or Teams appear in the third-party platform’s availability view. This bidirectional sync is the basis of all calendar-integrated room booking.
For organisations using a third-party booking platform alongside native Microsoft calendar booking, configure the room mailbox to auto-accept all invites from the third-party system’s service account to prevent permission conflicts.
Teams Rooms vs room panels: what the admin centre covers
The Teams admin centre manages Teams Rooms devices (dedicated room systems running the full Teams Rooms application on a Windows or Android device). It does not manage third-party room booking panels (Joan panels, Evoko panels, Logitech Tap Scheduler) – those are managed through their respective vendor management platforms. The distinction matters because some organisations run both: Teams Rooms in rooms used for external video calls, and third-party booking panels in rooms used primarily for in-person meetings.
Bottom line
Effective Microsoft room management requires working across Exchange, Entra ID, and the Teams admin centre as three separate but interdependent layers. The most common configuration issues stem from treating room management as a Teams-only task when the foundational configuration lives in Exchange. For related guidance, see our article on Microsoft 365 room booking integration and the Microsoft Places guide.
