The Core Problem: Per-User Licences on Shared Devices

Shared devices — common area phones in building lobbies, Teams panels outside meeting rooms, Teams displays at hot-desking stations, kiosk touchscreens in warehouses — do not represent individual users. They are infrastructure. Assigning a full Microsoft 365 E3 or E5 licence to a shared device is functionally equivalent to buying a first-class airline ticket for a piece of equipment: the equipment only needed a freight booking.

Yet this is exactly what many organisations do. In the rush to deploy Teams telephony and meeting room technology, IT departments create user accounts for shared devices, assign them M365 E3 licences to get Teams functionality, and move on. The cost consequence: a £30.10/user/month E3 licence (at EA pricing) assigned to a lobby phone that makes and receives calls and does nothing else, when the correct licence — the Microsoft Teams Shared Device plan — costs approximately £2–3/device/month at EA pricing. That is a 90%+ overspend per device.

At scale, this matters. A 5,000-employee organisation with 200 shared devices (common area phones, panels, displays, hot-desking stations) that are incorrectly licenced at E3 is spending approximately £60,200/month on those devices — £36,000/month more than necessary. Over a three-year EA: £1.3M in unnecessary spend, for devices that will never use 95% of what an E3 licence provides.

The Microsoft 365 Teams Shared Devices plan: The Teams Shared Devices plan (sometimes called Teams Shared Device) is a purpose-built licence for shared physical endpoints. It provides Teams calling and meeting functionality on the device — without user-specific capabilities like personal mailboxes, OneDrive storage, SharePoint access, or Copilot. At approximately £2–3/device/month at EA pricing, it is the correct commercial choice for any device that is used by multiple people or as a room/space identifier rather than as an individual user endpoint.

Shared Device Types and Correct Licensing

Device Type Correct Licence Common Mistake Annual Saving per Device vs E3
Common area phone (lobby, reception, break room) Teams Shared Devices (~£2–3/month) M365 E3 or O365 E3 assigned to a user account ~£324–336/device/year
Teams panel (room booking panel outside meeting rooms) Teams Shared Devices OR Teams Rooms Basic (free, 25-room limit) M365 E3 user account; or Teams Rooms Pro unnecessarily ~£192–336/device/year vs Teams Shared vs E3
Teams display (hot-desking endpoint with touchscreen) Teams Shared Devices M365 E3 user account ~£324–336/device/year
Hot-desking workstation (sign-in to personal account) No device licence needed — user's own M365 licence covers usage Duplicate device account + E3 in addition to user E3 Full E3 saving per device account — ~£361/year
Kiosk/frontline shared device (warehouse, retail) M365 F1 (~£2.25/month) or M365 F3 (~£7.20/month) depending on app needs M365 E3 for frontline workers who share devices Up to £339/user/year (E3 vs F1)
Teams Rooms device (meeting room AV system) Teams Rooms Basic (free, ≤25 rooms) or Teams Rooms Pro (~£14–16/room/month) Teams Shared Devices plan (insufficient for full room features) N/A — Teams Rooms Pro is justified for conferencing AV

Common Area Phones: The Biggest Per-Unit Saving

Common area phones are the most straightforward shared device category. A physical phone installed in a building lobby, warehouse floor, break room, or reception desk makes and receives calls, potentially accesses a Teams meeting, and has no individual user identity. The Teams Shared Devices plan provides exactly this: PSTN calling capability, basic Teams access, and device management through the Teams Admin Centre. Nothing else is needed, and nothing else should be paid for.

The Teams Shared Devices licence also requires a Teams Phone add-on (Teams Phone Standard, approximately £7–9/month at EA pricing) if the device needs PSTN calling capability — inbound and outbound calls to phone numbers. If the device only needs internal Teams-to-Teams calling and meeting joining, no Teams Phone add-on is required. For common area phones in lobbies that primarily receive external calls, include the Teams Phone Standard add-on in your cost model.

Teams Panels: The Free Tier First

Teams panels are the touchscreen devices typically mounted outside meeting rooms to display room booking status, check room availability, and allow ad-hoc meeting reservations. The correct licence depends on your room count and management requirements. Teams Rooms Basic — the free tier of Teams Rooms licensing — supports up to 25 rooms, includes basic room booking management, and uses a Teams Shared Device account. For organisations with fewer than 25 meeting rooms, Teams Rooms Basic provides the panel functionality at no licence cost beyond the device account.

