Microsoft 365 Resource Mailbox Licensing: Room, Equipment, and Workspace Account Rules

Resource Mailboxes: The No-Licence Starting Point

Resource mailboxes — room mailboxes for meeting rooms, equipment mailboxes for shared assets like projectors and vehicles, and workspace accounts for flexible working environments — begin life as zero-cost objects in a Microsoft 365 tenant. Unlike user mailboxes and shared mailboxes, resource mailboxes are designed to be used by automated booking systems rather than by humans, and Microsoft's licensing model reflects that distinction.

A standard room or equipment mailbox requires no M365 licence. It maintains a calendar, accepts and declines meeting requests automatically based on configured rules, and can send booking confirmations. For straightforward room booking across hundreds of meeting rooms, the licence cost is zero.

Where cost enters the picture is when you add intelligence to those rooms (Teams Rooms devices), need flexible working support (workspace accounts with hot-desk booking), or apply compliance requirements to resource mailbox calendars and histories. Each of those scenarios has specific licensing requirements that are frequently underestimated — particularly as organisations modernise their physical workspace environments post-pandemic.

Room Mailboxes: What You Get for Free

A room mailbox in Exchange Online provides automatic booking management: it accepts or declines meeting requests based on availability, enforces booking rules (lead time, duration limits, recurring booking rules), sends booking confirmation emails, and appears in the room directory for the organisation's calendar clients. All of this works without any assigned M365 licence.

Room mailboxes can be managed by room delegates — individuals who handle exception requests or VIP bookings — without any additional licensing requirement for the mailbox itself. The delegates must hold their own user licences to access their email and calendars, but the room mailbox they manage requires no additional licence.

The practical limit for unlicensed room mailboxes is storage. Like shared mailboxes, room mailboxes default to a 50GB storage limit. For calendars, this storage is consumed by meeting bookings, recurring events, and any attachments. In practice, a typical meeting room calendar rarely approaches this limit — most organisations with hundreds of room mailboxes will never trigger the storage threshold from calendar data alone.

Equipment Mailboxes: The Same Framework

Equipment mailboxes follow identical licensing rules to room mailboxes. An equipment mailbox for a projector, company car, portable conference system, or any other shared asset that requires booking management requires no licence for basic functionality. It maintains a calendar, accepts bookings, enforces scheduling rules, and sends confirmations — all licence-free.

The equipment mailbox scenario where licensing sometimes surfaces is when the equipment item itself runs an M365-connected service. A shared video conferencing system that connects to Teams and uses a shared account, for example, may require a specific licence depending on how it accesses the Teams service. Standard equipment mailboxes without device integration remain licence-free.

Teams Rooms: Where Resource Licensing Gets Expensive

This is the area of resource mailbox licensing that consistently surprises organisations. When you deploy Microsoft Teams Rooms (MTR) — the hardware and software system that brings Teams into physical meeting rooms via dedicated devices — each room requires its own Teams Rooms licence. The room mailbox itself remains free; it is the Teams Rooms software and its access to Teams meeting features that requires the licence.

Teams Rooms licences come in two tiers:

Licence	Approx. Price / Room / Month	Key Capabilities	Best For
Teams Rooms Basic	Free (up to 25 rooms)	Join Teams meetings, basic meeting controls, room calendar	Small organisations, basic meeting rooms up to 25 rooms total
Teams Rooms Pro	~£14–16 / room / month (EA)	Intelligent speaker recognition, AI-enhanced meeting features, Intune management, conditional access, Microsoft 365 Copilot support, advanced analytics	Enterprise deployments, managed rooms, executive suites, any deployment requiring security and compliance controls

Teams Rooms Basic is limited to 25 rooms per tenant before Teams Rooms Pro becomes mandatory. For any enterprise with more than 25 meeting rooms running MTR hardware, Teams Rooms Pro is the only option. At approximately £14–16 per room per month across a 200-room estate, this represents £33,600–38,400 per year in Teams Rooms Pro licensing alone — before considering the hardware cost of the MTR devices.

Teams Rooms Pro vs Individual User Licences

