Additional meeting and call-related features and issues within Microsoft Teams for business
Hello Patricia,
Thank you for confirming that the room uses a Poly Studio X52 with a Poly TC10. This is a certified Teams Rooms on Android solution, so the Windows-specific Teams Rooms instructions provided by AI earlier do not apply to this room device.
Teams uses Bluetooth Low Energy to discover nearby rooms. You do not need to pair your computer manually with the Poly system through the operating system’s Bluetooth menu.
From Microsoft Teams side, please verify the following:
- Keep Bluetooth and Location Services enabled on your computer.
- Confirm that Teams has permission to use Location Services and nearby-device discovery.
- Fully close Microsoft Teams, reopen it, and test again while physically near the room.
- Make sure you are signed in to the correct organizational account. The user and room accounts should be in the same tenant, or the organizations must have the appropriate external trust relationship.
- If applicable, confirm that you are not being held in the meeting lobby, as this can prevent Teams from adding the room as another meeting device.
- Update the Teams client, then restart your computer and test again.
Since you already confirmed that Bluetooth is enabled on the computer, I would next verify that Bluetooth beaconing is enabled on the Teams Rooms device. For the best proximity experience, the room administrator can also enable Automatically accept proximity-based meeting invitations. For detailed configuration guidance, you can refer to Proximity Join using Bluetooth and ultrasound
Because the Studio X52 and TC10 are HP/Poly devices, a room administrator may need to verify the device-side configuration, including:
- The Studio X52 is running in Microsoft Teams provider mode.
- Bluetooth beaconing is enabled in the Teams Rooms meeting settings.
- The TC10 is correctly paired with the Studio X52.
- The Poly VideoOS, Teams Rooms app, and TC10 software are running compatible versions.
- Both devices have been restarted after any configuration or software changes.
To isolate the source of the issue, I would also suggest discovering the room from another laptop or mobile device:
- If another device can detect the room, the problem is likely specific to the original computer. The next areas to check are Teams permissions, Bluetooth drivers, Location Services, Teams cache, and organizational security policies.
- If no device can detect the room, the room may not be advertising its Bluetooth beacon correctly. In that case, the room administrator should review the Studio X52 configuration and contact HP/Poly Support if the device-side checks do not resolve the issue.
The following HP/Poly resources provide visual guidance for checking the Studio X52 and TC10 configuration:
- Using a Poly Studio X system with Microsoft Teams Rooms on Android
- Poly Studio X Series setup with Microsoft Teams
These resources are provided by HP/Poly, not Microsoft. Screenshots, menu names, and available settings may vary depending on the installed Poly VideoOS, TC10 software, and Teams Rooms app versions. Please consult your room administrator before changing the provider mode, updating firmware, or resetting either device. A factory reset should only be used as a last resort because the room will likely need to be reconfigured, paired, and signed in again.
I hope these steps help isolate the source of the BLE discovery issue. If the problem persists, please share whether another device can detect the room, along with the Teams client and Poly VideoOS versions, so I can help you further.
Best regards,