For organisations exceeding the 25-room free tier threshold, Teams Rooms Pro (~£14–16/room/month at EA) provides the full panel functionality plus the Teams Rooms Pro Management portal, AI meeting features, and advanced analytics. The step from free to £14–16/month is significant — ensure you genuinely need Pro features (remote device management at scale, AI features, advanced analytics) before moving beyond the free tier for your panel deployment. See our guide to Teams Rooms licensing for the full Basic vs Pro analysis.

Teams Displays and Hot-Desking

Teams displays are small personal touchscreen devices designed for desk use — they show Teams status, meetings, and calls. In a hot-desking environment (where multiple workers use the same physical desk on different days), Teams displays typically operate in one of two modes:

Shared mode (Common Area configuration): The device is permanently configured with a Teams Shared Devices account. Users interact with the device for basic functionality — calling, joining meetings from the shared account — without signing into their personal account on the device. This is appropriate for shared desk spaces where personal identity on the device is not required. Licence: Teams Shared Devices plan.

Hot-desking mode (personal sign-in): The user signs into their personal Microsoft account on the Teams display for their session and signs out when they leave. The device uses the user's own M365 licence during the session — no separate device account or device licence is needed. The Teams display hardware supports hot-desking sign-in natively. Licence: the user's existing M365 E3/E5 — no incremental device cost.

Hot-desking and duplicate accounts: The hot-desking over-spend pattern occurs when IT creates a user account for a hot-desking Teams display (requiring a device licence) in addition to the user signing into their personal account on the device. The device account is unnecessary in hot-desking mode — the user's personal licence covers the session. The device account should only exist if the display is operating in permanent shared mode. Auditing your Teams device accounts for hot-desking displays with both device accounts and regular user sign-in is a quick source of licence savings.

The Teams Shared Devices Plan: What It Includes and Excludes

Understanding what the Teams Shared Devices plan covers — and does not cover — is essential to confirming it is the right licence for each device type.

Capability Teams Shared Devices M365 E3 (for comparison)
Teams calling (Teams-to-Teams) Yes Yes
Teams meetings (join) Yes Yes
PSTN calling (requires Teams Phone add-on) Yes — with Teams Phone Standard add-on Yes — with Teams Phone Standard add-on
Teams chat Basic — device-level, not personal identity chat Yes — full personal chat
Exchange Online mailbox No Yes — 100GB mailbox
OneDrive storage No Yes — 1TB
SharePoint access No Yes
Microsoft 365 Apps (Office) No Yes
Intune device management Yes — Intune Plan 1 included Yes — via Intune Plan 1 in E3
Teams Admin Centre management Yes — full device management Yes
Entra ID (basic) Yes Yes
M365 Copilot capability No No — requires Copilot add-on

The exclusion of Exchange Online, OneDrive, and Microsoft 365 Apps is precisely what makes the Teams Shared Devices plan appropriate for shared physical endpoints — and inappropriate for individual users. A common area phone does not need a personal mailbox. A lobby display does not need OneDrive storage. A hot-desking station in shared mode does not need Office apps installed. The Teams Shared Devices plan is not a lesser licence; it is a correctly scoped licence for the specific use case.

The Frontline Shared Device Use Case

Frontline workers — warehouse operatives, retail floor staff, healthcare aides, field service teams — frequently share mobile devices or fixed stations rather than having dedicated personal endpoints. This is a different use case from common area phones and room equipment, but it also has licensing implications that differ from standard per-user M365 E3 deployment.

For frontline shared device deployments where individual workers sign into the device under their personal accounts (using their F1 or F3 licence), no shared device licence is required — the personal licence covers the usage. Where devices are configured in shared device mode (a single device account is signed in permanently and individual workers use it without personal sign-in), the M365 F1 plan at approximately £2.25/user/month covers the basic frontline shared device scenario with Teams access, Shifts, and limited Outlook capability.

The important distinction is whether individual worker identities need to be tracked at the device level. Compliance, audit, and accountability requirements in regulated industries often require individual sign-in — in which case personal F1 or F3 licences per worker are the correct architecture, even if those workers share devices. See our guide to M365 kiosk and frontline licensing for the full F1/F3/shared device analysis in frontline contexts.

How to Audit and Right-Size Shared Device Licences

Identifying incorrectly licenced shared devices requires a cross-reference between Teams device management data and the M365 Admin Centre licence assignment records. The process has four steps:

Step 1: Export Teams device inventory. From the Teams Admin Centre, export the full device list including device type (phone, display, panel, Teams Rooms) and the user account each device is signed in with. This gives you the complete shared device population.

Step 2: Identify device accounts in M365 Admin Centre. Cross-reference device account names from the Teams export against the M365 Admin Centre licence assignment. Identify device accounts that hold M365 E3, M365 E5, O365 E1/E3, or other per-user suite licences when only Teams Shared Devices plan is required.

Step 3: Identify hot-desking displays with redundant device accounts. For Teams displays, check whether devices in the inventory are operating in hot-desking mode (personal sign-in) while also maintaining a device account with a licence. These device accounts — and their licences — are unnecessary and can be decommissioned.

Step 4: Transition incorrectly licenced devices. For devices identified as needing the Teams Shared Devices plan, create Teams Shared Device accounts, configure the devices under the correct account type, and revoke the incorrect per-user licences. Add Teams Phone Standard add-ons for devices requiring PSTN calling. Document the transition for the licence compliance record and reflect the reduced count in your next EA true-up.

EA Negotiation Considerations for Shared Devices

The primary commercial opportunity in shared device licensing is count reduction at EA renewal — replacing incorrectly assigned E3/E5 licences with Teams Shared Devices plan licences. This reduces the total committed count for M365 E3/E5, which affects the EA value and potentially the volume discount tier. See our guide to EA volume discount tiers for the threshold mechanics.

When negotiating Teams Shared Devices plan pricing specifically, the lever is volume commitment. The plan is not one of the heavily negotiated line items in most EA discussions — Microsoft pricing teams expect it to be a small-volume, operational line item. For organisations with large shared device estates (hundreds of devices), bundling the Teams Shared Devices commitment with the broader M365 negotiation and requesting alignment on volume discount tier inclusion can secure better pricing on the plan itself.

The Teams Phone Standard add-on (required for PSTN calling) is the higher-value line item — at approximately £7–9/month per device at EA pricing, a 200-device shared phone estate adds £16,800–21,600/year in Teams Phone add-on cost. This is worth negotiating as part of a broader Teams Phone deployment discussion, where the volume across individual user Teams Phone licences and shared device Teams Phone add-ons creates consolidated volume that justifies better pricing.

Get Microsoft Licensing Intelligence Weekly

Independent analysis on M365, Teams, and EA negotiation — direct to your inbox every week.

No spam. Unsubscribe at any time.

Frequently Asked Questions

Can I use the Teams Shared Devices plan for a phone that only needs internal calls?

Yes. The Teams Shared Devices plan without a Teams Phone add-on provides Teams-to-Teams calling within your organisation and the ability to join scheduled Teams meetings. If the device only needs internal calls — for example, a break room phone used to contact reception or facilities — no Teams Phone add-on is required. The Teams Phone Standard add-on is only needed when the device must make or receive calls to external PSTN numbers.

Does the Teams Shared Devices plan include Intune for device management?

Yes — the Teams Shared Devices plan includes Intune Plan 1. This allows the shared device account to be enrolled in Intune for device configuration policy, compliance enforcement, and remote management through the Intune console. This is operationally important for organisations managing large shared device estates — Teams devices enrolled in Intune can receive configuration updates, certificate deployments, and compliance policies from the same management infrastructure as personal user devices. The Intune inclusion eliminates the need to purchase a separate Intune licence for shared device accounts.

What happens at M365 EA renewal if we have shared devices on E3 licences?

The incorrectly licenced devices count toward your E3 commitment volume. If you reduce those devices to the Teams Shared Devices plan at renewal, your E3 count reduces — which may affect your volume discount tier. Model the tier impact before submitting the renewal position: if removing 200 E3 shared device licences drops your total M365 commitment below a tier threshold, the per-unit price on all remaining E3 licences may increase, potentially offsetting some of the direct saving. A full renewal modelling exercise — as described in our EA renewal preparation guide — accounts for this tier interaction.

Shared device licensing is a common source of avoidable EA spend

We audit your M365 deployment and identify shared device accounts incorrectly licenced at E3 — typically saving £300–400 per device per year. 500+ engagements. $2.1B managed. 32% average cost reduction.

Book a Free Licensing Review

M365 Cost Optimisation White Paper

12 proven strategies for reducing M365 licensing costs — including shared device right-sizing, licence harvesting, and SKU rationalisation.

Download the guide →