A common question is whether a Teams Rooms device can share a user's M365 licence. The answer is no. Microsoft's Teams Rooms product requires a dedicated Teams Rooms licence assigned to the resource account used by the device. Assigning a user's M365 E3 or E5 licence to a Teams Rooms resource account is a licence violation and will eventually be flagged in a SAM engagement or audit.

Teams Rooms Pro includes a subset of Microsoft 365 functionality appropriate for a shared room device — Teams, Exchange calendar integration, and the Pro management capabilities — but it is not interchangeable with user licences. Some organisations attempt to use Microsoft 365 F1 or F3 (frontline worker) licences on Teams Rooms accounts to reduce cost. This is also non-compliant and Microsoft is increasingly identifying these configurations in SAM engagements.

Workspace Accounts: The Hot-Desk Licensing Complexity

As hybrid working became standard, Microsoft introduced the concept of workspace accounts — a specific account type designed for hot-desk and flexible working environments where employees book a physical desk or workspace through the same calendar mechanism as meeting rooms. A workspace account is provisioned as a resource mailbox, but it carries different licensing requirements depending on how it is used.

When Workspace Accounts Are Free

A workspace account used purely as a bookable resource — where employees use their own devices and accounts to book a desk, and the workspace account simply manages the booking calendar — requires no additional licence. The workspace account functions identically to a room mailbox in this scenario: it accepts and declines booking requests, enforces rules, and maintains a calendar.

When Workspace Accounts Require Licences

Licensing requirements emerge when the workspace account is used to provide a computing environment to the employee at the desk. If the workspace includes a shared PC where employees sign into their personal accounts via the workspace account context — particularly relevant for hot-desk stations with docked monitors and keyboards — then the workspace account may be associated with a shared device configuration requiring a Microsoft 365 licence.

Microsoft Places (the intelligent building and workplace management feature added to M365 in 2024) deepens the workspace account integration. Microsoft Places features that provide location sharing, colleague presence for physical workspaces, and desk-specific content surfacing require M365 E3/E5 for the employee users accessing those features — not the workspace account itself. However, the Microsoft Places Essentials and premium offerings add per-user costs that apply to employees who use the intelligent workspace features.

Compliance Requirements on Resource Mailboxes

Resource mailboxes are sometimes overlooked in compliance programmes. The assumption is that meeting room and equipment calendars contain no sensitive data. For most organisations this is true — a standard meeting room booking carries the meeting title, attendees, and time slot. That data is rarely subject to compliance holds.

However, for certain industries and for specific high-value meeting rooms (boardrooms, sensitive discussion rooms, executive suites), there may be a genuine compliance requirement to retain and hold meeting calendar data. This applies most commonly in financial services, legal, and regulated industries where the existence of certain meetings — board meetings, regulatory reviews, M&A discussions — must be demonstrable.

Placing a resource mailbox under Litigation Hold follows the same licensing rule as shared mailboxes: Exchange Online Plan 2 must be assigned to the resource mailbox. Without that licence, the hold will not function correctly. The same applies to eDiscovery holds placed through Microsoft Purview.

For organisations that need to retain meeting room calendar data but not necessarily under active litigation hold, a retention policy can be applied to Exchange items (including resource mailbox calendar items) without a per-resource-mailbox licence requirement, provided the retention policy is applied at the tenant or Exchange level through Purview Data Lifecycle Management. This is the more cost-effective path for organisations whose compliance requirement is retention rather than hold.

See the Microsoft 365 retention policies guide for guidance on applying retention to Exchange items across mailbox types.

The Booking Systems Landscape: Beyond Basic Calendar

Microsoft provides two distinct approaches to resource booking, and choosing between them has licensing implications.

The native Exchange/Outlook resource booking system (using room and equipment mailboxes) is licence-free at the resource level. It is well-suited to standard meeting room booking where Outlook calendar integration is sufficient.

Microsoft Bookings (available in M365 Business Standard and above, and M365 E3/E5) provides a more feature-rich booking experience with external-facing booking pages, appointment scheduling for services, and Bookings with Me for individual professional scheduling. Bookings operates on a per-user licence model — the staff members who use Bookings need qualifying M365 licences — but does not require additional resource mailbox licences beyond the base booking infrastructure.

