Skip to content

Commit 74c6555

Browse files
committed
Merge remote-tracking branch 'upstream/main' into AB#7273
2 parents 63e6680 + 818b519 commit 74c6555

File tree

81 files changed

+317
-177
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

81 files changed

+317
-177
lines changed

SharePoint/SharePointOnline/administration/domain-rename-faq.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: Cloud-Writer
55
ms.reviewer: PramodBalusu
66
ms.author: meerak
77
manager: dcscontentpm
8-
ms.date: 07/11/2024
8+
ms.date: 10/16/2025
99
audience: Admin
1010
ms.topic: troubleshooting
1111
ms.custom:
@@ -151,7 +151,7 @@ If OneDrive sync isn't stopped prior to the rename, issues might occur after the
151151
<details>
152152
<summary><b>I have more than 10,000 sites. When will my tenant be eligible for tenant rename?</b></summary>
153153

154-
If you have more than 10,000 sites, you must use Advanced Tenant Rename. This is available in SharePoint Advanced Management. Currently, Advanced Tenant Rename supports organizations that have up to 100,000 sites. We're working on increasing that limit further.
154+
If you have more than 10,000 sites, you must use Advanced Tenant Rename. This is available in SharePoint Advanced Management. There is no upper limit on the number of sites.
155155

156156
</details>
157157
<br/>

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/.openpublishing.redirection.azure.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6354,6 +6354,10 @@
63546354
"source_path": "app-service/ase-migration-faq.yml",
63556355
"redirect_url": "/troubleshoot/azure/app-service/welcome-app-service",
63566356
"redirect_document_id": true
6357+
},
6358+
{
6359+
"source_path": "app-service/app-service-compliance-wit.md",
6360+
"redirect_url": "/troubleshoot/azure/app-service/welcome-app-service"
63576361
},
63586362
{
63596363
"source_path": "azure-storage/files/alerts/files-troubleshoot-create-alerts.md",

support/azure/app-service/app-service-compliance-wit.md

Lines changed: 0 additions & 25 deletions
This file was deleted.

support/azure/app-service/toc.yml

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,21 +18,17 @@
1818
href: faqs-web-app-security.md
1919
- name: Availability, performance, and application FAQs
2020
href: web-apps-performance-faqs.md
21-
- name: App Service Compliance with PCI Standards 3.0 and 3.1
22-
href: app-service-compliance-wit.md
2321
- name: Backing up, restoring, and cloning
2422
href: backing-up-restoring-and-cloning-microsoft-azure-app-services.md
2523
- name: Built-in Linux containers FAQs
2624
href: faqs-app-service-linux.yml
2725
- name: Deployment FAQs for Web Apps
2826
href: web-apps-deployment-faqs.md
29-
- name: FAQs about App Service Environment migration
30-
href: ase-migration-faq.yml
3127
- name: FAQs about scaling web apps
3228
href: ./scaling-web-app-faq.yml
3329
- name: Fix HTTP 502 and HTTP 503 Errors
3430
href: troubleshoot-http-502-http-503.md
35-
- name: Map your own custom domain
31+
- name: Set up an existing custom domain
3632
href: /azure/app-service/app-service-web-tutorial-custom-domain
3733
- name: Node.js Best Practices and Troubleshooting Guide
3834
href: app-service-web-nodejs-best-practices-troubleshoot-guide.md

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)
Loading
Loading
Loading
Loading

0 commit comments

Comments
 (0)