Merge branch 'main' into v-liuamson-CI6613

Amson Liu · web-flow · commit 6bb040a3ab1b · 2025-07-23T12:40:04.000-04:00
diff --git a/Teams/teams-rooms-and-devices/teams-rooms-known-issues-android.md b/Teams/teams-rooms-and-devices/teams-rooms-known-issues-android.md
@@ -23,17 +23,25 @@ appliesto:
   - Microsoft Teams
 search.appverid: 
   - MET150
-ms.date: 07/01/2025
+ms.date: 07/22/2025
 ---
 # Known issues with Teams Rooms on Android
 
 <!-- If you get word that one of these issues no longer applies, contact meerak@microsoft.com to EoL the corresponding KB.  -->
 
+## Issues affecting Teams meeting room devices
+
+| Issue  |  Description | Workaround |
+| --- | --- | --- |
+|Unable to pair Yealink MeetingBar A40 device with CTP25 touch panel.|You might experience intermittent or failed pairing attempts between a Yealink MeetingBar A40 device and a CTP25 touch panel that are running the following firmware versions:<br/><br/>A40 device: 289.320.0.60<br/>CTP25 touch panel: 311.320.0.55<br/><br/>In some instances, the device might revert to an unpaired state shortly after initialization, or the touch panel might remain stuck on the pairing screen without displaying a code.|No workaround is available at this time.|
+|Logitech Rally Bar device is failing during remote login authentication.|You're able to sign in to a LogiTech VR1009 Rally Bar device locally but it signs out if an attempt is made to log in remotely. In this situation you might see Entra ID error codes 530003, 530002, and others.|No workaround is available at this time.|
+
 ## Issues affecting multiple devices
 
 | Issue  |  Description | Workaround |
 | --- | --- | --- |
 |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).|
+|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).|
 
 ## Issues with Teams phones
 