Microsoft Bookings is sometimes confused with resource mailbox booking. They solve related but different problems: resource mailboxes manage shared physical assets; Bookings manages service appointments and professional scheduling. Understanding which scenario applies to your organisation determines whether additional licensing is required.

Resource Mailbox Count and True-Up

Resource mailboxes without assigned licences do not contribute to your M365 true-up count. Teams Rooms Pro licences assigned to room accounts do count. Microsoft Places licences count on a per-user basis. Workspace accounts with Exchange Online Plan 2 or higher assigned count.

The true-up risk for resource mailboxes is primarily Teams Rooms Pro licence compliance — organisations that deployed MTR hardware before formalising the Teams Rooms Pro licensing agreement, or organisations that provisioned Teams Rooms accounts using M365 F1 or shared user licences as a cost-saving measure. Both configurations are non-compliant and increasingly visible to Microsoft's commercial compliance team.

For the broader context of how resource and shared mailbox decisions interact with your M365 EA, see the shared mailbox licensing guide and the Exchange Online licensing guide.

EA Negotiation: Room Counts as Volume Leverage

If your organisation is deploying Teams Rooms Pro at scale — 50+ rooms — the room licence count becomes a negotiating variable in your EA. Teams Rooms Pro licences are line items in the EA price sheet, and volume tiers apply. A deployment of 200+ rooms at a single renewal is a negotiation opportunity: you should be asking for discounts of 12–20% below list price on Teams Rooms Pro, particularly if you are simultaneously renewing M365 and Azure commitments.

Teams Rooms Pro is also a product where Microsoft is under competitive pressure from Zoom Rooms, Cisco Webex Devices, and Google Meet hardware. If your organisation has hybrid conferencing infrastructure that includes non-Microsoft endpoints, use the competitive deployment as leverage when negotiating Teams Rooms Pro pricing. The presence of competing room systems is an active discount driver in EA room licensing negotiations.

For a broader view of how individual M365 product negotiations interact with your overall EA commercial position, see the Microsoft EA negotiation complete guide.

Summary: Resource Mailbox Licensing Decision Framework

Scenario	Licence Required?	Recommended Licence
Room mailbox — calendar booking only	No	None
Equipment mailbox — asset booking only	No	None
Room mailbox — Litigation Hold / eDiscovery hold	Yes	Exchange Online Plan 2
Room mailbox — archiving required	Yes	Exchange Online Plan 2 or Plan 1 + EOA
Teams Rooms device (MTR) — up to 25 rooms	Basic (free)	Teams Rooms Basic (free, limited to 25 rooms)
Teams Rooms device (MTR) — 26+ rooms, enterprise management	Yes	Teams Rooms Pro (~£14–16/room/month)
Workspace account — desk booking only	No	None (resource mailbox functions)
Workspace account — Microsoft Places intelligent features	User licence	M365 E3/E5 for the employees using Places features

Frequently Asked Questions

Can I use a Microsoft 365 F1 licence on a Teams Rooms resource account to save cost?

No. Microsoft's licensing terms require Teams Rooms Pro (or Teams Rooms Basic for the first 25 rooms) for MTR devices. Using F1 or other user-type licences on Teams Rooms accounts is a licence violation. Microsoft's SAM engagement programme and commercial compliance reviews are increasingly identifying these configurations. The cost of non-compliance discovered in an audit significantly exceeds the licensing savings.

How many room mailboxes can I have in a tenant?

Microsoft does not impose a specific limit on room mailboxes. You can create as many as your tenant supports. There is no per-room licence requirement for standard room mailbox functionality regardless of quantity.

Does the Teams Rooms Pro licence include Teams audio conferencing?

Teams Rooms Pro includes the standard Teams meeting joining capability. For dial-in conferencing (PSTN audio conferencing), a separate Audio Conferencing licence or Teams Calling Plan must be assigned to the resource account, or you can use Direct Routing. Teams Rooms Pro does not bundle telephone calling capabilities.

Are workspace accounts subject to Intune compliance policy?

Workspace accounts used for room/desk booking only (without a managed device enrolled) do not typically require Intune management. Teams Rooms Pro includes Intune management capabilities for the MTR devices themselves. If a workspace station is a shared managed PC enrolled in Intune, the device enrolment follows standard Intune licensing rules (M365 E3/E5 or Intune standalone).