Microsoft Teams desk phones

Choose the position before the hardware

Decide whether the phone is assigned to one person, placed in a common area, used as a meeting-room companion or offered for hot desking. Those workloads have different identity, sign-in, directory, calling and privacy requirements. A touchscreen size or number of keys cannot resolve that operating decision.

For a shared position, document who may sign in, what directory and call history may appear, whether emergency and external calling are required, and how the account is recovered. Microsoft currently describes common-area phones as certified Teams devices signed in with a resource account; that account, licence and PSTN configuration are separate from the handset purchase.

The Yealink MP52 E2 provides a current Android 15 common-area example with physical keys and a compact non-touch display. Its exact-model evidence also prevents Wi-Fi, Bluetooth or expansion features from being inherited from larger MP E2 siblings.

For a touch-screen desk or reception position, the Yealink MP56 E2 provides a current Android 15 example with Wi-Fi, Bluetooth and an optional EXP50 expansion path. Those interfaces do not replace exact accessory, policy, power and key-workflow acceptance.

Separate Teams certification from generic SIP capability

Use Microsoft's current certified-hardware list to verify the exact model, Android generation, certification reference firmware and certification end date. Certification is tied to an Android operating-system version and has a lifecycle; it is not a permanent property of a family name. Microsoft says it supports the Teams application on a certified Android version for two years after that certification period ends, but the current list and policy can change.

Some manufacturer pages also describe SIP registrations, codecs or security protocols. Do not infer that a Teams-configured device or orderable SKU can be moved to an arbitrary SIP PBX. Confirm the exact part number, software mode, conversion entitlement, administrator documentation and calling-platform support before procurement or reprovisioning.

For current Poly examples, compare the CCX 350 physical-dial-pad reference with the CCX 400 touch-interface reference. They share Microsoft's listed Android 12 certification family at review, but interface, ports, part numbers and acceptance needs remain exact-model decisions.

Plan identity, licence and PSTN service together

Assign the intended Teams account type and usage location before sign-in, then apply the licence required for that workload. Microsoft renamed the Teams Shared Devices licence to Teams Shared Space before April 2026; current documentation says one licence enables one device for common-area phone use. Treat that statement as current service documentation, not a price or perpetual entitlement.

If the position needs public calling, provide an applicable PSTN connection and number according to the tenant design. Prove inbound, outbound and emergency behavior in the actual location. A signed-in phone does not establish that normalization, caller identity, policy, location information or emergency routing is correct.

Apply common-area sign-in and policy deliberately

For a common-area resource account, Microsoft documents the Teams IP phone sign-in mode CommonAreaPhoneSignIn. It also documents remote, local and Teams admin center sign-in paths. Conditional Access and multifactor authentication can affect device sign-in, so align security policy with the supported device workflow rather than weakening controls during deployment.

Use Teams phone policies to expose only the intended directory and features, and decide whether hot desking is permitted. Microsoft notes that policy changes can take time to apply and may require sign-out and sign-in. It also warns that presence-based call-queue routing is not supported reliably for common-area phone accounts; design shared-line and queue behavior from current service documentation and a tenant pilot.

Control firmware and application updates in rings

Record the phone model, Android version, installed firmware, Teams client and Microsoft application versions at acceptance. Compare them with Microsoft's current device and firmware tables, then use representative pilot, limited and broad rings for updates. The latest version published by Microsoft is not proof of the version installed on a particular phone.

Test cold boot, sign-in, directory access, inbound and outbound calls, hold, transfer, voicemail, headset behavior, power recovery and the required shared-space controls. Keep a rollback or replacement path for a device that no longer meets certification, application or tenant requirements.

Keep the evidence boundary visible

Certification, product specifications and tenant documentation establish documented capabilities and current service rules. They do not prove stock, price, accessory inclusion, local network quality, tenant compatibility, PSTN availability, audio quality, policy propagation or remaining support life. Recheck the live Microsoft certification and firmware lists and the exact manufacturer part number at every purchase or material change.

Do not collapse certification and public-cloud firmware

The AudioCodes C470HD has a Microsoft certification reference and a later public-cloud firmware line. Capture Android, phone firmware and bundled Teams, Intune, Authenticator and Admin Agent versions from the actual handset; neither table alone proves installed state or tenant approval.

Match AudioCodes physical-key and touch models to the position

The AudioCodes C435HD provides a current physical-key example for personal or shared positions. The C455HD provides a touch model with an exact DBW-only expansion path. For either, the certified model, account, licence, policy, firmware and PSTN service remain separate acceptance records.

Compare current AudioCodes shared-position and MDEP options

The C436HD is a current physical-control common-area example with an integrated sidecar. The C456HD is a current Android 13 MDEP example with a programmable action input and optional G2 module. For either, certification, account, licence, policy, installed bundle and PSTN acceptance remain separate records.