The Poly Studio X family includes all-in-one video bars and modular solutions for large boardrooms and training rooms. With incredible audio and video technology, compact sizes, and simple deployment, these devices are ideal for classrooms and environments of various sizes. The devices are equipped with an 8" TC8 or 10" TC10 touchscreen controller that allow users to join meetings, start instant meetings, make calls, share content, and manage participants in a meeting. In this blogpost, we look at some of the frequently asked questions regarding pairing of MTR Android touch controllers.

A Microsoft Teams Signature Room is a dedicated meeting space that is designed to provide the best possible experience for hybrid meetings. It includes a set of hardware and software that is specifically optimized for Microsoft Teams, as well as a carefully designed layout that promotes collaboration and engagement. Microsoft provides design guidance for Signature Rooms using a Jabra Panacast50. In this blogpost, we look at a possible Teams Signature Room layout that uses the Poly Studio E70 camera. Caveat: The information here does not represent any official guidance from HP | Poly or Microsoft. However, it is a real design that has been used in an actual signature room.

Teams common area phones are typically placed in an area like a lobby or another area that is available to many people to make a call: a reception area, lobby, or conference phone. Common area phones are signed in with accounts tied to a Microsoft Teams Shared Devices license which costs USD8.00 per month. 

This article provides an overview of how to deploy and configure Teams phone devices as common area phones for shared spaces. Many of the Teams voice deployment steps were already covered in a previous blog post and here we will use the existing tenant dial plan and voice routing policy. Number assignment will be done using a new cmdlet that were introduced recently. Once complete the phone will be able to display a dialpad and make and receive PSTN calls via direct routing

While the Teams Admin Center (TAC) remains as the main administrative portal for managing Teams as well as Teams Devices including Teams Phones, Teams Panels and Teams Rooms, organizations can now make use of the Microsoft Teams Rooms Pro Management portal to manage Teams Room devices that have the Teams Room Pro license. Note that management service is not available with Teams Room Basic licenses as mentioned in a previous blogpost comparing the Basic vs Pro licenses. Recently, Microsoft added Teams Room on Android (MTRA) devices to this service and so now organizations can manage not only Teams Room on Windows (MTRW) systems but also on Android as well. It's time for a walkthrough of the various management capabilities of the Teams Room Pro Management service and highlight some of the useful features using this portal compared with using the Teams Admin Center.

Large organizations that prioritize security want to migrate to cloud services such as Microsoft 365, but they must ensure that their users can only access approved resources. Companies have traditionally restricted access by restricting domain names or IP addresses. This strategy fails in a world where software as a service (SaaS) apps are hosted in the public cloud and use shared domain names such as outlook.office.com and login.microsoftonline.com. Instead of restricting users to approved identities and resources, blocking these addresses would prevent them from accessing Outlook on the web entirely. Tenant restrictions are a feature in Azure Active Directory (Azure AD) that addresses this issue . In this blogpost, we look at how MTR devices can potentially implement this capability.

This blog post aims to help readers understand the new Teams Room licenses that was just released by Microsoft this month and how to work with these licenses in actual Teams Room devices. For more information see the Microsoft Docs article.

Whether planning to deploy Microsoft Teams Room on Windows (MTRoW) solution for a Proof-of-Concept (POC) or an actual deployment, there are certain mandatory pre-requisites that have to be met before the solution can be deployed successfully in a corporate network environment. This includes hardware components of the solution, software licenses, network requirements as well as firewall ports and proxy configurations, and last but not least security and AD/AAD requirements. Below is a handy checklist to make sure all the pre-requisites are met before starting to unbox that brand new MTRoW you just received :)

The latest release of firmware version 7.2.1 allows Poly CCX native Teams phones to have a secondary SIP registration with a standards-based VOIP call server. The Teams account signed in on the phone still remains the primary line for incoming/outgoing calls, while the secondary SIP registration will allow PSTN calls in the event that the Teams connection becomes unavailable. This is useful for disaster recovery scenarios where the corp WAN link is down and the device is no longer able to communicate with Teams. In this case with the secondary SIP registration to a local PBX with PSTN Trunks, users can manually switch to the SIP registered line and continue to make PSTN calls. Note that this is manual failover, not automatic . The blog post describes the steps to enable and deploy this feature. Do note that this feature only works with CCX400/500 with HW Rev K or higher and CCX600.

Proximity Join and Teams Casting are 2 excellent features that are available on Teams Rooms devices. They allow easy joining of a Team Room system into a meeting using a personal iOS or Android smartphone without the need to even touch the control panel of the room device. This is certainly welcome for back to office scenarios in the post-pandemic world of hybrid work. However, not many people are familiar with how to get these 2 features working and in this blog post, we explore 5 tips on how to get Proximity Join and Teams Casting working smoothly.

The adoption of Teams certified devices such as Teams Rooms, Teams phones, headsets, speakers etc continus to grow at a rapid pace and as organizations deploy hundreds of these devices across their network, its vital for IT administrators to be able to manage them from a central location as also be alerted when things go down. Fortunately, the Teams Admin Center provides a way for IT admins to be notified whenever a shared or room devices goes down. This blog post walks through the steps