Logitech
The latest articles from our experts and partners
Community Guides
Televic D-Cerno and Logitech Rally Bar in Hybrid Meeting Rooms
Experience At Seat Audio with Televic D-Cerno and Logitech Rally Bar + Tap Hybrid meetings have become a constant in corporate boardrooms, but consistency is still the challenge. When audio breaks down, the entire experience follows. Remote participants miss context. In-room conversations fragment. Decisions slow. The expectation today is simple: every participant should be able to understand and contribute equally, regardless of location. Achieving that at scale requires a design that is both reliable and easy to repeat across rooms. This is where the combination of Televic D-Cerno and Logitech Rally Bar defines a different experience. For the IT manager, the system behaves exactly as it should: predictably. A single USB connection links the Televic D-Cerno system directly to the Logitech Rally Bar, eliminating unnecessary integration layers and reducing points of failure. Standard shielded CAT cabling connects each tabletop unit, delivering an “At Seat Audio” approach where every participant has a dedicated audio path. The system is accessible over the network for configuration, monitoring, and updates, but once deployed it becomes largely invisible to maintain. This simplicity reduces deployment time, room design standardize, and ongoing support effort are minimized — These are key requirements for organizations scaling hybrid spaces across multiple rooms For the in-room participant, the experience is immediate and intuitive. There is no learning curve. Televic’s hands-free operation means participants simply speak, and the system responds. A green LED provides clear visual confirmation that their microphone is active. Audio is reinforced locally through the same unit, allowing natural conversation without relying on ceiling speakers or external systems. When control is needed, the Logitech Tap interface provides familiar meeting controls—adjusting far-end volume or muting the room for private discussion. Personal control remains simple as well: a press-and-hold on the microphone button mutes the individual position, with clear visual feedback. For the remote participant, the difference is clarity. Instead of struggling to follow fragmented audio from across the room, every voice is captured at the source. Conversations become intelligible, structured, and easy to follow. This is where meeting equity becomes real—when every voice carries equal weight and presence. Together, Televic and Logitech deliver a unified hybrid experience that prioritizes intelligibility, simplicity, and consistency. It is a system designed not just to work, but to work the same way every time—across rooms, across users, and across organizations. Experience At Seat Audio for yourself, visit the Televic website. https://www.televic.com/en/conference/products/wired/dcerno-product-family https://www.televic.com/en/conference/our-partners-technology-partners/logitech How to simplify classroom AV with Nureva and Logitech
Modern classrooms are evolving fast — and AV technology needs to keep up. Logitech® solutions like the Rally Camera and Tap IP bring high-quality video and intuitive control to learning spaces, making it easy to connect with remote learners and guest speakers. But audio is just as critical, especially in active, student-centered environments. That’s why we’ve teamed up with Nureva, an innovative company offering plug and play audio systems made for larger spaces. Nureva’s founders built the global tech brand, SMART Technologies, which put an interactive whiteboard into millions of classrooms around the world, and these deep roots in education and innovation inform everything Nureva offers. AV for engaged learning By combining Nureva and Logitech, you get exceptional audio and video coverage that makes HyFlex and hybrid learning engaging for remote and in-room students alike. With Microphone Mist™ technology, Nureva fills classrooms with thousands of virtual mics, so instructors can move freely as they teach and still be heard clearly. Setup is simple, and the system automatically adapts to changes in room layout or usage. Plus, by combining up to three Logitech Rally Cameras with Nureva’s sound location data and an INOGENI® CAM230 multi-camera selector, you get automated switching, so remote students always get the best view. Together, we’re creating complete classroom solutions that are easy for IT teams to deploy and manage, and even easier for instructors to use. For more details on how to set up your classrooms with our joint solutions, get this reference design: https://403995.hs-sites.com/hubfs/product-resource/reference-designs/nureva-logitech-standard-classroom-reference-design.pdf] And if you’re looking for a solution that includes Logitech RoomMate running CollabOS, check out this reference design: https://403995.hs-sites.com/hubfs/product-resource/reference-designs/nureva-logitech-roommate-collabOS-classroom-reference-design.pdf] Tim JLogitechScaling up: How Nureva and Logitech power larger meeting rooms
Are you looking for easy and effective AV solutions for your larger spaces? Logitech is working with Nureva to ensure large and extra-large meeting rooms get the full-room microphone coverage teams need — without a complicated and costly setup. With Nureva’s patented Microphone Mist™ technology, you can fill spaces up to 35' x 55' (10.7 x 16.8 m) with thousands of virtual mics, delivering consistent pickup without complexity. No ceiling mics. No DSP tuning. Just plug and play. Our collaboration solutions — such as Logitech® Tap IP — have been tested to work smoothly with Nureva® audio systems. And by combining up to three Logitech Rally Cameras with Nureva’s sound location data and an INOGENI® CAM230 multi-camera selector, you also get simplified automated switching. From hybrid meetings to AI summaries Together, Nureva and Logitech create a high-performance AV experience that’s easy to deploy and manage. Anyone joining a meeting remotely can see and hear everything, making collaboration from a distance feel natural. Plus, our joint solutions are ideal for AI-powered Teams meetings, providing Microsoft® Copilot with the audio data needed to generate accurate transcripts, summaries, follow-up tasks and more. For details on how to set up large and extra-large meeting rooms with our joint solutions, check out these two reference designs: https://403995.hs-sites.com/hubfs/product-resource/audio-conferencing/nureva-and-logitech-extra-large-boardroom-reference-design.pdf] https://403995.hs-sites.com/hubfs/product-resource/audio-conferencing/nureva-and-logitech-large-meeting-room-reference-design.pdf] Tim JLogitechHow to solve the divisible room challenge with Nureva and Logitech
Managing AV setups in divisible rooms can be complex — but Logitech and Nureva together make everything refreshingly simple. With our joint solutions, spaces up to 35' x 55' (10.7 x 16.8 m) can be divided into two fully equipped areas. Your teams get a great audio and video experience, whether they’re using the room as one space or two, and it’s easy to switch back and forth as needed with an Ethernet switch. Flexible and adaptable Nureva’s audio systems deliver true full-room microphone pickup. So, in both divided and combined room configurations, voices will be heard clearly in every inch of the space. And there’s no need to adjust your audio whenever you switch — Nureva® systems automatically and continuously adapt to a room’s acoustic profile. Logitech’s conferencing gear — including cameras and touch controllers — integrates seamlessly, adapting to room changes with minimal intervention. And all our products are easy to install and manage. Together, we make sure that remote participants see and hear everything in a divisible room, no matter how the space is being used. And all you need are two Nureva HDL310 audio systems, an Ethernet switch, two Logitech® Rally Cameras and two Logitech Tap touch controllers. It’s a plug and play experience that’s built for flexibility and built for IT. To find out how to set up your space, see this reference design: Tim JLogitechLogitech and Nureva: A powerful combo in larger meeting spaces
IT pros love the audio and video performance they get from Logitech® systems. But in some cases, such as for setups in larger rooms, a little more audio horsepower might be required for microphone pickup. To give our customers what they need in these spaces, we seek out, carefully vet and then collaborate with select AV suppliers. When it comes to audio, we’re pleased to work closely with the good people at Nureva. Why Nureva? Three reasons. First, they share Logitech’s dedication to simplicity. It’s in the DNA of both of our companies to simplify videoconferencing technology as much as possible — for the IT pros responsible for setting up, maintaining and monitoring the equipment and, ultimately, for those using the meeting rooms and classrooms. We love how Nureva’s tech makes it possible to provide full-room mic pickup with just one wall-mounted mic and speaker bar for large rooms or two for extra-large rooms. Second, we’re impressed by the audio performance they deliver. Their Microphone Mist™ technology provides pro AV performance that allows for seamless collaboration in a wide range of room shapes and sizes. It produces the audio quality that Logitech customers demand. Third, Nureva has committed to working closely with us to provide the initial testing and ongoing device software updates that ensure our solutions work together seamlessly. Bottom line: If you’re an IT pro equipping hybrid work and hybrid learning spaces, you’ll want flexible, reconfigurable solutions that easily adapt to room conditions and the other tech in each space. With Logitech and Nureva, you’ll get just what you’re looking for. Find out more and browse reference designs at https://www.nureva.com/ecosystem/logitech. Tim JLogitechFilling the Gaps: How INOGENI Complements Logitech in the AV Ecosystem
As Logitech continues to lead the way in scalable video collaboration solutions, particularly with products like Rally Bar, CollabOS, Tap, and Scribe, we recognize that our systems are often part of larger, more complex AV environments. In these scenarios, our customers occasionally encounter limitations, especially around connectivity, source switching, camera control, and BYOM flexibility. This is where INOGENI, a trusted partner in USB and AV bridging technologies, plays a critical role. Their hardware products are designed to extend, enhance, and simplify Logitech deployments, particularly in rooms that demand high flexibility, cross-platform compatibility, and robust control integration. Why This Matters for Logitech INOGENI helps us preserve our simplicity and scale, while unlocking compatibility and reliability in complex AV environments we don’t directly address today. These are not competitors, they’re trusted AV enablers who make our solutions more versatile, especially in high-value deployments. Working closely with INOGENI ensures we can confidently say "yes" to more customer needs, reduce friction for IT/AV teams, and win in spaces where flexibility and integration are key. To help learn how Inogeni products can fill in the gap, check out this reference: If you are looking for a deeper technical understanding, we have created a compatibility matrix that can be found here. For more information please reach out to Ryan Willden, US Technical Sales Director. [email protected] 801-664-6229 Tim JLogitech[Google Meet] Administrator guide to setup Logitech Scribe for Chromebox
This feature makes it easier to share what is shared from a Logitech Scribe with everyone in the meeting, regardless of location, so they can view the content from a whiteboard clearly. This will enable the content written on a Scribe whiteboard in a room to be shared as a presentation in a meeting using the Logitech Scribe. As a result, remote meeting participants will be able to see what is being drawn on a Scribe whiteboard. Admins: There is no admin control for this feature. However, admins will have the option of setting a default whiteboard camera in the Admin console if they want to receive alerts when it goes offline. To set a default peripheral camera: Go to menu panel Devices -> Google Meet hardware -> Devices. Note: Some features may require the manage Devices privilege for Google Meet hardware In the Connected peripherals section, select the peripheral you want to set as the default -> click “Set As Default” 1 - Connected peripherals from Google Admin upon connecting Scribe 2 - Setting the default peripheral camera 3 - Disconnect Scribe from Chromebox, and click on Issue History. Click on the issue to expand on the details. End users: There is no end user setting for this feature. In order to use the whiteboard feature, a Logitech Scribe must be plugged into a Google Meet hardware device. When both Tap HDMI and Scribe are connected to the Meet hardware device at the same time, the following options - Whiteboard camera and HDMI device will be available. Note: The purple Share button is not supported by Google Meet. If you encounter any issue with Logitech Scribe with a Q-SYS device, please refer to the article below for more information. Known Issue from Google - Logitech Scribe with a Q-SYS device [Google] Administrator guide to configure API access control for Logitech applications
API controls in Google Admin are required to authorize Logitech Sync and Logi Tune to access Google calendar resources and user information. This allows the applications to integrate with Google Workspace and provide features like calendar scheduling and user management within the Logitech platform. Once these permissions are enabled, users are able to book a desk and view meeting schedule from Logitech Dock Flex using their Google Workspace work account and book a meeting room enabled with Logitech Tap Scheduler from Google Calendar. Configure API access for Logitech Sync in Google Login to Google admin console using admin credentials. Ensure that the administrator has a role privilege of Admin API minimally or Super Admin. From the home page, navigate to -> Security -> Access and data control -> API controls. In the App access control section, click “Manage third-party app access”. Click “Configure new app”. Search for: App: Logitech Sync Client ID: 152214001440-eha4ds1puu0lenoo98rmm5den3scdj4t.apps.googleusercontent.com Select “Logitech Sync”. Choose the organizational scope you wish to grant access to Logitech Sync. Note: You have two options: Scope “All users”: Grant organizational-wide access to all calendar resources. Scope “Select org units”: When configuring Logitech Sync app, ensure the Google organization unit you select contains all the calendars you intend to use with the application, as granting access will apply to all calendars within that organizational unit. After selecting the scope, click “Continue”. In the Access to Google Data step, scroll to the Access to Google Data section. Google automatically includes these scopes. https://www.googleapis.com/auth/userinfo.email https://www.googleapis.com/auth/admin.directory.resource.calendar.readonly https://www.googleapis.com/auth/calendar.events https://www.googleapis.com/auth/admin.directory.user.readonly Click “Specific Google data” in order to proceed with the final step to review the new app configuration. Click “Continue”. Finally, click "Finish" to complete the setup. Your application should now be approved. At this stage, you can proceed to configure your Google service account in Logitech Sync. Configure API access for Logi Tune in Google Navigate to Security -> API controls. Search for the following application: Application Name: Logi Tune Client ID: 280855413050-jbtv8i5f8qpq4gtjhcapjkvo62sttp56.apps.googleusercontent.com Select “Specific Google data” in the Access to Google Data section. Below are some admin tips on troubleshooting or reviewing API access control. Search for the targeted application by the application ID available in Google Admin logs. Below is a sample screenshot of “Deny access” to Logitech Sync from Google application. The number of users accessing the application would take a day or more to reflect the updates. Once the API access controls are granted, you can proceed with the following requisites to grant users access to Logi Tune with their Google Workspace work accounts and access to meeting rooms’ visibility with Logitech Sync. Logitech Sync: Set up Google Calendar integration with Sync Logi Tune: Flex Desk User Management, Using QR codes for Desk booking For additional details, please refer to the links provided below: Space Management: Security and Privacy Whitepaper Google Support | Control which third-party & internal apps access Google Workspace data Deep dive on AOSP and Teams devices
I’ve lost track of the number of times I have been asked about AOSP for Teams devices so I’m covering it here. It’s also a good time to cover it as Microsoft nears the finish line with the migration. History When Microsoft started supporting phones for Microsoft Teams around 7 years ago they decided on Android as the operating system. Since these devices would be authenticating into Microsoft 365 as users they also needed a way to add management and security for these devices. This is so IT can put a layer of control over devices that access company services and data. Regardless of whether it is a smartphone or tablet, or a Teams Android device, this management solution is Intune. The devices have to enroll themselves into Intune. How they get enrolled will differ by device. The important thing to call out is Teams Android devices enrolled themselves using Android Device Administrator (ADA) management. Device Administrator was how it was done in early Android operating system versions and that’s how Microsoft decided on when Teams devices started appearing. ADA is considered a legacy method for managing Android devices. It provides basic management capabilities and was introduced with Android 2.2. Google deprecated ADA management in 2020. Intune will end support of ADA later this year. There are other ways to manage Android devices. How they are managed depends on the device and how they are used. Smartphones and tablets have access to a Play Store to install apps. This relies on Google Media Services (GMS). Microsoft Teams Android devices only have a few apps installed which is by design. All they need is the Teams app, an admin agent and a way to authenticate. The vendor, i.e. Logitech also adds their own admin agent, i.e. Sync. Which means they don’t need access to Google Media Services. AOSP management is a more modern approach to managing Android devices, especially those without Google Mobile Services (aka NGMS devices). AOSP management offers more advanced features compared to ADA. It includes comprehensive device settings, security policies, app management, and remote management capabilities. Where to now? ADA and AOSP are totally different ways to manage devices in Intune. There’s also the authentication aspect. ADA used Company Portal to authenticate. AOSP actually uses Intune to authenticate. Then there’s the policies. In order to enroll a device into Intune, Intune needs to know what the device is and how it should be managed. ADA devices had to be allowed to enroll in Intune. The same applies for AOSP devices. This means you need to create some policies. No you can’t just migrate the ADA policies over and call it a day. You have to do it from scratch. Creating the AOSP policies Microsoft’s documentation on creating the policies for AOSP is very good. There are so few steps that anyone can follow it and it should only take you a few minutes to do. Step 1: Create new enrollment profiles & configuration/compliance policies in Intune. Open https://intune.microsoft.com/ Go to Devices -> Enrollment -> Android Scroll down to Android Open Source Project (AOSP) and click on Corporate-Owned User Associated Devices Click on Create Policy Give it a name, e.g. Teams AOSP Devices Under For For Microsoft Teams Devices (preview) click Enabled Click Next and Create Step 2: Create a new Intune Compliance Policy Go to https://intune.microsoft.com/ Click on Devices -> Compliance Click on Create Policy Under Platform select Android (AOSP) Click Create Give the Policy a name and click Next Under compliance settings set the following Block Rooted Devices Minimum OS level 10 Require encryption of data storage to YES Click Next Under actions for noncompliance add any additional settings you need in your org. It will mark the device as non-compliant immediately anyway. Click Next Under Assignments click Add groups, find and select the group which includes your Android room and device accounts. You should have one of these groups already if you have Android devices. Click Next Review and Create If you also have any Conditional Access policies that lock things down to location, vendor and device model or anything else for that matter. You also need to recreate these. Totally optional though. That’s it! You can do this now. It won’t hurt anything. The point is you’ll be ready for when you do Step 3. Step 3: Upgrade to an AOSP Device Management capable firmware For existing devices, as long as you completed step one and the token is valid, the devices should just update and reboot. As long as the room account is in the group you added to the compliance policy it will sign in and be ready to go as normal. The firmware update will automatically un-enroll the device from Device Administrator and re-enroll the device with AOSP Device Management using the enrollment profile created in Step 1. In Intune you’ll see the devices appear as AOSP devices. There will still be an entry for the ADA version of the devices. You can clean these up later on. For new devices, they should just sign in using the Intune authentication and appear as AOSP devices. If you check the Teams Admin Centre, before the update you will see in TAC that the device has the Company Portal app. After it is updated you will see it has Authenticator and Microsoft Intune. When will you get the update For Logitech CollabOS devices this will be CollabOS 1.14B which will be released to public Beta in early May 2025. The build will become Generally Available (GA) approximately 2 weeks later around the 15th of May. The GA update will be available from Sync or on the device itself (which comes from Sync) initially. Followed by the Teams Admin Centre (TAC). For availability in the TAC, Microsoft is keeping a Learn post up to date with all the latest information. Moving Teams Android Devices to AOSP Device Management | Microsoft Community Hub I recommend bookmarking the page and checking it often. The article states “Please ensure that all prerequisites for AOSP device management migration are completed for your organization to ensure a smooth migration. Your devices may sign out during migration if the prerequisites are not carried out properly. Please see the table below for the schedule of auto updates for your devices.” It says that for Logi devices the update will be available in the Teams Admin Centre from May. At which time you can begin manually updating devices from TAC. They go on to say that on 15th June, automatic updates will begin. Once the auto update phase starts the firmware updates are not pauseable. Devices will simply start automatically updating following one of the three update rings set for each device in Teams Admin Centre: These are Validation: Validation gets updates starting at day 0 and aims to complete by the end of day 15. Think of this as a test ring. General: General gets updates at day 16 and aims to complete by the end of day 45. This is the default update ring Final: Final gets updates at day 45 and aims to complete by the end of day 60. Microsoft say this ring is for important rooms where more caution is needed on applying updates. Therefore you can build in the most amount of delays before being served the update. Conclusion and final thoughts As I said, the prep work is easy. The hardest part for you might just be finding the team with the rights in Intune to do step one. But once you do it is literally just one profile which takes seconds to create. So just go do it so you’re ready. If you are ready and you want to try out the AOSP build now you can sign up for the AOSP Device Management Migration for Teams Rooms on Android - Early Preview using the Sign Up Form. What’s the difference between multi-camera and multi-stream in MTR on Windows?
Microsoft is adding features to Teams Rooms every month. Some of the features sound similar but are actually quite different. Two of the features I get asked about a lot recently are multi-stream and multi-camera. Multi-Stream Multi-Stream IntelliFrame, as it is officially known, is a feature for Microsoft Teams Rooms on Windows that combines the power of an intelligent camera solution such as Logitech Rally Bar with IntelliFrame from Microsoft. The solution works because the MTR app on the Teams Rooms compute can accept multiple camera streams from a connected camera. The Logitech Rally Bar and Rally Bar Mini can now be enabled for multi-stream in Sync and send up to five separate streams into a Teams meeting. This consists of the room view and up to 4 active speaker tiles. The configuration for multi-stream is done either in the Sync Windows client on the MTR compute, or in the Sync portal provided your Sync client has been provisioned to Sync. Make sure you have Sync App 3.7.149 from January 2025 and CollabOS 1.14.180 where we added Multi-stream support. Multi-stream for MTR is enabled under Grid View in the RightSight 2 camera settings First enable Grid View Enable Subtiling Enable Multi-stream confirm and reboot Sub-tiling is optional but recommended Sub-tiling in multi-stream works the same way as standard Grid View. It subdivides one or more of the four grid quadrants into multiple tiles, effectively giving more people a tile within the grid. The sub-divided tile is sent as one of the 5 streams. The last thing to do is configure the Teams Rooms app to build out the multi-stream view. Go to Teams Admin settings and under peripherals set the default camera as the RallyBar (or RallyBar Mini) UVC 1.0 Room View. Then save and exit. Alternatively, you can choose the RallyBar (or RallyBar Mini) UVC 1.0 Room View in the camera settings box when in a meeting. The experience in multi-stream will be broadly similar to this. In multi-stream, Microsoft clusters all five streams together and nests it in the gallery. The gallery itself is dynamic. This means that the size of the video tiles is dependent on who and how many are joining. People joining from a laptop are given a 1x1 tile. Rooms can grow automatically to a 2x2 tile (equivalent to 4 people), unless there’s only one person in the room, which shrinks it to 1x1 again. Multi-stream, and multi-camera view (which I’ll cover next) is always given a 2x2 tile. This means that when you join a Teams meeting either on your laptop or from a room, the gallery will be made up of individual people, larger room tiles, which could be composite from a Rally Bar and Sight, or a Group frame, and either multi-stream or multi-camera views or both. A feature coming in the not too distant future is the ability to have name tags of the users in each people stream. Known as people recognition, when the meeting is recorded and transcribed it will start recognising people by voice and face. Of course you would have had to enable all this at the back end and your users will need to have enrolled their face and voice into Teams. But assuming all that’s done, Teams will apply a name tag to tiles of users it recognises. See below. More information on Multi-stream IntelliFrame What is Microsoft Multi-Stream IntelliFrame and Intelligent Camera? - Microsoft Teams | Microsoft Learn How to enable Multi-Stream IntelliFrame on Rally Bar for Microsoft Teams on Windows (Beta) - Logitech Sync Hub Introducing the Multi-Stream Experience in Microsoft Teams - Logitech Sync Hub Multi-camera Multiple-camera view, as it is officially known, is a feature for Microsoft Teams Rooms on Windows that allows you to attach up to four single stream USB cameras to your MTR compute, then send them as the multi-camera view into the Teams meeting. Microsoft construct a composite of these four cameras and send that as the primary video feed into the meeting. Users dialling in to the meeting can choose to watch the multi-camera view or switch between each camera. Multi-camera view can work with Logitech Rally Bars with or without Sight (as a single stream composite only), Meetup or Meetup 2, or Rally cameras or any certified logitech webcam. All cameras need to plug into the compute directly rather than through a USB hub. The user will see this icon in the top right of the multi-camera view. Clicking the right arrow will switch from multi-camera to the first or next single camera in the list from top left to bottom right. Clicking the left arrow will navigate to the previous camera, then back to the multi-camera view. You must connect your cameras directly to the compute over USB. Microsoft gives guidance on the minimum spec for the MTR compute to support multi-camera and the number of cameras. You need an i5 or better just to support multi-camera and a 9th gen Intel to support two or three cameras, or a 12th gen to support four. You also need enough USB ports to connect a touch console, audio and 4 cameras. Connecting a Rally Bar and 3 additional cameras only consumes 4 ports since Rally Bar is the audio and video. Same with Rally system and 3 standalone Rally cameras. Logitech offers customers a choice of Logi Asus Nuc, Dell Optiplex and Lenovo Core as the MTR compute. The current 2024 and 2025 line up are all suitable for having four cameras connected. From a configuration standpoint it is simple. In Teams rooms settings select peripherals and enable “remote participants can see multiple camera view” under Multiple camera view. Then decide which is the default or primary camera. Then add additional cameras using the Add Video Cameras button and selecting the right camera. Once you have selected all your cameras, tap save and exit. Now you can test it. Start a meet now or join a scheduled meeting. Tap the arrow next to the camera icon to view the camera setting and verify that multiple camera view is enabled. For now, the camera preview will only show you the view from one camera. I think in the future it will show you a preview of the multi-camera view. There are loads of use cases for multiple camera views. From having multiple cameras around the room to capture individuals or banks of people. To presenter and attendee cameras in a hybrid event or in hybrid learning. Or pointing multiple cameras at points of interest around a room and creating a single view of all of them for attendees to see and select from. One topical use case for Logitech is using Logi Sight with Rally System. This capability will rely on the multi-camera view. So watch this space for more on that feature. More information on Multiple Camera View Multiple camera view in Teams Rooms - Microsoft Teams | Microsoft Learn Use multiple camera view in a Microsoft Teams Room - Microsoft Support Summary To sum things up. Multi-stream is sending up to 5 streams from a single camera and providing a place for name tags for people recognition. Multi-camera is simultaneously streaming up to 4 cameras into a meeting and allowing the attendees to choose what camera they want to view. There are use cases for both multi-stream and multi-cameras in Microsoft Teams Rooms. Both features will get better over time as Microsoft starts to be able to evolve IntelliFrame and direct the action from multiple streams and multiple cameras to try to capture and send the best view from the room. I can’t wait!