You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Teams/teams-rooms-and-devices/teams-rooms-known-issues-android.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,6 +41,7 @@ ms.date: 07/22/2025
41
41
| Issue | Description | Workaround |
42
42
| --- | --- | --- |
43
43
|Signed out of Teams on Android devices | Teams Rooms on Android, Teams phone devices, Teams panels, and Teams displays are signed out of Teams automatically. | Follow the instructions provided in [Signed out of Teams on Android devices](./signed-out-of-teams-android-devices.md).|
44
+
|Unable to extract log files.|You're trying to extract a log file but either the log files are empty or you see an error message. This behavior can occur when the logs contain partially corrupted zip files or log files.|Contact Microsoft Support by filing a request at [SERVICENOW](https://microsoft.service-now.com/sp?id=sc_cat_item&sys_id=0baac5bcdb0ca414b720f337689619ce&sysparm_category=8b859929136eea002620b0912244b066).|
44
45
45
46
## Issues with Teams phones
46
47
@@ -51,7 +52,6 @@ ms.date: 07/22/2025
51
52
|Can't resume a call after using **Consult first** option on Teams phones | After using the **Consult first** option in the **Transfer** menu when you select the **Resume** option to resume the call, the call fails. | End the call made by using the **Consult first** option and then resume the original call.|
52
53
|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.|
53
54
|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.|
54
-
|Unable to extract log files.|You're trying to extract a log file but either the log files are empty or you see an error message. This behavior can occur when the logs contain partially corrupted zip files or log files.|Contact Microsoft Support by filing a request at [SERVICENOW](https://microsoft.service-now.com/sp?id=sc_cat_item&sys_id=0baac5bcdb0ca414b720f337689619ce&sysparm_category=8b859929136eea002620b0912244b066).|
Copy file name to clipboardExpand all lines: support/azure/automation/runbooks/job-not-start-as-expected.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Troubleshoot Issues with Runbook Execution Start Time
3
3
description: Discusses an issue where jobs don't start as expected in Azure Automation.
4
-
ms.date: 06/27/2025
4
+
ms.date: 07/23/2025
5
5
ms.reviewer: adoyle, v-weizhu
6
6
ms.service: azure-automation
7
7
ms.custom: sap:Runbook not working as expected
@@ -12,7 +12,7 @@ Process automation in Azure Automation allows you to create and manage PowerShel
12
12
13
13
## Service-level agreement (SLA)
14
14
15
-
The SLA for runbook automation is 30 minutes. It's expected that 99.999 percent of runbooks start within five minutes of the scheduled time. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
15
+
The SLA for runbook automation is 30 minutes. It's expected that 99.9 percent of runbooks start within 30 minutes of the planned start time. For more information, see [SLAs for Online Services](https://www.microsoft.com/licensing/docs/view/Service-Level-Agreements-SLA-for-Online-Services).
16
16
17
17
The *SLA for the Automation Service - Process Automation* defines the following terms:
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
10
10
---
11
11
# Troubleshoot API server and etcd problems in Azure Kubernetes Services
@@ -16,7 +16,7 @@ Microsoft has tested the reliability and performance of the API server at a scal
16
16
17
17
## Prerequisites
18
18
19
-
-[Azure CLI](/cli/azure/install-azure-cli).
19
+
-The [Azure CLI](/cli/azure/install-azure-cli).
20
20
21
21
- The Kubernetes [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/) tool. To install kubectl by using Azure CLI, run the [az aks install-cli](/cli/azure/aks#az-aks-install-cli) command.
22
22
@@ -89,7 +89,40 @@ Although it's helpful to know which clients generate the highest request volume,
89
89
90
90
### Step 2: Identify and chart the average latency of API server requests per user agent
91
91
92
-
To identify the average latency of API server requests per user agent as plotted on a time chart, run the following query:
92
+
**1.a.** Use the API Server Resource Intensive Listing Detector in Azure Portal
93
+
94
+
> **New:** Azure Kubernetes Service now provides a built-in analyzer to help you identify agents making resource-intensive LIST calls, which are a leading cause of API server and etcd performance issues.
95
+
96
+
**How to access the detector:**
97
+
98
+
1. Open your AKS cluster in the Azure portal.
99
+
2. Go to **Diagnose and solve problems**.
100
+
3. Click **Cluster and Control Plane Availability and Performance**.
101
+
4. Select **API server resource intensive listing detector**.
102
+
103
+
This detector analyzes recent API server activity and highlights agents or workloads generating large or frequent LIST calls. It provides a summary of potential impacts, such as request timeouts, increased 408/503 errors, node instability, health probe failures, and OOM-Kills in API server or etcd.
104
+
105
+
#### How to interpret the detector output
106
+
107
+
-**Summary:**
108
+
Indicates if resource-intensive LIST calls were detected and describes possible impacts on your cluster.
109
+
-**Analysis window:**
110
+
Shows the 30-minute window analyzed, with peak memory and CPU usage.
111
+
-**Read types:**
112
+
Explains whether LIST calls were served from the API server cache (preferred) or required fetching from etcd (most impactful).
113
+
-**Charts and tables:**
114
+
Identify which agents, namespaces, or workloads are generating the most resource-intensive LIST calls.
115
+
116
+
> Only successful LIST calls are counted. Failed or throttled calls are excluded.
117
+
118
+
The analyzer also provides actionable recommendations directly in the Azure portal, tailored to the detected patterns, to help you remediate and optimize your cluster.
119
+
120
+
> [!NOTE]
121
+
> The API server resource intensive listing detector is available to all users with access to the AKS resource in the Azure portal. No special permissions or prerequisites are required.
122
+
>
123
+
> After identifying the offending agents and applying the above recommendations, you can further use [Priority and Fairness](https://kubernetes.io/docs/concepts/cluster-administration/flow-control/) or refer to [this section](/troubleshoot/azure/azure-kubernetes/create-upgrade-delete/troubleshoot-apiserver-etcd?branch=pr-en-us-9260&tabs=resource-specific#cause-3-an-offending-client-makes-excessive-list-or-put-calls) to throttle or isolate problematic clients.
124
+
125
+
**1.b.** Additionally, you can also run following query to identify the average latency of API server requests per user agent as plotted on a time chart:
description: Troubleshooting guide for Azure activity log download issues
4
+
ms.date: 07/22/2025
5
+
ms.reviewer: v-liuamson; v-gsitser
6
+
ms.service: azure-monitor
7
+
ms.custom: I can’t configure export of Activity Logs
8
+
---
9
+
10
+
# Troubleshooting activity log download issues
11
+
12
+
When users try to download activity logs from Microsoft Azure, they might receive error messages that indicate that the CSV file wasn't prepared. This issue often occurs if the requested logs exceed a certain volume and cause the process to fail. Understanding the root cause and implementing the right solutions can help resolve this issue efficiently.
13
+
14
+
## Common issues and solutions
15
+
16
+
-**Issue**: The download process fails because an excessive number of logs are requested. This activity generates a "file not found" error.
17
+
-**Solution**: Reduce the range of time during which logs are requested to minimize the volume and prevent errors.
18
+
19
+
### Instructions to resolve download failures
20
+
21
+
1. Check the error message to verify that it relates to the CSV file preparation failure.
22
+
2. Navigate to the Azure portal, and access the **Activity Logs** section. Reduce the time range that you're trying to download logs for. This change can help decrease the number of logs that are processed.
23
+
3. Clear your browser cache to make sure that no outdated data is causing issues.
24
+
4. If possible, break down the log requests into smaller batches to avoid overwhelming the system.
25
+
5. Make sure that the storage account where the logs are stored is reachable and correctly configured.
26
+
27
+
## FAQ: Azure activity log download
28
+
29
+
**Q1: Why does the download fail?**
30
+
31
+
**A1:** The download might fail if the number of requested logs is excessive and prevents the system from being able to process the logs.
32
+
33
+
**Q2: How can I avoid download failures?**
34
+
35
+
**A2:** To avoid this issue, prevent the system from being overwhelmed. To do this, reduce the time range for the download, and request logs in smaller batches.
title: Troubleshoot Export of Audit Logs to Another Tenant
3
+
description: This article provides guidance to resolve permissions-related errors when you export audit logs to another tenant.
4
+
ms.date: 07/22/2025
5
+
ms.reviewer: v-liuamson; v-gsitser
6
+
ms.service: azure-monitor
7
+
ms.custom: I can’t configure export of Activity Logs
8
+
---
9
+
10
+
# Troubleshoot export of audit logs to another tenant
11
+
12
+
When users try to export audit logs from one tenant to another by using Microsoft Azure Lighthouse, they might experience permissions-related errors. This article provides guidance to resolve these issues.
13
+
14
+
## Common issues and solutions
15
+
16
+
-**Issue**: Permissions errors occur when a user configures diagnostic settings for exporting audit logs.
17
+
-**Root cause**: The user lacks the required permissions on the target workspace or has an incorrect role assignment.
18
+
19
+
### Instructions to resolve export issues
20
+
21
+
1. Verify the user's permissions:
22
+
1. Make sure that the user has the necessary permissions to perform actions on the target workspace.
23
+
1. Navigate to the Azure portal, and check the user's role assignments in the **Access Control (IAM)** section.
24
+
25
+
2. Reset the guest invitation:
26
+
1. If the user is a guest, reset the invitation status to ensure proper linkage between home and resource tenants.
27
+
1. Follow the steps in [Reset Guest Invitation Status](/entra/external-id/reset-redemption-status).
28
+
29
+
3. Check the role assignments:
30
+
1. Verify that the user has the appropriate roles assigned, such as **Log Analytics Contributor** or **Reader**.
31
+
1. Use the Azure portal to assign roles, if it's necessary.
32
+
33
+
4. Review ARM template role definitions:
34
+
1. Make sure that the ARM template that's used for deployment specifies the correct `RoleDefinitionId` value.
35
+
1. Adjust the template as necessary to include the required permissions.
36
+
37
+
5. Test the configuration:
38
+
1. Test the configuration to make sure that logs are exported successfully.
39
+
1. Monitor the Azure activity logs for any more error messages or warnings.
40
+
41
+
## References
42
+
43
+
-[Manage Access to Log Analytics workspaces](/azure/azure-monitor/logs/manage-access?tabs=portal#workspace-permissions)
44
+
-[Azure role assignments](/azure/role-based-access-control/role-assignments-portal)
45
+
46
+
If the issue persists after you follow these steps, open a support case for further assistance.
title: Understanding and Managing Diagnostic Settings Retention
3
+
description: Provides guidance for understanding and managing diagnostic settings retention.
4
+
ms.date: 07/22/2025
5
+
ms.reviewer: v-liuamson; v-gsitser
6
+
ms.service: azure-monitor
7
+
ms.custom: I can’t configure export of Activity Logs
8
+
---
9
+
10
+
# Understanding and managing diagnostic settings retention
11
+
12
+
When you manage Azure resources, you might experience issues that are related to the transition from diagnostic settings storage retention to Azure Storage lifecycle management. This article provides guidance to handle these issues effectively.
13
+
14
+
## Common issues and solutions
15
+
16
+
-**Issue**: Users might notice that templates aren't displayed when they try to verify resources that are affected by the transition from legacy solutions to diagnostic settings.
17
+
-**Root cause**: The automatic switch from activity log solutions to diagnostic settings might cause confusion if users don't fully understand diagnostic settings retention.
18
+
19
+
### Instructions to resolve diagnostic settings issues
20
+
21
+
1. Determine how resources are affected:
22
+
1. Navigate to the Azure portal > **All Services**.
23
+
1. Select **Resource Manager**.
24
+
1. Select **Deploy**, and then select **Templates** in the left pane.
25
+
1. Check whether any resources are affected by the transition.
26
+
27
+
2. To determine whether legacy solutions are in use, run the following PowerShell command:
If no output is returned, legacy solutions aren't in use, and no further action is required.
37
+
38
+
3. Understand that the transition to diagnostic settings is automatic. If your environment is already using diagnostic settings, no additional steps are necessary.
0 commit comments