@@ -65,6 +73,6 @@ For issues with Teams devices offered by third-party providers, contact their in
 - Logitech: [Logitech Support](https://support.logi.com/hc/)
 - Crestron: [Crestron Support](https://support.crestron.com/)
 - Poly: [Poly Support](https://www.poly.com/us/support)
-- Yealink: [Yealink Support](https://support.yealink.com/portal/home)
+- Yealink: [Yealink Support](https://support.yealink.com/us/portal/home)
 
 [!INCLUDE [Third-party disclaimer](../../includes/third-party-contact-disclaimer.md)]
diff --git a/support/azure/automation/runbooks/job-not-start-as-expected.md b/support/azure/automation/runbooks/job-not-start-as-expected.md
@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot Issues with Runbook Execution Start Time
 description: Discusses an issue where jobs don't start as expected in Azure Automation.
-ms.date: 06/27/2025
+ms.date: 07/23/2025
 ms.reviewer: adoyle, v-weizhu
 ms.service: azure-automation
 ms.custom: sap:Runbook not working as expected
@@ -12,7 +12,7 @@ Process automation in Azure Automation allows you to create and manage PowerShel
 
 ## Service-level agreement (SLA)
 
-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).
+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).
 
 The *SLA for the Automation Service - Process Automation* defines the following terms:
 
diff --git a/support/azure/azure-kubernetes/create-upgrade-delete/troubleshoot-apiserver-etcd.md b/support/azure/azure-kubernetes/create-upgrade-delete/troubleshoot-apiserver-etcd.md
@@ -3,9 +3,9 @@ title: Troubleshoot API server and etcd problems in AKS
 description: Provides a troubleshooting guide for API server and etcd problems in Azure Kubernetes Services.
 author: seguler
 ms.author: segule
-ms.date: 11/15/2024
+ms.date: 07/22/2025
 ms.service: azure-kubernetes-service
-ms.reviewer: mikerooney, v-weizhu, axelg, josebl, aritraghosh, v-leedennis
+ms.reviewer: kthakar1990, v-weizhu, axelg, josebl, aritraghosh, v-leedennis, v-liuamson
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
 ---
 # 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
 
 ## Prerequisites
 
-- [Azure CLI](/cli/azure/install-azure-cli).
+- The [Azure CLI](/cli/azure/install-azure-cli).
 
 - 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.
 
@@ -89,7 +89,40 @@ Although it's helpful to know which clients generate the highest request volume,
 
 ### Step 2: Identify and chart the average latency of API server requests per user agent
 
-To identify the average latency of API server requests per user agent as plotted on a time chart, run the following query:
+**1.a.** Use the API Server Resource Intensive Listing Detector in Azure Portal
+
+> **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.
+
+**How to access the detector:**
+
+1. Open your AKS cluster in the Azure portal.
+2. Go to **Diagnose and solve problems**.
+3. Click **Cluster and Control Plane Availability and Performance**.
+4. Select **API server resource intensive listing detector**.
+
+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.
+
+#### How to interpret the detector output
+
+- **Summary:**  
+  Indicates if resource-intensive LIST calls were detected and describes possible impacts on your cluster.
+- **Analysis window:**  
+  Shows the 30-minute window analyzed, with peak memory and CPU usage.
+- **Read types:**  
+  Explains whether LIST calls were served from the API server cache (preferred) or required fetching from etcd (most impactful).
+- **Charts and tables:**  
+  Identify which agents, namespaces, or workloads are generating the most resource-intensive LIST calls.
+
+> Only successful LIST calls are counted. Failed or throttled calls are excluded.
+
+The analyzer also provides actionable recommendations directly in the Azure portal, tailored to the detected patterns, to help you remediate and optimize your cluster.
+
+> [!NOTE]
+> 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.
+> 
+> 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.
+
+**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:
 
 ### [Resource-specific](#tab/resource-specific)
 
diff --git a/support/azure/azure-monitor/activity-logs/config-export/centralized-configuration-of-activity-logs-to-event-hub.md b/support/azure/azure-monitor/activity-logs/config-export/centralized-configuration-of-activity-logs-to-event-hub.md
@@ -0,0 +1,50 @@
+---
+title: Centralized Configuration of Activity Logs to Event Hubs
+description: Provides guidance to set up Azure Activity Logs to be centrally exported to a single Event Hub.
+ms.date: 07/22/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: I can’t configure export of Activity Logs
+---
+
+# Centralized Configuration of Activity Logs to Event Hubs
+
+## Introduction
+
+This article provides guidance for setting up Azure Activity Logs to be centrally exported to a single hub in Azure Event Hubs. This setup is useful for organizations that want to streamline log management across multiple Azure subscriptions and forward logs to third-party SIEM solutions.
+
+Organizations often require a centralized approach to manage Activity Logs across numerous subscriptions. This guide discusses common challenges and considerations for configuring Azure Policies to automate streaming these logs to a specified event hub.
+
+## Instructions to configure Activity Logs
+
+1. **Create an Azure Policy for Activity Logs:**
+   - Navigate to the Azure portal, and access the **Azure Policy** service.
+   - Create a policy definition by using the JSON file that's provided in the community example. This policy should automate the enablement of activity log diagnostic settings across all subscriptions under a management group.
+
+2. **Assign the Policy to Management Group:**
+   - Assign the newly created policy to the desired management group that contains the required subscriptions.
+   - Make sure that the policy is set to send data to the specified Event Hub.
+
+3. **Configure Log Analytics Workspace:**
+   - Access **Log Analytics Workspace** in the Azure portal.
+   - Set up data export rules to forward logs from the Log Analytics Workspace to the event hub. Specify the source table as `AzureActivity` and the destination as the central event hub.
+
+4. **Verify event hub configuration:**
+   - Make sure that the event hub is configured to handle the expected log volume from all subscriptions.
+   - Review performance benchmarks and adjust the event hub tier if it's necessary to manage logs efficiently.
+
+5. **Monitor and adjust:**
+   - Regularly monitor the event hub performance and log flow.
+   - Adjust configurations as necessary to optimize performance and cost.
+
+## Common issues and solutions
+
+- **Performance concerns:** If the event hub experiences difficulty in handling the log volume, consider upgrading the tier or distributing logs across multiple hubs.
+- **Policy Limitations:** Azure Policy might require manual steps for each subscription. Make sure that all configurations are correctly applied.
+
+## Reference
+
+- [Azure Policy Assignment to Enable Activity Log on Subscription](/azure/policy-assignment-to-enable-activity-log-on-subscription)
+- [Azure Event Hubs Overview](/azure/event-hubs/event-hubs-about)
+
+If the issue persists after you follow these steps, open a support case for further assistance.
diff --git a/support/azure/azure-monitor/activity-logs/config-export/troubleshoot-azure-cli-configuration-issues.md b/support/azure/azure-monitor/activity-logs/config-export/troubleshoot-azure-cli-configuration-issues.md
@@ -0,0 +1,44 @@
+---
+title: Troubleshoot Azure CLI Configuration Issues
+description: Troubleshooting guide for Azure CLI configuration issues.
+ms.date: 07/22/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: I can’t configure export of activity logs
+---
+
+# Troubleshoot Azure CLI configuration issues
+
+This article discusses issues that are related to configuring Microsoft Azure to export activity logs by using PowerShell or CLI. Because of missing proxy certificates, users might experience difficulties when they try to run PowerShell commands.
+
+## Common issues and solutions
+
+- **Issue:** PowerShell commands don't run.
+- **Root Cause:** Missing proxy certificates that are required for command execution.
+
+### Instructions to resolve configuration issues
+
+1. **Verify proxy settings:**
+   - Navigate to the **Network & Internet** settings on your system.
+   - Make sure that the proxy settings are configured correctly to allow PowerShell access.
+
+2. **Install proxy certificates:**
+   - Download the necessary proxy certificates from your network administrator.
+   - Open the **Certificates Manager** snap-in by typing `certmgr.msc` in the Windows search bar.
+   - Import the downloaded certificates into the **Trusted Root Certification Authorities** store.
+
+3. **Test PowerShell command execution:**
+   - Open PowerShell and run a test command to check whether the issue is resolved.
+   - Example command: `Get-AzActivityLog -MaxRecord 5`.
+
+4. **Check Azure CLI configuration:**
+   - Run `az upgrade` to verify that the Azure CLI is updated to the latest version.
+   - Run `az configure` to verify that the CLI is configured correctly.
+
+## References
+
+- [Azure CLI Documentation](/azure/cli/)
+- [PowerShell Documentation](/powershell/)
+- [Azure Activity Logs Overview](/azure/azure-monitor/essentials/activity-log)
+
+If the issue persists after you follow these steps, open a support case for further assistance.
diff --git a/support/azure/azure-monitor/activity-logs/config-export/understanding-and-managing-diagnostic-settings-retention.md b/support/azure/azure-monitor/activity-logs/config-export/understanding-and-managing-diagnostic-settings-retention.md
@@ -0,0 +1,45 @@
+---
+title: Understanding and Managing Diagnostic Settings Retention
+description: Provides guidance for understanding and managing diagnostic settings retention.
+ms.date: 07/22/2025
+ms.reviewer: v-liuamson; v-gsitser
+ms.service: azure-monitor
+ms.custom: I can’t configure export of Activity Logs
+---
+
+# Understanding and managing diagnostic settings retention
+
+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.
+
+## Common issues and solutions
+
+- **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.
+- **Root cause**: The automatic switch from activity log solutions to diagnostic settings might cause confusion if users don't fully understand diagnostic settings retention.
+
+### Instructions to resolve diagnostic settings issues
+
+1. Determine how resources are affected:
+   1. Navigate to the Azure portal > **All Services**.
+   1. Select **Resource Manager**.
+   1. Select **Deploy**, and then select **Templates** in the left pane.
+   1. Check whether any resources are affected by the transition.
+
+2. To determine whether legacy solutions are in use, run the following PowerShell command:
+
+     ```powershell
+     $WorkspaceName = Get-AzOperationalInsightsWorkspace
+     foreach ($Name in $WorkspaceName) {
+         Get-AzOperationalInsightsDataSource -Kind AzureActivityLog -ResourceGroupName $Name.ResourceGroupName -WorkspaceName $Name.Name
+     }
+     ```
+
+   If no output is returned, legacy solutions aren't in use, and no further action is required.
+
+3. Understand that the transition to diagnostic settings is automatic. If your environment is already using diagnostic settings, no additional steps are necessary.
+
+## References
+
+- [Azure Monitor activity logs](/azure/azure-monitor/platform/activity-log?tabs=powershell#legacy-collection-methods)
+- [Azure Storage lifecycle management](/azure/storage/blobs/storage-lifecycle-management-concepts)
+
+If the issue persists after you follow these steps, open a support case for further assistance.
diff --git a/support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md b/support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md
@@ -1,7 +1,7 @@
 ---
 title: Understanding and Transitioning from Legacy to Diagnostic Settings for Activity Logs
 description: Provides step-by-step instructions to transition from legacy to diagnostic settings.
-ms.date: 07/16/2025
+ms.date: 07/22/2025
 ms.reviewer: v-liuamson; v-gsitser
 ms.service: azure-monitor
 ms.custom: I can’t configure export of Activity Logs
@@ -11,9 +11,17 @@ ms.custom: I can’t configure export of Activity Logs
 
 When Azure announced the transition from legacy solutions to diagnostic settings for forwarding activity logs, users received notifications about necessary updates. This article provides guidance on how to manage this transition effectively.
 
-### Introduction
+## Introduction
 Azure is retiring the legacy solution for forwarding activity logs and replacing it with diagnostic settings. This change is automatic, but users with automation relying on the legacy API need to update their configurations. This guide will help you verify your current setup and make necessary adjustments.
 
+## Common Issues and Solutions
+
+- **Issue:** Unable to find existing log profiles.
+  - **Solution:** Ensure you are using the correct commands and have the necessary permissions to access log profiles.
+
+- **Issue:** Automation scripts fail after the transition.
+  - **Solution:** Double-check that all scripts are updated to use the new diagnostic settings API.
+
 ### Step-by-Step Instructions to Transition to Diagnostic Settings
 
 1. **Verify Existing Log Profiles**
@@ -22,24 +30,16 @@ Azure is retiring the legacy solution for forwarding activity logs and replacing
 
 2. **Update Automation Scripts**
    - If you have automation scripts using the legacy API, update them to use the diagnostic settings API by September 30, 2026.
-   - Refer to the [Azure Monitor documentation](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell#managing-legacy-log-profiles---retiring) for detailed instructions.
+   - Refer to the [Azure Monitor documentation](/azure/azure-monitor/platform/activity-log?tabs=powershell#managing-legacy-log-profiles---retiring) for detailed instructions.
 
 3. **Manual Transition to Diagnostic Settings**
    - For users with legacy log profiles, manually transition to diagnostic settings by following the steps outlined in the Azure documentation.
    - Ensure all configurations are updated before the retirement date to avoid disruptions.
 
-### Common Issues and Solutions
-
-- **Issue:** Unable to find existing log profiles.
-  - **Solution:** Ensure you are using the correct commands and have the necessary permissions to access log profiles.
-
-- **Issue:** Automation scripts fail after the transition.
-  - **Solution:** Double-check that all scripts are updated to use the new diagnostic settings API.
-
-### Reference
+## Reference
 
-- [Azure Monitor Documentation](https://learn.microsoft.com/azure/azure-monitor/platform/activity-log?tabs=powershell#managing-legacy-log-profiles---retiring)
-- [Get-AzLogProfile Command](https://learn.microsoft.com/powershell/module/az.monitor/get-azlogprofile?view=azps-14.0.0)
-- [Azure CLI Log Profiles](https://learn.microsoft.com/cli/azure/monitor/log-profiles?view=azure-cli-latest#az-monitor-log-profiles-list)
+- [Azure Monitor Documentation](/azure/azure-monitor/platform/activity-log?tabs=powershell#managing-legacy-log-profiles---retiring)
+- [Get-AzLogProfile Command](/powershell/module/az.monitor/get-azlogprofile?view=azps-14.0.0&preserve-view=true)
+- [Azure CLI Log Profiles](/cli/azure/monitor/log-profiles?view=azure-cli-latest#az-monitor-log-profiles-list&preserve-view=true)
 
 If the issue persists after following the solution steps, please open a support case for further assistance.
diff --git a/support/azure/azure-monitor/toc.yml b/support/azure/azure-monitor/toc.yml
@@ -17,6 +17,12 @@ items:
         href: activity-logs/config-export/exporting-directory-level-activity-logs-to-event-hub.md
       - name: Resolving Log Limit Issues in Azure Function Apps
         href: activity-logs/config-export/resolving-log-limit-issues-in-azure-function-apps.md
+      - name: Understanding and Managing Diagnostic Settings Retention
+        href: activity-logs/config-export/understanding-and-managing-diagnostic-settings-retention.md  
+      - name: Centralized Configuration of Activity Logs to Event Hub
+        href: activity-logs/config-export/centralized-configuration-of-activity-logs-to-event-hub.md
+      - name: Troubleshoot Azure CLI Configuration Issues
+        href: activity-logs/config-export/troubleshoot-azure-cli-configuration-issues.md
       - name: Troubleshoot Export of Audit Logs to Another Tenant
         href: activity-logs/config-export/troubleshoot-export-of-audit-logs-to-another-tenant.md
 - name: Application Insights
