HP Poly CCX 350 Microsoft Teams desk phone

Select the exact interaction model

HP positions the CCX 350 as a Microsoft Teams-integrated desk phone with a traditional physical dial pad. The data sheet lists a 2.8-inch 640 × 480 color LCD and a dedicated Teams button. Treat that as a different interaction model from the existing CCX 400, whose larger touch display changes navigation, accessibility and training assumptions.

Record the exact part number and user or shared-space workload before purchase. A physical keypad can be useful where tactile dialing is required, but its presence does not prove that font, contrast, prompts, handset, hearing-device behavior or task flow meets an individual user's accessibility needs. Run acceptance with intended users.

Separate certification, release and installed state

Microsoft listed the Poly CCX 350 with Android 12, certification reference firmware 9.0.0.10315 and an August 15, 2028 certification end date at review. Its public-cloud table separately listed 9.5.1.0067 (AOSP), released September 15, 2026, for the CCX 350/400/500/505/600 and Trio C60 group. Those are certification and release records, not proof of the build installed on one handset.

At commissioning, preserve the Android, firmware, Teams client, Intune, Authenticator and Admin Agent versions reported by the actual device and management plane. Recheck the live Microsoft table before an order or update because certification dates, published firmware and application support can change independently.

Verify power, ports and package

HP documents two Gigabit Ethernet ports, one USB 2.0 Type-C port for media and storage, and IEEE 802.3af Class 0 PoE with a published 13 W maximum. It lists a console, stand, handset and cord, CAT-5E cable and setup sheet in the referenced package. Confirm the regional SKU, switch power budget, VLAN, DHCP, DNS, time service, mounting and any separately required power or accessory.

A USB-C connector does not establish that a headset, storage device or adapter is supported. Validate the exact accessory and firmware combination through current HP and Teams guidance and a bounded pilot. Keep the device serial, part number, switch port and accessory identifiers with the result.

Bind identity, policy and calling to the position

Choose an assigned-user, common-area or other supported Teams workload before sign-in. Apply the correct account, usage location, licence, Conditional Access treatment and phone policy, then configure the intended PSTN connection and number where required. A successful sign-in does not prove directory scope, call queue behavior, caller identity, normalization or emergency routing.

For a shared position, follow Microsoft's current resource-account and common-area workflow. Test sign-out, restart and replacement recovery without leaving personal data or reusable credentials. Keep emergency identity, physical location, callback path and provider-approved test evidence together; never make an uncoordinated live emergency call.

Interpret audio and codec lists narrowly

The HP data sheet lists Poly Acoustic Clarity features and codecs including G.711, G.722-family variants, G.729A, G.719, iLBC, Opus, SILK and Siren 14. Those lists do not establish what the Teams service, PSTN path or installed call negotiates, and they do not measure room noise, handset intelligibility, speaker behavior or user comfort.

Pilot inbound and outbound calling, answer and reject, hold, transfer, mute, voicemail, keypad entry, speaker, approved headset behavior, policy restrictions, update recovery and power interruption. Preserve the remote-party result and observed application versions. No CCX 350, tenant, network, accessory, firmware, protected session, emergency workflow, audio path or live call was tested.

Retain procurement and support unknowns

The reviewed pages establish a current product and support surface, hardware specifications and a dated Microsoft certification record. They do not establish stock, price, lead time, included regional accessories, mode conversion, arbitrary SIP-PBX compatibility or a remaining support commitment for a proposed purchase. Confirm each item from the exact quote, entitlement and support policy rather than transferring a sibling CCX model's behavior.