Skip to content

Commit 93cf3dd

Browse files
committed
Merge remote-tracking branch 'upstream/main' into AB#7238-Enable-openssh-verbose-logging
2 parents e1fc1b7 + fbb4e8d commit 93cf3dd

12 files changed

Lines changed: 208 additions & 18 deletions

File tree

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

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ appliesto:
2323
- Microsoft Teams
2424
search.appverid:
2525
- MET150
26-
ms.date: 09/24/2025
26+
ms.date: 10/06/2025
2727
---
2828
# Known issues with Teams on Android devices
2929

@@ -54,6 +54,7 @@ ms.date: 09/24/2025
5454
|Unable to assign speed dial to line keys on a sidecar|When you assign speed dial contacts to line keys on the sidecar that is connected to a touch phone device, they don't work.|No workaround is available for the speed dial contacts that you assigned by using the sidecar. However the speed dial contacts that're already set up and shared line delegates and other groups are automatically pinned on the sidecar.|
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.|
57+
|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.|
5758

5859
## Limitations
5960

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
---
22
title: Troubleshoot Custom Log Table Creation in Azure
33
description: Troubleshooting guide for custom log table creation in Azure.
4-
ms.date: 07/23/2025
5-
ms.reviewer: v-liuamson; v-gsitser
4+
ms.date: 09/30/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
68
ms.service: azure-monitor
79
ms.custom: Configure and Manage Log analytics tables
810
---
@@ -31,9 +33,11 @@ Users might receive an error message that states "Cannot read properties of unde
3133

3234
5. If the issue persists, try to refresh the Azure portal to make sure that all settings are updated.
3335

34-
## Reference
36+
## References
3537

