หมายเหตุ
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลอง ลงชื่อเข้าใช้หรือเปลี่ยนไดเรกทอรีได้
การเข้าถึงหน้านี้ต้องได้รับการอนุญาต คุณสามารถลองเปลี่ยนไดเรกทอรีได้
Issues affecting multiple device types
| Issue | Description | Workaround |
|---|---|---|
| Android 15 devices show unmonitored in Pro Management Portal | Teams Android devices running Android 15 may show unhealthy or unmonitored within the Teams Pro Management Portal. | No workaround is available at this time. |
Issues affecting Teams Rooms on Windows devices
| Issue | Description | Workaround |
|---|---|---|
| Local PTZ Reset may restore zoom but not pan or tilt in Teams Rooms app version 5.6 | On Microsoft Teams Rooms on Windows devices running app version 5.6 with local PTZ enabled, selecting Reset may restore zoom without restoring pan or tilt on some cameras. The camera can remain in its adjusted position after Reset is selected. | Update the Teams Rooms on Windows app to version 5.7.112.0 or a later supported release. If the issue persists after updating, contact Microsoft Support with the camera model, camera firmware version, and Teams Rooms app version. Consult the camera manufacturer for recommended firmware and model-specific guidance. |
| Teams Rooms app may stop responding when using local PTZ zoom controls | On Teams Rooms on Windows, using local pan, tilt, and zoom controls with some camera and firmware combinations may cause the Teams Rooms app to stop responding or close unexpectedly. This has been observed with repeated zoom commands on an AVer CAM520 Pro running firmware V0.0.1000.26. Broader camera and firmware impact is still being evaluated. | Contact the camera manufacturer for guidance on supported firmware updates. As a temporary avoidance measure, admins can disable local PTZ controls and restart the Teams Rooms console. Disabling local PTZ is an avoidance measure and does not resolve the underlying issue. |
| Teams Rooms app out of date | The Teams Rooms console displays the system config out of date error. | To fix this issue, use the Microsoft Teams Rooms recovery tool. |
| Can't access Windows Settings from the desktop right-click menu in admin mode. | On Teams Rooms devices, any user account that has the Teams Rooms app installed can access Windows Settings only by using the Start menu. If you try to access Windows Settings by using another method, the Teams Rooms app opens instead. | Use one of the following workarounds to access Windows Settings:
|
| Video participants missing from Front row. | The Front row view doesn't show all the video participants, and they're missing from the overflow area as well. The Front row view displays a maximum of five attendees on a single screen, and up to nine attendees on a dual screen. When the maximum number of attendees are already shown on the screen, the extra attendees are represented in the overflow view area. However, when two or more participants turn on their cameras, the remaining video streams might not fit in the Front-of-Room display, and they are not accounted for in the overflow area as well. This issue causes those video participants to appear as "missing" from the meeting. |
Use a different meeting view than the Front row view. |
| All video streams turn off on Front row during a meeting. | When you use the Front row view on a Teams Rooms on Windows device, all video streams including the meeting room's video and incoming content turn off in the Front-of-Room display. This issue occurs intermittently when a remote participant turns off their video while content is being shared. | Leave and rejoin the Teams meeting from the Teams Rooms device. |
| USB devices fail intermittently on Teams Rooms devices. | On Teams Rooms on Windows devices that use Intel PCH 500, 600, or 700 systems, you hear occasional glitches or unexpected clicking or popping noises in an audio stream. You might also see glitches in a video stream momentarily, and occasionally a USB audio or video device might stop working. These issues occur if your device experiences USB split transaction issues. |
Switch to Admin mode on your Teams Rooms on Windows device and perform step 3 listed in the Resolution section of USB-connected audio or video devices malfunction when connected to specific Intel-based devices. If the script that you run determines that your device is impacted, perform step 4 to add the registry entry as described. |
| Teams Rooms device loses internet connectivity after installing a feature update for Windows | A Teams Rooms device that is connected to a network, which requires a proxy can't connect to the internet after installing a feature update for Windows, including an upgrade to Windows 11. This issue occurs if the proxy setting for internet access on the affected device is configured for the LocalSystem instead of a system-wide proxy. The Windows feature update deletes the LocalSystem settings. This behavior is by design. |
If your device has proxy settings set for the LocalSystem user, transfer those settings to the system-wide proxy settings that are set and maintained through Mobile Device Management (MDM). Alternatively, you can use the Set-WinInetProxy PowerShell cmdlet to configure the system-wide proxy settings. When you use system-wide proxy settings, they won't be affected when you install Windows feature updates on the device in future. |
| File Explorer view appears when Google Meet starts. | When you join a Google Meet meeting by using a Teams Rooms on Windows device, the display shows a view of File Explorer briefly before the Google Meet interface appears. | No workaround is needed. The view of File Explorer disappears automatically when the meeting finishes loading. |
| Brief spike in volume after disconnecting from Google Meet. | You join a Google Meet meeting by using a Teams Rooms on Windows device. Another user joins the meeting by using a different device such as a laptop, and shares a presentation involving audio. The volume of the presentation audio heard on the Teams Rooms device is low. If you disconnect the Teams Rooms device while the presentation is ongoing, then for a brief moment while the device disconnects from the meeting, you hear a significant increase in the volume of the presentation audio. |
No workaround is available at this time. |
| During a Coordinated meeting, when the meeting volume is changed by using a room remote, the speaker on a Surface Hub or Teams Rooms device turns on. | For a trusted device such as a Surface Hub or Teams Rooms device that is set up to automatically join a Coordinated meeting when the primary device joins, the speaker turns on when a room remote is used to change the meeting volume. This issue occurs even though the audio settings on the device are turned off, and whether they're enabled or disabled. | Turn off proximity join and room remote capabilities on the trusted devices that automatically join a Coordinated meeting. |
| The central part of the console on a Teams Rooms device doesn't respond to touch and mouse input. | On some Microsoft Teams Rooms devices such as the Crestron Dell Optiplex 7080 that use a 4k monitor connected as the front-of-room display, the central portion of the display intermittently stops responding to touch and mouse controls. Despite this issue, the Teams Rooms app is functional and accepts inputs from a connected keyboard. |
Contact Microsoft Support for assistance to work around this issue. |
| Poor audio quality from a Teams Rooms device. | You might experience any of the following audio quality issues from a USB microphone or speaker that is connected to your Teams Rooms device:
This issue might be caused when a setting in the audio driver configuration to enhance audio quality is enabled. |
To fix the audio quality issue, disable the audio enhancement setting for the attached Teams-certified USB audio device by using the following steps:
|
Issues affecting Teams Rooms on Android devices
| Issue | Description | Workaround |
|---|---|---|
| Unable to join E2EE meeting using Teams Rooms on Android device. | When you use a Teams Rooms on Android device that is paired with a console, you're not able to join a Teams meeting that is set up with end-to-end encryption (E2EE). | Update to Teams Rooms on Android application 1449/1.0.96.2026249711 |
| [DGJ] Unable to join future Google meet meetings on Teams Rooms on Android via One-Touch join | When using a Teams Rooms on Android device to join a Google Meet meeting before its scheduled start time, the meeting cannot be joined using the One-Touch Join button | If you need to join a Google Meet meeting before its scheduled start time, use the Join by ID option |
Issues affecting Teams panel devices
| Issue | Description | Workaround |
|---|---|---|
| Line of business apps are unavailable | Line of Business (LoB) applications assigned to Teams panel resource accounts are not visible on the Teams panel home screen except for the Room Equipment application | No workaround is available at this time. |
Issues affecting Teams phone devices
| Issue | Description | Workaround |
|---|---|---|
| Incoming calls generate a "Just me" chat automatically. | When you receive a call from a main call queue on a Teams Phone, a "Just Me" chat is generated automatically in the Teams desktop app. This chat only includes you and it remains in the chat notifications list until you delete it manually. A new chat is generated with each incoming call. The problem occurs specifically when answering calls from a call queue on a Teams Phone device, but not when they're answered by using the Teams desktop app. |
To work around the issue, turn on Conference mode for the call queue. Use the following steps:
|
| Unable to save app configuration settings in the Teams admin center. | In the Microsoft Teams admin center you're not able to access the Allowed apps feature to remove applications that're installed on Teams Phone devices. This feature has been rolled back temporarily. | No workaround is available at this time. |
| Can't configure ringtones for line keys on a device. | When you use line keys on either a Yealink, AudioCodes, or Poly device that is provisioned with a Teams Shared Space license, you can't configure ringtones for individual line keys. | Configure a ringtone for a line key by using a user license, such as an E5 license instead. Use the following steps:
|
| Basic Calling displays instead of Advanced Calling. | You're using a Teams Shared Devices license that has the sign-in mode set to Common Area Phone (CAP) and is enabled for Advanced Calling. However, you see the Basic Calling experience instead of the expected Advanced Calling experience. This issue occurs after you update the device to version 1449/1.0.94.2026220406. | Use one of the following workarounds: |
Limitations
- Teams Rooms don't support High-Bandwidth Digital Content Protection (HDCP) inputs. Using an HDCP enabled input may cause issues that affect High-Definition Multimedia Interface (HDMI) ingest functionality, such as video and audio. To avoid these issues, make sure that the HDCP options are turned off for switches that are connected to Teams Rooms.
- Teams Rooms on Android devices that are paired with a console don't support the ability to join cross-cloud meetings. However devices that aren't paired with a console can join cross-cloud meetings by installing Teams Rooms on Android app version 1449/1.0.96.2025325609 or a later version.
- When you use the Call app on a Teams Rooms device to dial the toll number or conference ID for a Teams meeting, the conference bridge triggers multiple call flows. Because the Teams Rooms app is designed to support only one active call at a time, the call fails. Instead of using the Call app, join the meeting by using the Join with an ID option and entering the meeting ID.
- If you're in a call with another user who is on a Teams Rooms device, you can't transfer the call. The Teams Rooms app is designed to support only one call at a time.
- The meeting details that you export in the Microsoft Teams admin center includes the link speed of the Ethernet network interface that's used during the meeting. The details always display the default value of 10 Mbps. However, this value might not be accurate because Teams Rooms for Android devices can't fetch the exact value. The actual link speed might be faster than the default value.
- When you use multiple connected USB cameras of the same make and model with Teams Rooms on Windows, you experience the following issues:
- Inability to reliably select or control a specific physical camera.
- Unexpected changes in camera selection, framing behavior, and source switching.
- Change to the active camera setting after it is disconnected and reconnected, or after the Teams Rooms app or the meeting restart.
- Intelligent or enhanced framing experiences target the wrong camera.
Expected Behaviors
- Teams Rooms Pro and Teams Rooms Basic licenses include test service plans: Teams Rooms Test 1 & Teams Rooms Test 2. These service plans don't have any capabilities and can be ignored. They'll continue to display for the lifetime of the two SKUs.
- Teams Rooms on Android, Teams Phones, Teams panels, and Teams displays can be automatically signed out of Teams due to a policy block on the device registration service. See Signed out of Teams on Android devices for more information. Similarly, sign-in may continually loop when both the MFA and the Terms of Use (ToU) Conditional Access (CA) policies are used. The combination of MFA CA and ToU CA isn't supported. You should exclude it from being used. When only the MFA CA is used, make sure that it's enabled in Device Registration Services (DRS). For more information, see Conditional Access: Cloud apps, actions, and authentication context.