Skip to content

Commit e5144ae

Browse files
committed
Merge remote-tracking branch 'upstream/main' into AB#7273
2 parents 5d08606 + 6250d2f commit e5144ae

22 files changed

+401
-51
lines changed

Teams/teams-rooms-and-devices/bluetooth-disabled-status-unhealthy.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: The Bluetooth disabled status of a Teams Rooms device is Unhealthy
33
description: Resolves an issue that causes the Bluetooth disabled signal of a Microsoft Teams Rooms device to appear as Unhealthy.
4-
ms.reviewer: rebenite
4+
ms.reviewer: rebenite, v-lianna
55
ms.topic: troubleshooting
66
ms.date: 10/30/2023
7-
author: v-lianna
8-
ms.author:
7+
author: Cloud-Writer
8+
ms.author: meerak
99
manager: dcscontentpm
1010
audience: Admin
1111
search.appverid:

Teams/teams-rooms-and-devices/teams-rooms-known-issues-android.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -55,6 +55,7 @@ ms.date: 10/06/2025
5555
|Speed dial line key doesn't transfer an active call.|In older Teams Phones versions, you could transfer an active call by selecting a line key that is configured as a speed dial for a specific contact.<br/><br/>Beginning with Teams Phones version 1.7.0 1449/1.0.94.2025165302, you're only able to make an outgoing call to the speed dial after you select it from the **Transfer** menu.|If you want to transfer active calls to specific contacts, configure line keys as speed dials for those contacts and assign the **Transfer** and **Consult Transfer** menu options to the appropriate line keys.|
5656
|The screen hangs on Yealink phones when the headset is picked up.|On Yealink MP56 phones that are running version 1449/1.0.94.2025248901 of the Teams for Android app, the screen hangs or crashes when you pick up the headset to make an outbound call.|No workaround is available at this time.|
5757
|Can't see line keys on the home screen.|After you update your Teams Phones to version 1449/1.0.94.2025264001 of the Teams for Android app, you don't see any assigned line keys on the home screen.<br/><br/>This behavior is seen on non-touch phones such as Poly CCX 350 that have either the CAP or Premium CAP licenses.|No workaround is available at this time.|
58+
|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.<br/><br/>The problem occurs specifically when answering calls from a call queue on a Teams Phone device, but not when they are answered by using the Teams desktop app.|To work around the issue, turn on Conference mode for the call queue. Use the following steps:<br/><ol><li>In the Microsoft Teams admin center, select **Call queues**.</li><li>Select **Edit a call queue** > **Call answering**.</li><li>On the Call answering page, toggle the **Conference mode** button to turn it on.</li></ol>|
5859

5960
## Limitations
6061

Teams/teams-sign-in/resolve-sign-in-errors.md

Lines changed: 2 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,12 @@ ms.custom:
99
- CI 156289
1010
- CI 187814
1111
- CSSTroubleshoot
12-
ms.reviewer: billkau; meerak
12+
ms.reviewer: billkau; cafarric; meerak
1313
appliesto:
1414
- Microsoft Teams
1515
search.appverid:
1616
- MET150
17-
ms.date: 02/25/2025
17+
ms.date: 10/20/2025
1818
---
1919
# Resolve sign-in errors in Teams
2020

@@ -43,20 +43,6 @@ If your users encounter errors when they try to sign in to Microsoft Teams, use
4343

4444
This test verifies that the user account meets the requirements to sign in to Teams.
4545

46-
## Run the classic Teams sign-in troubleshooter
47-
48-
[!INCLUDE [Get Help troubleshooter note](../../includes/sara-note-new-teams.md)]
49-
50-
The [classic Teams sign-in troubleshooter](https://aka.ms/SaRA-TeamsSignIn-sarahome) helps you resolve classic Teams sign-in issues.
51-
52-
To run the troubleshooter, follow these steps:
53-
54-
1. Start the Get Help app.
55-
1. In the **Search** bar, enter *Unable to sign-in to Microsoft Teams*.
56-
1. Follow the instructions in the Get Help app to run the troubleshooter.
57-
58-
After the troubleshooter finishes, it displays the results and provides additional information about how to resolve the issue.
59-
6046
## Fix the issue manually
6147

6248
If you want to perform the checks and fix the issue manually, follow these steps:
@@ -65,8 +51,6 @@ If you want to perform the checks and fix the issue manually, follow these steps
6551

6652
The desktop app is configured to update automatically. However, if you find that the app is missing the latest update, follow the instructions to install it, and try again to sign in. If you still see an error when you try to sign in to Teams, go to step 3.
6753

68-
1. If you use a federated sign-in provider such as Active Directory Federation Services (AD FS), verify the AD FS sign-in configuration by using the [Microsoft 365 Single Sign-on Test](https://testconnectivity.microsoft.com/tests/SingleSignOn/input) in the Microsoft Remote Connectivity Analyzer.
69-
7054
1. Check the error code on the Teams sign-in screen. If the code is listed here, follow the provided guidance to fix the error. If the code isn't listed here, see [Why am I having trouble signing in to Microsoft Teams?](https://support.microsoft.com/topic/a02f683b-61a3-4008-9447-ee60c5593b0f)
7155

7256
- **0xCAA82EE7** or **0xCAA82EE2**

0 commit comments

Comments
 (0)