Skip to content

Commit ffd34a0

Browse files
committed
2 parents 9387aa6 + 9792dd6 commit ffd34a0

File tree

34 files changed

+108
-90
lines changed

34 files changed

+108
-90
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Known issues with Teams Rooms on Windows
33
description: Provides a list of known issues for Teams Rooms on Windows.
44
ms.author: meerak
55
author: Cloud-Writer
6-
ms.reviewer: mattslomka, sohailta, garyanselme, czawideh
6+
ms.reviewer: mattslomka
77
manager: dcscontentpm
88
audience: ITPro
99
ms.topic: troubleshooting
@@ -22,7 +22,7 @@ appliesto:
2222
- Microsoft Teams
2323
search.appverid:
2424
- MET150
25-
ms.date: 10/07/2025
25+
ms.date: 10/16/2025
2626
---
2727
# Known issues with Teams Rooms on Windows
2828

@@ -50,7 +50,7 @@ ms.date: 10/07/2025
5050
|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.|
5151
|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.<br/><br/>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.|
5252
|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's connected to your Teams Rooms device: <ul><li> - Echo sent to remote participants on the call.</li><li> - Low audio quality sent to remote participants on the call.</li><li> - Decrease in audio quality as the call progresses.</li><li> - Low volume in speakers within the room.</li></ul><br/>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:<ol><li>Select **Settings** on the Teams Rooms device console.</li><li>Select **Windows Settings**, and sign in to the Teams Rooms device as an administrator.</li><li>Open **Control Panel**.</li><li>Select **Hardware and Sound** > **Sound**.</li><li>On the **Playback** tab, select the affected audio device and then select **Properties**.</li><li>Select the **Advanced** tab.</li><li>In the **Signal Enhancements** section, uncheck **Enable audio enhancements**, and then select **OK**.</li><li>Select the **Recording** tab and repeat steps 5, 6 & 7 for the same audio device </li><li>Select **OK** and then close **Control Panel.</li><li>Restart the Teams Rooms device.</li></ol>|
53-
|Lenovo Teams Rooms devices display BitLocker recovery screen.|When you try to update Windows from 23H2 to 24H2 on a Lenovo Teams Rooms for Windows device that has BitLocker enabled, the update might fail and you see a BitLocker recovery screen instead.|Perform the following actions:<ol><li>Pause the Windows update on the affected device.</li><li>In the [Microsoft Teams Rooms Pro Management portal](/microsoftteams/rooms/update-management#update-management-experience-walk-through), pause the Teams Rooms app update to versions 5.3.205.0 and 5.4.210.0.</li></ol><br/>If one of these versions of the Teams Rooms app has already been installed on your device and it now displays the BitLocker recovery screen, enter the BitLocker recovery key to restore functionality.|
53+
|Lenovo Teams Rooms devices display BitLocker recovery screen.|When you try to update Windows from 23H2 to 24H2 on a Lenovo Teams Rooms for Windows device that has BitLocker enabled, the update might fail and you see a BitLocker recovery screen instead.|The Windows update to 24H2 on Lenovo devices is [blocked](https://support.microsoft.com/topic/kb5070632-some-devices-are-temporarily-unable-to-upgrade-to-windows-11-version-24h2-or-25h2-c3dd7515-21e6-46ce-9a9d-64a8882ef5ca) due to this issue. <br/><br/>You can safely upgrade the versions of the Teams Rooms app to 5.3.205.0 and 5.4.210.0 on the affected devices which will remain on Windows version 23H2. <br/><br/>If one of these versions of the Teams Rooms app is already installed and the device displays the BitLocker recovery screen, enter the BitLocker recovery key to restore functionality.|
5454

5555
## Limitations
5656

support/azure/azure-kubernetes/connectivity/dns/troubleshoot-localdns.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.topic: troubleshooting-general
1313
---
1414
# Troubleshoot issues with LocalDNS on Azure Kubernetes Service (AKS)
1515

16-
This article discusses how to create a troubleshooting workflow to fix Domain Name System (DNS) resolution problems in Azure Kubernetes Service (AKS), when using LocalDNS. To learn more about LocalDNS, you can read our overview in [DNS Resolution in Azure Kubernetes Service (AKS)](https://learn.microsoft.com/azure/aks/dns-concepts#localdns-in-azure-kubernetes-service-preview).
16+
This article discusses how to create a troubleshooting workflow to fix Domain Name System (DNS) resolution problems in Azure Kubernetes Service (AKS), when using LocalDNS. To learn more about LocalDNS, you can read our overview in [DNS Resolution in Azure Kubernetes Service (AKS)](/azure/aks/dns-concepts#localdns-in-azure-kubernetes-service-preview).
1717

1818
## Prerequisites
1919

@@ -164,7 +164,7 @@ az aks nodepool update --name mynodepool1 --cluster-name myAKSCluster --resource
164164
165165
Option 2 - Enable Query logging on a specific node
166166
167-
You can diagnose LocalDNS issues on a specific node by temporarily rewriting the LocalDNS configuration. You can [connect to the node](https://learn.microsoft.com/azure/aks/node-access#connect-using-kubectl-debug) manually and update the core file used by LocalDNS, only restarting the specific LocalDNS service.
167+
You can diagnose LocalDNS issues on a specific node by temporarily rewriting the LocalDNS configuration. You can [connect to the node](/azure/aks/node-access#connect-using-kubectl-debug) manually and update the core file used by LocalDNS, only restarting the specific LocalDNS service.
168168
169169
**Note:** The changes made this way are ephemeral in nature and don't persist once the troubleshooting is complete.
170170
@@ -316,11 +316,11 @@ Jul 03 16:59:07 aks-userpool-24995383-vmss000000 localdns-coredns[2491520]: [INF
316316
If you see logs for your traffic, the pod is able to reach the LocalDNS service.
317317
318318
## Next steps
319-
If the above logs fail to help root cause the issue, you can enable [Query logging for CoreDNS](https://learn.microsoft.com/azure/aks/coredns-custom#enable-dns-query-logging) to validate if CoreDNS is working as intended.
319+
If the above logs fail to help root cause the issue, you can enable [Query logging for CoreDNS](/azure/aks/coredns-custom#enable-dns-query-logging) to validate if CoreDNS is working as intended.
320320
321321
[!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]
322322
323323
[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]
324324
325-
[!INCLUDE [Third-party contact disclaimer](../../../../includes/third-party-contact-disclaimer.md)]
325+
326326

support/azure/azure-kubernetes/connectivity/tcp-timeouts-kubetctl-third-party-tools-connect-api-server.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,9 @@ title: TCP time-outs when kubectl or other 3rd-party tools connect to API
33
description: Troubleshoot TCP time-outs that occur when kubectl or other third-party tools connect to the API server in Azure Kubernetes Service (AKS).
44
ms.topic: article
55
ms.date: 06/03/2024
6-
author: azureuser
7-
ms.author: azureuser
6+
author: JarrettRenshaw
7+
ms.author: jarrettr
8+
ms.service: azure-kubernetes-service
89
ms.custom: sap:Connectivity,innovation-engine
910
---
1011

support/azure/azure-kubernetes/create-upgrade-delete/error-code-badrequest-or-invalidclientsecret.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,7 @@ ms.topic: article
55
ms.date: 06/13/2024
66
author: axelgMS
77
ms.author: axelg
8+
ms.service: azure-kubernetes-service
89
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool), innovation-engine
910
---
1011

support/azure/azure-kubernetes/create-upgrade-delete/pod-stuck-crashloopbackoff-mode.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Pod is stuck in CrashLoopBackOff mode
33
description: Troubleshoot a scenario in which a pod is stuck in CrashLoopBackOff mode on an Azure Kubernetes Service (AKS) cluster.
44
ms.date: 04/07/2025
5-
author: VikasPullagura-MSFT
6-
ms.author: vipullag
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
77
editor: v-jsitser, addobres
88
ms.reviewer: chiragpa, nickoman, cssakscic, v-leedennis, addobres
99
ms.service: azure-kubernetes-service

support/azure/azure-kubernetes/extensions/cluster-extension-deployment-errors.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,8 @@
22
title: Troubleshoot errors when deploying extensions in an AKS cluster
33
description: Learn how to troubleshoot errors that occur when you deploy cluster extensions in an Azure Kubernetes Service (AKS) cluster.
44
ms.date: 03/26/2024
5-
author: maanasagovi
6-
ms.author: maanasagovi
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
77
editor: v-jsitser
88
ms.reviewer: nickoman, v-weizhu, v-leedennis
99
ms.service: azure-kubernetes-service

support/azure/azure-monitor/app-insights/agent/status-monitor-v2-troubleshoot.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
22
title: Azure Application Insights Agent troubleshooting and known issues
33
description: Review Application Insights Agent known issues and troubleshooting examples. Works with ASP.NET web apps hosted on-premises, in virtual machines, or on Azure.
4-
ms.date: 06/24/2024
4+
ms.date: 10/16/2025
55
editor: v-jsitser
6-
ms.reviewer: aaronmax, nzamoralopez, toddfous, v-leedennis
6+
ms.reviewer: aaronmax, nzamoralopez, toddfous, jarrettr
77
ms.service: azure-monitor
88
#Customer intent: As an Application Insights user, I want to understand the known issues for the Application Insights Agent and how to troubleshoot common issues so that I can use Application Insights and the Agent effectively.
9-
ms.custom: sap:Manual Instrumentation using SDK, Open Telemetry or by installing Agent
9+
ms.custom: sap:Missing or incorrect telemetry and performance issues
1010
---
1111

1212
# Troubleshoot Azure Application Insights Agent (formerly Status Monitor v2)

support/azure/azure-monitor/toc.yml

Lines changed: 19 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -74,28 +74,28 @@ items:
7474
href: app-insights/data/how-to-update-third-party-server-configuration.md
7575
- name: Node.js
7676
href: app-insights/data/troubleshoot-app-insights-nodejs.md
77-
- name: Application Insights experiences
77+
- name: Application Insights portal experiences
7878
items:
7979
- name: Troubleshoot Application map issues
8080
href: app-insights/troubleshoot-application-map-issues.md
81-
- name: Troubleshoot Azure Application Insights availability monitoring
82-
items:
83-
- name: Availability monitoring common issues FAQ
84-
href: app-insights/availability/availability-monitoring-common-issues-faq.yml
85-
- name: Diagnose ping test failures
86-
href: app-insights/availability/diagnose-ping-test-failure.md
87-
- name: Intermittent test failure and protocol violation error
88-
href: app-insights/availability/intermittent-test-failure-protocol-error.md
89-
- name: Use availability tests on an internal server behind a firewall
90-
href: app-insights/availability/internal-server-availability-tests-firewall.md
91-
- name: Daily cap unexpected behaviors
92-
href: app-insights/availability/daily-cap-unexpected-behaviors.md
93-
- name: Missing CPU Total and Committed Memory metrics
94-
href: app-insights/availability/missing-cpu-total-committed-memory-metrics.md
95-
- name: Portal connectivity issues
96-
href: app-insights/availability/troubleshoot-portal-connectivity.md
97-
- name: Troubleshoot user behavior analytics tools in Azure Application Insights
98-
href: app-insights/availability/usage-troubleshoot.md
81+
- name: Availability Tests
82+
items:
83+
- name: Availability monitoring common issues FAQ
84+
href: app-insights/availability/availability-monitoring-common-issues-faq.yml
85+
- name: Diagnose ping test failures
86+
href: app-insights/availability/diagnose-ping-test-failure.md
87+
- name: Intermittent test failure and protocol violation error
88+
href: app-insights/availability/intermittent-test-failure-protocol-error.md
89+
- name: Use availability tests on an internal server behind a firewall
90+
href: app-insights/availability/internal-server-availability-tests-firewall.md
91+
- name: Daily cap unexpected behaviors
92+
href: app-insights/availability/daily-cap-unexpected-behaviors.md
93+
- name: Missing CPU Total and Committed Memory metrics
94+
href: app-insights/availability/missing-cpu-total-committed-memory-metrics.md
95+
- name: Portal connectivity issues
96+
href: app-insights/availability/troubleshoot-portal-connectivity.md
97+
- name: Troubleshoot user behavior analytics tools in Azure Application Insights
98+
href: app-insights/availability/usage-troubleshoot.md
9999
- name: Status Monitor and Change Analysis
100100
items:
101101
- name: Troubleshoot Azure Application Insights Agent (formerly Status Monitor v2)

support/azure/cloud-services/extended/availability/retrieve-cloud-service-extended-support-detail-powershell.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,10 +4,10 @@ description: Describes how to get the Azure Cloud Service (extended support) con
44
ms.date: 04/01/2024
55
ms.topic: how-to
66
ms.reviewer: maheshallu, piw, v-weizhu
7-
ms.author: zhangjerry
7+
author: JarrettRenshaw
8+
ms.author: jarrettr
89
ms.service: azure-cloud-services-extended-support
910
ms.custom: sap:Service Availability and Performance
10-
author: JerryZhangMS
1111
---
1212
# Retrieve Azure Cloud Service (extended support) detail via PowerShell
1313

support/azure/cloud-services/extended/connectivity/allow-internet-traffic-cses-application-gateway.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,8 @@ title: Allow internet traffic to Cloud Services (extended support) by using an a
33
description: Configure traffic from the internet to Azure Cloud Services (extended support) by using a public application gateway together with an internal load balancer.
44
ms.date: 02/19/2024
55
ms.topic: how-to
6-
author: JerryZhangMS
7-
ms.author: zhangjerry
6+
author: JarrettRenshaw
7+
ms.author: jarrettr
88
editor: v-jsitser
99
ms.reviewer: maheshallu, piw, v-leedennis
1010
ms.service: azure-cloud-services-extended-support

0 commit comments

Comments
 (0)