Merge pull request #8704 from MicrosoftDocs/main

Auto push to live 2025-04-14 02:00:02

Author: Deland-Han

support/azure/azure-kubernetes/availability-performance/node-not-ready-expired-certificates.md

@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot Node Not Ready state when certificates have expired
 description: Troubleshoot scenarios in which Node Not Ready failures occur in an Azure Kubernetes Service (AKS) cluster node if there are expired certificates.
-ms.date: 10/28/2024
-ms.reviewer: rissing, chiragpa, momajed, v-leedennis
+ms.date: 04/10/2025
+ms.reviewer: rissing, chiragpa, momajed, v-leedennis, addobres, v-weizhu
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to fix expired certificates so that they don't cause Node Not Ready failures within an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Node/node pool availability and performance

support/azure/azure-kubernetes/create-upgrade-delete/windows-cse-error-check-api-server-connectivity.md

@@ -1,8 +1,8 @@
 ---
 title: Troubleshoot WINDOWS_CSE_ERROR_CHECK_API_SERVER_CONNECTIVITY error (5)
 description: Learn how to troubleshoot the WINDOWS_CSE_ERROR_CHECK_API_SERVER_CONNECTIVITY error (5) when you try to add Windows node pools in an AKS cluster.
-ms.date: 10/31/2023
-ms.reviewer: shtao, abelch, junjiezhang, v-weizhu
+ms.date: 04/14/2025
+ms.reviewer: shtao, abelch, junjiezhang, v-weizhu, addobres
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the WINDOWS_CSE_ERROR_CHECK_API_SERVER_CONNECTIVITY error (5) so that I can successfully add Windows node pools in an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -31,7 +31,9 @@ Your cluster nodes can't connect to the cluster API server pod.
 
 ## Troubleshooting steps
 
