Poly Studio X & TC8/TC10 Setup: Teams Rooms on Android (MTR-A) Complete Deployment Guide

The Poly Studio X Series (Studio X30, X50, X52, X70) paired with the Poly TC8 or TC10 touch controller represents one of the most widely deployed hardware platforms for Microsoft Teams Rooms on Android (MTR-A). Designed as an all-in-one appliance running PolyOS (built on Android), it eliminates the complexity of external compute modules, USB extension extenders, and discrete audio DSPs.

However, enterprise rollouts frequently stall during post-unboxing configuration. IT teams encounter the infamous “Searching for Video System” loop on the TC8 controller due to cross-subnet routing barriers, authentication failures triggered by Microsoft Intune Android Device Administrator retirement, or firmware update conflicts between Poly Lens and the Microsoft Teams Admin Center (TAC).

This deployment runbook provides a battle-tested, step-by-step engineering procedure to configure, secure, and operate Poly Studio X systems in an enterprise Microsoft 365 environment.

Table of Contents

1. Hardware Architecture & Network Prerequisites

Poly Studio X video bars operate as standalone appliances where the camera, stereo microphones, speakers, and Android SoC reside in a single chassis. The TC8 or TC10 touch controller acts as an out-of-band IP peripheral powered via Power over Ethernet (PoE 802.3af Class 3).

2. Microsoft Intune & Conditional Access Configuration (AOSP Transition)

Microsoft has retired legacy Android Device Administrator management for meeting room devices. Modern Poly Studio X units running PolyOS 4.x must enroll using Android (AOSP) Device Management.

A. Enabling Android (AOSP) Enrollment in Microsoft Intune

1. Navigate to the Microsoft Intune Admin Center (endpoint.microsoft.com).
2. Go to Devices ➔ Enrollment ➔ Android.
3. Under Android (AOSP) enrollment profiles, click Create profile.
4. Name: MTR-Android-Shared-Devices.
5. Token Type: Corporate-owned dedicated device (user-associated).
6. Set the Token Expiration Date (up to 65 years for room appliances) and assign the profile to your Teams Room device dynamic group.

B. Conditional Access Exclusion Checklist

Teams Rooms on Android cannot perform user-interactive Multi-Factor Authentication (MFA) challenges after initial pairing. Configure your Conditional Access policies as follows:

• Exclude from User MFA: Create a dynamic security group containing all MTR-A resource accounts (e.g., SG-MTR-Accounts) and exclude it from policies requiring biometric or authenticator app pushes.
• Grant Controls: Require Require device to be marked as compliant or Require approved client app.
• Session Controls: Set Sign-in frequency to “Every 365 Days” or leave unmanaged to prevent automated sign-out cycles during overnight maintenance.

3. Zero-Touch Onboarding via Poly Lens Cloud Portal

Managing firmware, configurations, and diagnostic logs across dozens of boardrooms manually via individual web browsers is inefficient. Poly Lens (lens.poly.com) provides centralized cloud management.

{
  "system.provider": "MicrosoftTeams",
  "system.mode": "Appliance",
  "device.autoRestart.enabled": true,
  "device.autoRestart.time": "03:00",
  "network.ntp.server1": "time.windows.com",
  "camera.tracking.mode": "SpeakerFraming",
  "camera.tracking.speed": "Normal",
  "audio.noiseblock.enabled": true,
  "audio.acousticFence.enabled": false
}

Onboarding Steps:

1. Log in to Poly Lens ➔ Navigate to Manage ➔ Device Groups.
2. Create a Device Group named Teams-Rooms-Android-Prod and configure the provider to Microsoft Teams.
3. Retrieve your organization’s Poly Lens Onboarding PIN / Cloud Account ID.
4. During initial hardware boot wizard (or inside the device web GUI under Admin Settings ➔ Poly Lens), enter the Cloud PIN. The Studio X bar automatically registers and pulls its baseline configuration.

4. TC8 / TC10 Pairing & Cross-Subnet Troubleshooting

The touch controller communicates directly with the video bar. In standard single-subnet deployments, pairing occurs automatically over mDNS. In enterprise segregated networks, manual IP pairing is required.

Step-by-Step Manual IP Pairing via Web GUI:

1. Connect your laptop to the room VLAN and open a web browser to the Studio X IP address (e.g., https://10.20.50.25).
2. Log in with admin credentials (default: admin / last 6 digits of serial number or custom password).
3. Navigate to General Settings ➔ Device Management.
4. Under Connected Devices, locate your TC8 / TC10 controller.
5. If the controller is not discovered automatically, click Manual Pair.
6. Enter the IP address of the TC8 / TC10 controller. Click Pair.
7. A 4-digit pairing PIN will appear on the touch controller display. Type this PIN into the Studio X web interface to confirm the TLS encryption key exchange.

5. Provisioning & Sign-in Flow (TAC Remote Provisioning)

Microsoft provides a zero-touch remote provisioning flow via the Teams Admin Center (TAC), eliminating the need for technicians to type 20-character passwords on room touchscreens.

Remote Provisioning Workflow:

1. Power up the Poly Studio X system with the provider set to Microsoft Teams.
2. The TC8/TC10 display will present a 9-character hardware provisioning code (e.g., XYZ-123-ABC).
3. The systems administrator opens the Microsoft Teams Admin Center (admin.teams.microsoft.com).
4. Navigate to Teams devices ➔ Teams Rooms on Android.
5. Click the Actions dropdown at the top right ➔ Select Provision devices.
6. Under the Waiting on activation tab, locate the MAC address or click Add MAC address and paste the hardware code.
7. Select the pre-staged room resource account (e.g., nyc-boardroom@yourdomain.com) and click Apply.
8. The Poly Studio X automatically receives its OAuth token from Azure AD, registers with Microsoft Intune, and launches the native Teams Room interface with calendar schedule synchronization.

6. Firmware Lifecycle Management: Poly Lens vs. TAC Update Rings

A frequent operational mistake is allowing both the Teams Admin Center and Poly Lens to push software updates simultaneously. This leads to version mismatch loops where TAC downgrades an update pushed by Poly Lens.

Best Practice Governance Model:

• Provider Engine Updates: Configure TAC to handle the Teams Rooms App and Company Portal updates via standard ring distribution (Ring 0 for pilot, Ring 2 for executive rooms).
• Appliance OS Updates: Use Poly Lens for underlying PolyOS firmware releases. Poly tests and certifies complete OS builds (combining camera drivers, DSP code, and Android kernel) before releasing them to the stable channel.
• Update Schedule: Set Poly Lens auto-update policies to trigger on Sundays between 02:00 and 04:00 AM local time with automatic restart verification.

7. Camera & Audio Optimization: Tuning Poly DirectorAI

Poly’s proprietary machine learning algorithms (Poly DirectorAI) manage framing and tracking. Selecting the appropriate framing profile based on room geometry is critical for meeting equity:

Acoustic Fence & NoiseBlockAI Configuration:

Under Audio Settings in the device GUI or Poly Lens:

• NoiseBlockAI (Outbound): Keep set to Enabled. Eliminates mechanical keyboard clatter, paper shuffling, and HVAC hum.
• Acoustic Fence: Set to Enabled only in open-plan huddle spaces or glass-walled conference rooms to ignore voices outside the physical meeting perimeter. For enclosed boardrooms, keep Disabled to prevent clipping speakers seated at the far end of the conference table.

8. Common Failure Modes & Diagnostics

1. TC8 Controller Stuck on “Could not connect to company portal”

Cause: Intune enrollment restrictions are set to block Android Device Administrator without an active Android (AOSP) profile assigned to the resource account.

Fix: Verify the room account is targeted by an active Corporate-owned dedicated device AOSP profile. In Intune, check Troubleshooting + support for the room user to verify the specific enrollment restriction blocking sign-in.

2. Device Randomly Reboots During Microsoft Teams Calls

Cause: Incompatible PoE power budget on the switch port powering the TC8/TC10, or thermal throttling on the Studio X bar due to recessed mounting behind display panels.

Fix: Verify the switch port provides full PoE+ (802.3at) if powering peripheral microphones. Ensure the Studio X chassis has at least 3 inches of top and side clearance for passive convection cooling.

3. Calendar Meetings Missing from Room Touchscreen

Cause: Exchange Online mailbox Set-CalendarProcessing rules are configured with DeleteComments $true, stripping the Microsoft Teams meeting URL from the invitation body.

Fix: Connect to Exchange Online PowerShell and run:

Set-CalendarProcessing -Identity "nyc-boardroom@yourdomain.com" -DeleteComments $false -DeleteSubject $false -AutomateProcessing AutoAccept

9. Frequently Asked Questions (FAQ)

Related Meeting Room & Infrastructure Guides

• Microsoft Teams Rooms (MTR) Setup: Step-by-Step Exchange Online, CA & Console Guide
• Microsoft Teams Rooms (MTR) Intune & Pro Portal: Custom Compliance Policies & Remote Log Analysis
• Exchange Online Room Finder & Hierarchical Room Lists: Step-by-Step Set-Place Guide
• Cisco Webex Room Kit Integration with Microsoft Teams: Direct Guest Join (WebRTC) & xAPI Setup Guide
• Microsoft Teams SIP Gateway: Onboarding Cisco & AudioCodes Desk Phones
• How to Configure AudioCodes SBC for Microsoft Teams Direct Routing