How do we handle common area and lobby phones with Teams?

Key facts

• Common area phones sign in with a dedicated account, not a person's account.
• The Teams Shared Devices license is designed for these accounts; a PSTN connection is still needed for outside calls.
• Common area mode gives a simplified dial pad interface suited to lobbies, break rooms and warehouses.
• Shared devices cannot answer MFA prompts, so Conditional Access needs a device-based approach for them.
• Every shared phone needs an emergency location so 911 calls send the right address.

Where common area phones fit

Most Teams users answer calls on a laptop or mobile. Some places still need a fixed phone that anyone can pick up: lobbies, reception desks when unstaffed, break rooms, warehouses, labs, loading docks and conference rooms without Teams Rooms. These are common area phones.

In Teams, a common area phone is a certified Teams phone signed in with an account that represents the location rather than a person. It can make and receive calls, join call groups or queues, and use call park and pickup, but it does not carry a person's mailbox, chats or files.

Accounts and licensing

Create one account per phone with a clear naming convention, such as a site and location code. Assign the Teams Shared Devices license, which is built for shared phones and displays, then connect it to the PSTN the same way you do for users: a Calling Plan, Operator Connect or Direct Routing number.

Keep these accounts in a dedicated group so policies, Conditional Access and licensing can target them as a set. Do not reuse a former employee's account or a regular user license; it complicates audit and offboarding.

• One account per phone, named by site and location.
• Teams Shared Devices license plus a phone number.
• A dedicated group for policy and Conditional Access targeting.
• An owner responsible for each shared device.

Sign in and device mode

Certified Teams phones can be signed in on the device itself or remotely from the Teams admin center using a provisioning code, which saves a trip to each location. An IP phone policy set to common area sign-in mode gives the phone a simplified interface focused on dialing, rather than a full user experience.

Manage the phones in the Teams admin center: firmware updates, configuration profiles, and health status. Hot desking can let a user sign in temporarily on a shared phone and return it to common area mode afterward, which suits hybrid offices with shared desks.

Restrict calling and secure the account

A lobby phone should not be able to call anywhere in the world. Use calling restrictions to limit it to internal extensions, local and national numbers, or emergency calls only, depending on the location. With Calling Plans, outbound dial-out policies restrict call types; with Direct Routing, voice routing policies control which routes the phone can use.

Shared accounts cannot answer an MFA prompt, so standard user Conditional Access policies will lock them out. Create a policy for the shared device group that relies on device compliance and trusted locations instead, and exclude the group from user MFA policies with that control in place. Use long, unique passwords stored securely, and review sign-in logs for these accounts.

Emergency calling and analog devices

Assign every shared phone to an emergency location, and use network-based dynamic emergency calling where your network is mapped. A lobby phone is often where a visitor dials 911, so test it and confirm the address and any internal notification to security.

Analog phones such as elevator phones, door entry, fax and paging cannot sign in to Teams. Connect them through an analog telephone adapter with Teams SIP Gateway or Direct Routing, or through your operator's analog line service. Inventory these early, because they often drive the PSTN choice.

How Accred Consulting approaches it

Accred Consulting plans common area phones as part of a Teams Phone project. Discovery inventories every shared location, analog device and call flow, and the proposal sets scope, fixed price and timeline. The US-based specialists assigned to your engagement create shared accounts and groups, assign licensing and numbers, configure common area mode, calling restrictions and Conditional Access for shared devices, and set emergency locations. In one engagement, four sites moved from a PBX to Teams Direct Routing, pilot site first and HQ last. Handover includes documentation and knowledge transfer, with optional support retainers.

Track record: 475+ client projects, 2,000+ migration workstreams and 210,000+ users migrated by a US-based team. Company facts · Case studies

Related questions