-1. Verify that your nodes can resolve the cluster's fully qualified domain name (FQDN):
+1. Connect to the respective node by following the steps described in [Windows Server proxy connection for SSH](/azure/aks/node-access#windows-server-proxy-connection-for-ssh):
+
+2. Verify that your nodes can resolve the cluster's fully qualified domain name (FQDN):
 
     On existing Windows nodes, run the following command:
 
@@ -45,15 +47,17 @@ Your cluster nodes can't connect to the cluster API server pod.
     nc -vz <cluster-fqdn> 443
     ```
 
-2. If the command output shows `False` or `Timeout`, check your network configuration. For example, check whether you set "Deny" rules for the API server in network security groups (NSGs) of the virtual network.
+3. If the command output shows `False` or `Timeout`, check your network configuration. For example, check whether you set "Deny" rules for the API server in network security groups (NSGs) of the virtual network.
 
-3. If you're using egress filtering through a firewall, make sure that traffic is allowed to your cluster FQDN.
+4. If you're using egress filtering through a firewall, make sure that traffic is allowed to your cluster FQDN.
 
-4. If you've authorized IP addresses that are enabled on your cluster, the firewall's outbound IP address can be blocked. In this scenario, you must add the outbound IP address of the firewall to the list of authorized IP ranges for the cluster. For more information, see [Secure access to the API server using authorized IP address ranges in AKS](/azure/aks/api-server-authorized-ip-ranges).
+5. If you've authorized IP addresses that are enabled on your cluster, the firewall's outbound IP address can be blocked. In this scenario, you must add the outbound IP address of the firewall to the list of authorized IP ranges for the cluster. For more information, see [Secure access to the API server using authorized IP address ranges in AKS](/azure/aks/api-server-authorized-ip-ranges).
 
 ## References
 
-[General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+- [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)
+
+- [Exit codes in Windows CSE](https://github.com/Azure/AgentBaker/blob/master/parts/windows/windowscsehelper.ps1)
 
 [!INCLUDE [Third-party disclaimer](../../../includes/third-party-disclaimer.md)]
 

support/entra/entra-id/app-integration/media/use-netlog-capture-network-traffic/import-netlog-json.png

@@ -0,0 +1,69 @@
+---
+title: Use NetLog to Capture Network Activity
+description: Provides guidance about using the Network Logs (NetLog) tool as an alternative to Fiddler and HTTP Archive (HAR) captures.
+ms.reviewer: bachoang, v-weizhu
+ms.date: 04/14/2025
+ms.service: entra-id
+ms.topic: how-to
+ms.custom: sap:Enterprise Applications
+---
+# Use NetLog as an alternative to Fiddler and HAR captures
+
+This article provides guidance on using the Network Logs (NetLog) tool as an alternative to Fiddler and HTTP Archive (HAR) captures to diagnose network issues in Microsoft Entra. NetLog is built into Chromium-based browsers like Microsoft Edge, Google Chrome, and Electron. When standard Fiddler captures are unavailable or HAR captures from developer tools truncate necessary information, you can use NetLog to capture network activity.
+
+## Known limitations
+
+Before using NetLog, be aware of the following limitations:
+
+- POST request bodies aren't captured.
+- Sites running in Internet Explorer compatibility mode aren't captured.
+
+Depending on the information you need, you might still need to use Fiddler or HAR captures.
+
+## Use NetLog in browsers
+
+Follow these steps to capture network activity using NetLog:
+
+1. (Optional but helpful) Close all browser tabs except one.
+1. Navigate to NetLog:
+    - For Google Chrome: Open a new tab and go to `chrome://net-export`.
+    - For Microsoft Edge: Open a new tab and go to `edge://net-export`.
+1. In the **Options** section, select **Include raw bytes (will include cookies and credentials)**.
+1. Leave the **Maximum log size** field blank.
+1. Select **Start Logging to Disk**.
+1. Select a location (such as **Desktop**) to save the log file (**edge-net-export-log.json** or **chrome-net-export-log.json**).
+1. In the same browser window, open a new tab.
+1. Reproduce the issue.
+
+    > [!NOTE]
+    > If you close or navigate away from the NetLog tab, the logging will stop automatically.
+1. After reproducing the issue, return to the NetLog tab and select the **Stop Logging** button.
+1. Locate the NetLog file saved in step 6.
+
+For more information, see [How to capture a NetLog dump](https://dev.chromium.org/for-testers/providing-network-details).
+
+## Use NetLog on mobile devices
+
+NetLog is supported on mobile versions of Microsoft Edge and Google Chrome:
+
+- Android: NetLog works in Edge and Google Chrome for Android.
+- iOS: NetLog works in Google Chrome for iOS.
+
+On mobile devices, you have an email option to send the log.
+
+## View and analyze NetLog data
+
+You can view the NetLog file using the [online NetLog Viewer](https://netlog-viewer.appspot.com/#import). To do so, open the NetLog Viewer, select **File**, and then upload the exported NetLog file.
+
+You can use the following tabs in the NetLog Viewer to inspect different aspects of network activity:
+
+- **Events**: View detailed network events.
+- **Proxy**: Check proxy settings.
+- **Timeline**: Analyze request timing.
+- **DNS**: Inspect Domain Name System (DNS) lookups.
+- **Sockets**: Review Transmission Control Protocol (TCP) connections.
+- **Cache**: Examine cached resources.
+
+[!INCLUDE [Third-party information disclaimer](../../../includes/third-party-disclaimer.md)]
+
+[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

support/entra/entra-id/app-integration/use-netlog-capture-network-traffic.md

@@ -136,6 +136,8 @@
         href: app-integration/application-delegated-permission-access-tokens-identity-platform.md
       - name: Troubleshoot consent issues
         href: app-integration/troubleshoot-consent-issues.md
+- name: Use NetLog as an alternative to Fiddler and HAR captures
+  href: app-integration/use-netlog-capture-network-traffic.md
 - name: Business To Consumer (B2C) Tenants
   items:
   - name: Problem with app or API integration

support/entra/entra-id/toc.yml

@@ -1,7 +1,7 @@
 ---
 title: Known issues with Microsoft Intune
 description: Learn about known issues with Microsoft Intune, including workarounds and updated fixes.
-ms.date: 02/11/2025
+ms.date: 04/14/2025
 search.appverid: MET150
 ms.reviewer: kaushika, madakeva, annovich, jerryabo
 ms.custom: sap:Set Up Intune\Set up administrators and manage roles
@@ -10,6 +10,12 @@ ms.custom: sap:Set Up Intune\Set up administrators and manage roles
 
 This page lists recent known issues with Microsoft Intune. For a list of weekly feature announcements, see [What's new in Microsoft Intune](/mem/intune/fundamentals/whats-new) in the Intune product documentation. Visit the [Intune Customer Success blog](https://techcommunity.microsoft.com/t5/intune-customer-success/bg-p/IntuneCustomerSuccess) for posts about best practices, support tips, and other tutorials, and a backlog of past known issues.
 
+## Apps deployed with Configuration Manager take a long time to load on the Windows apps page in Company Portal
+
+- **Status:** Active
+
+There's a known issue in Company Portal where Windows apps deployed with Configuration Manager might take multiple seconds (up to a few minutes) to load on the Windows apps page. Microsoft is investigating this issue and will update this article when more information becomes available.
+
 ## Azure enterprise applications aren't displayed in the Company Portal for Windows or the Intune Company Portal website
 
 - **Status:** Active