3638
- [Create Custom Table in Azure](/azure/azure-monitor/vm/data-collection-log-json#create-custom-table)
3739
- [Data Collection Rule Best Practices](/azure/azure-monitor/data-collection/data-collection-rule-best-practices)
3840

39-
If the issue persists after you follow these steps, please open a support case for further assistance.
41+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
42+
43+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
---
22
title: Troubleshoot Custom Table Creation Errors in Azure
33
description: Troubleshooting guide for custom table creation errors in Azure.
4-
ms.date: 07/23/2025
5-
ms.reviewer: v-liuamson; v-gsitser
4+
ms.date: 09/30/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
68
ms.service: azure-monitor
79
ms.custom: Configure and Manage Log analytics tables
810
---
@@ -41,4 +43,6 @@ Users might receive an error message that indicates that properties of undefined
4143
- [Azure Monitor Overview](/azure/azure-monitor/fundamentals/overview)
4244
- [Create an Azure support request](/azure/azure-portal/supportability/how-to-create-azure-support-request)
4345

44-
If the issue persists after you following these steps, open a support case for further assistance.
46+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
47+
48+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-deleting-migrated-custom-tables.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
---
22
title: Troubleshoot Deleting Migrated Custom Tables in Log Analytics
33
description: Troubleshooting guide to deleting migrated custom tables in Log Analytics.
4-
ms.date: 07/24/2025
5-
ms.reviewer: v-liuamson; v-gsitser
4+
ms.date: 09/30/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
68
ms.service: azure-monitor
79
ms.custom: Configure and manage Log Analytics tables
810
---
@@ -29,4 +31,6 @@ To delete a migrated custom table, follow these steps by using the Azure Log Ana
2931

3032
- [Azure Log Analytics API documentation](/rest/api/loganalytics/)
3133

32-
If the issue persists after you follow these steps, open a support case for further assistance.
34+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
35+
36+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]
Lines changed: 46 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,46 @@
1+
---
2+
title: Tables Aren't Populated in a DNS Solution that's Deployed to a Workspace
3+
description: Troubleshooting guide for tables that don't get populated after you deploy a DNS solution to a workspace.
4+
ms.date: 09/30/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
8+
ms.service: azure-monitor
9+
ms.custom: Configure and manage Log Analytics tables
10+
---
11+
12+
# Tables aren't populated in a DNS solution that's deployed to a workspace
13+
14+
After you deploy a DNS solution to a workspace, you might experience an issue in which the deployment finishes successfully, but the tables don't get populated. This can occur if the table creation isn't defined in the ARM template or if there's insufficient data ingestion.
15+
16+
## Common issues and solutions
17+
18+
- **Issue**: The DNS solution deployment finishes, but tables aren't populated.
19+
- **Root cause**: Table creation might not be defined in the ARM template, or there may be no data ingestion.
20+
21+
## Resolution
22+
23+
To resolve the issue, follow these steps:
24+
25+
1. Verify the ARM template configuration:
26+
1. Check the DNS ARM template to make sure that it includes the definition for the table that you expect to be created.
27+
1. Navigate to the [Azure portal](https://portal.azure.com), and access the relevant resource group.
28+
1. Open the ARM template, and search for the table definition.
29+
30+
2. Check data ingestion:
31+
1. Verify that the Windows DNS Events via AMA Data Connector is installed and connected.
32+
1. Go to the **Azure Monitor** section in the Azure portal.
33+
1. Verify the data connector status, and make sure logs that are flowing into the workspace.
34+
35+
3. Manual table creation:
36+
1. If the table isn't created automatically, consider defining it manually within the ARM template.
37+
1. Use the Azure Resource Manager to update the template to have the required table definitions.
38+
39+
## References
40+
41+
- [Azure Monitor documentation](/azure/azure-monitor/)
42+
- [ARM template documentation](/azure/azure-resource-manager/templates/)
43+
44+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
45+
46+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-performance-logs-not-populating.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
---
22
title: Troubleshoot Performance Logs Not Populating in Azure Government
33
description: Troubleshooting guide for performance logs not populating in Azure Government.
4-
ms.date: 07/24/2025
5-
ms.reviewer: v-liuamson; v-gsitser
4+
ms.date: 09/30/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
68
ms.service: azure-monitor
79
ms.custom: Configure and Manage Log analytics tables
810
---
@@ -35,4 +37,6 @@ Users might experience issues if performance logs don't populate in Azure Govern
3537
- [Log Analytics workspace overview](/azure/azure-monitor/logs/log-analytics-workspace-overview)
3638
- [Create and manage alerts in Azure](/azure/azure-monitor/alerts/alerts-overview)
3739

38-
If the issue persists after you follow these steps, open a support case for further assistance.
40+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
41+
42+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
11
---
22
title: Understand and Mitigate High Data Consumption in Log Analytics
33
description: Provides instructions to resolve high data usage in Log Analytics.
4-
ms.date: 07/24/2025
5-
ms.reviewer: v-liuamson; v-gsitser
4+
ms.date: 09/30/2025
5+
author: JarrettRenshaw
6+
ms.author: jarrettr
7+
ms.reviewer: v-gsitser, v-ryanberg, neghuman, vikamala
68
ms.service: azure-monitor
79
ms.custom: Configure and Manage Log analytics tables
810
---
@@ -42,4 +44,6 @@ This article discusses high data consumption that occurs in Log Analytics worksp
4244
- [Best Practices for Cost Management](/azure/azure-monitor/fundamentals/best-practices-cost)
4345
- [Cost Management for Logs](/azure/azure-monitor/logs/cost-logs)
4446
45-
If the issue persists after you follow the solution steps, open a support case for further assistance.
47+
[!INCLUDE [azure-help-support](~/includes/azure-help-support.md)]
48+
49+
[!INCLUDE [Third-party contact disclaimer](~/includes/third-party-contact-disclaimer.md)]

support/azure/azure-monitor/toc.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,8 @@ items:
108108
items:
109109
- name: Understand and mitigate high data consumption in Log Analytics
110110
href: log-analytics/configure-and-manage-log-analytics-tables/understand-and-mitigate-high-data-consumption-log-analytics.md
111+
- name: Tables aren't populated in a DNS solution that's deployed to a workspace
112+
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-dns-table-issues.md
111113
- name: Troubleshoot custom table creation errors in Azure
112114
href: log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-table-creation-errors.md
113115
- name: Troubleshoot custom log table creation in Azure

support/power-platform/power-automate/desktop-flows/troubleshoot-desktop-flow-run-queue-errors.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ You can view lifecycle events for desktop flows in the queue from the monitor ru
3333

3434
## Cause
3535

36-
When no machines are available, Power Automate creates a queue to hold the desktop flows waiting to be run. Once a machine is available, the next desktop flow run will be selected to run based on [priority](/power-automate/desktop-flows/monitor-desktop-flow-queues#setting-a-priority) and request time. If no machine is available after six hours since the time it was requested, the desktop flow will time out and fail with a `NoCandidateMachine` error code.
36+
When no machines are available, Power Automate creates a queue to hold the desktop flows waiting to be run. Once a machine is available, the next desktop flow run will be selected to run based on [priority](/power-automate/desktop-flows/monitor-desktop-flow-queues#setting-a-priority) and request time. If no machine is available after twelve hours since the time it was requested, the desktop flow will time out and fail with a `NoCandidateMachine` error code.
3737

3838
As mentioned in the error message, this error means that the orchestrator can't find an available machine to run the desktop flow. This error occurs before the execution of the desktop flow starts.
3939

0 commit comments

Comments
 (0)