Merging changes synced from https://github.com/MicrosoftDocs/SupportArticles-docs-pr (branch live)

Author: Learn Build Service GitHub App

.openpublishing.redirection.json

@@ -13175,6 +13175,26 @@
     {
       "source_path": "support/windows-server/setup-upgrade-and-drivers/repair-or-in-place-upgrade.md",
       "redirect_url": "/windows-server/get-started/perform-in-place-upgrade"
+    },
+    {
+      "source_path": "support/windows-client/user-profiles-and-logon/roaming-profile-was-not-completely-synchronized-error.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-client/roaming-profile-was-not-completely-synchronized-error"
+    },
+    {
+      "source_path": "support/windows-client/user-profiles-and-logon/renaming-user-account-not-change-profile-path.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-client/renaming-user-account-not-change-profile-path"
+    },
+    {
+      "source_path": "support/windows-client/user-profiles-and-logon/event-id-300-windows-hello-successfully-created-in-windows-10.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-client/event-id-300-windows-hello-successfully-created-in-windows-10"
+    },
+    {
+      "source_path": "support/windows-server/active-directory/convert-domain-federated.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-server/convert-domain-federated"
+    },
+    {
+      "source_path": "support/windows-server/active-directory/connection-adfs-failed-set-msoladfscontex.md",
+      "redirect_url": "/previous-versions/troubleshoot/windows-server/connection-adfs-failed-set-msoladfscontex"
     }
   ]
 }

support/azure/azure-kubernetes/create-upgrade-delete/error-code-subnetisfull.md

@@ -1,11 +1,11 @@
 ---
 title: Troubleshoot the SubnetIsFull error code
 description: Learn how to troubleshoot the SubnetIsFull error when you try to scale an Azure Kubernetes Service (AKS) cluster.
-ms.date: 11/20/2023
+ms.date: 02/28/2025
 author: jotavar
 ms.author: jotavar
 editor: v-jsitser
-ms.reviewer: rissing, chiragpa, v-leedennis
+ms.reviewer: rissing, chiragpa, addobres
 ms.service: azure-kubernetes-service
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the SubnetIsFull error code so that I can successfully scale an Azure Kubernetes Service (AKS) cluster.
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
@@ -45,6 +45,17 @@ Trying to update a subnet's Classless Inter-Domain Routing (CIDR) address space
 
 4. Delete the original node pool by running the [az aks nodepool delete](/cli/azure/aks/nodepool#az-aks-nodepool-delete) command.
 
+
+## Best practices
+
+To avoid `SubnetIsFull` issues in Azure Kubernetes Service (AKS), follow best practices that are related to subnet sizing, IP address management, and node pool strategies. Here are some key recommendations: 
+
+- Plan for Future Growth: When you create subnets, make sure that they're large enough to accommodate future growth. We recommend that you reserve more IP addresses than you currently need to avoid running out of space as the cluster scales. 
+- Use Larger Subnet CIDR: If possible, use a larger subnet CIDR to provide more IP addresses. This strategy helps to accommodate more nodes and pods without running into IP exhaustion issues.
+- Monitor IP Usage: To identify potential issues before they become critical, regularly monitor the IP address usage within your subnets. Tools such as Azure Monitor can help track IP address consumption.
+- Optimize IP Allocation: Make sure that IP addresses are allocated efficiently. Avoid reserving IP addresses unnecessarily. To free up space, release any unused IP addresses.
+- Use multiple node pools: Consider using node pools that have different subnets to distribute the IP address load. This strategy can help mitigate the risk of running out of IP addresses in a single subnet.   
+
 ## More information
 
 - [General troubleshooting of AKS cluster creation issues](troubleshoot-aks-cluster-creation-issues.md)

support/azure/azure-kubernetes/error-codes/unsatisfiablepdb-error.md

@@ -1,8 +1,8 @@
 ---
 title: AKS cluster upgrade fails with UnsatisfiablePDB error
 description: Provides solutions to the UnsatisfiablePDB error when you try to upgrade an Azure Kubernetes Service (AKS) cluster.
-ms.date: 10/27/2023
-ms.reviewer: chiragpa, v-weizhu
+ms.date: 03/05/2025
+ms.reviewer: chiragpa, v-weizhu, addobres
 ms.service: azure-kubernetes-service
 ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
 #Customer intent: As an Azure Kubernetes Services (AKS) user, I want to troubleshoot an Azure Kubernetes Service cluster upgrade that failed because of a UnsatisfiablePDB error so that I can upgrade the cluster successfully.

support/developer/webapps/aspnet/development/disable-debugging-application.md

@@ -1,13 +1,14 @@
 ---
-title: Disable debugging for ASP.NET application
+title: Disable Debugging for ASP.NET Application
 description: This article discusses how to disable debugging for ASP.NET applications.
-ms.date: 03/27/2020
+ms.date: 03/26/2025
 ms.custom: sap:General Development
 ms.topic: how-to
+ms.reviewer: paulboc
 ---
 # Disable debugging for ASP.NET applications
 
-This article discusses how to disable debugging for ASP.NET applications.
+This article discusses how to disable debugging for ASP.NET applications running on .NET Framework.
 
 _Original product version:_   ASP.NET  
 _Original KB number:_   815157
@@ -18,38 +19,68 @@ ASP.NET supports compiling applications in a special debug mode that helps devel
 
 Debugging is disabled by default. Debugging is frequently enabled to troubleshoot a problem. But it's frequently not disabled after the problem is resolved. This article describes how to disable debugging for an ASP.NET application.
 
-To disable debugging, modify the *Web.config* file or the *Machine.config* file, as detailed in the following sections.
+To disable debugging, modify the **Web.config** file or the **Machine.config** file, as detailed in the following sections.
 
 ## Method 1: Modify the Web.config file
 
-To disable debugging, add the compilation element to the *Web.config* file of the application by following these steps. The *Web.config* file is located in the application directory.
+To disable debugging, add the compilation element to the **Web.config** file of the application by following these steps. The **Web.config** file is located in the application directory.
 
-1. Open the *Web.config* file in a text editor, such as Notepad. The file is typically located in the application directory.
-2. In the *Web.config* file, locate the compilation element. Debugging is enabled when the debug attribute in the compilation element is set to **true**.
-3. Change the debug attribute to **false** to disable debugging for that application.
+1. Open the **Web.config** file in a text editor, such as Notepad. The file is typically located in the application directory.
+2. In the **Web.config** file, locate the compilation element. Debugging is enabled when the debug attribute in the compilation element is set to `true`.
+3. Change the debug attribute to `false` to disable debugging for that application.
 
-    The following code sample shows the compilation element with debug set to **false**:
+    The following code sample shows the compilation element with debug set to `false`:
 
     ```xml
     <compilation debug="false"/>
     ```
 
-4. Save the *Web.config* file. The ASP.NET application automatically restarts.
+4. Save the **Web.config** file. The ASP.NET application automatically restarts.
 
 ## Method 2: Modify the Machine.config file
 
-You can also disable debugging for all applications on a system by modifying the *Machine.config* file. To confirm debugging hasn't been enabled in the *Machine.config* file, follow these steps:
+You can also disable debugging for all applications on a system by modifying the **Machine.config** file. To confirm that debugging isn't enabled in the **Machine.config** file, follow these steps:
 
-1. Open the *Machine.config* file in a text editor, such as Notepad. The file is typically located in the following folder:  
+1. Open the **Machine.config** file in a text editor, such as Notepad. The file is typically located in the following folder:  
 
-    `%SystemRoot%\Microsoft.NET\Framework\%VersionNumber%\CONFIG\`
-2. In the *Machine.config* file, locate the compilation element. Debugging is enabled when the debug attribute in the compilation element is set to **true**.
-3. If the debug attribute is **true**, change the debug attribute to **false**.
+   `%SystemRoot%\Microsoft.NET\Framework\%VersionNumber%\CONFIG\`
 
-    The following code sample shows the compilation element with debug set to **false**:
+   For 64-bit versions of the .NET Framework, the file is in the following folder:
 
-    ```xml
-    <compilation debug="false"/>
-    ```
+   `%SystemRoot%\Microsoft.NET\Framework64\%VersionNumber%\CONFIG\`
+
+1. In the **Machine.config** file, locate the compilation element. Debugging is enabled when the debug attribute in the compilation element is set to `true`.
+1. If the debug attribute is `true`, change the debug attribute to `false`.
+
+   The following code sample shows the compilation element with debug set to `false`:
+
+   ```xml
+   <compilation debug="false"/>
+   ```
+
+1. Save the **Machine.config** file.
+
+## Method 3: Using IIS Manager (if the web application is hosted on IIS)
+
+1. Open IIS Manager on the computer where the website is hosted (you can select <kbd>Windows</kbd> + <kbd>R</kbd> and type **inetmgr**):
+
+   :::image type="content" source="media/disable-debugging-application/type-inetmgr-run-window.png" alt-text="Screenshot of typing inetmgr in the Run window.":::
+
+1. Select the website or web application for which you want to enable or disable debug mode from the left-hand side tree view:
+
+   :::image type="content" source="media/disable-debugging-application/enable-disable-debug-mode-web-application.png" alt-text="Screenshot of website or web application for which you want to enable or disable debug mode." lightbox="media/disable-debugging-application/enable-disable-debug-mode-web-application.png":::
+
+1. From the middle pane of IIS Manager, select the **.NET Compilation** icon:
+
+   :::image type="content" source="media/disable-debugging-application/net-compilation-icon.png" alt-text="Screenshot of the .NET Compilation icon." lightbox="media/disable-debugging-application/net-compilation-icon.png":::
+
+1. Within the list of parameter values displayed in the middle pane of IIS Manager, set the value of **Debug** under the **Behavior** category to:
+
+   - **True**: Enable debug mode.
+   - **False**: Disable debug mode.
+
+   :::image type="content" source="media/disable-debugging-application/set-value-debug-under-behavior-category.png" alt-text="Screenshot of setting the value of Debug under the Behavior category." lightbox="media/disable-debugging-application/set-value-debug-under-behavior-category.png":::
+
+1. Select the **Apply** button from the right-hand side pane of IIS Manager to save the changes to the IIS configuration:
 
-4. Save the *Machine.config* file.
+   :::image type="content" source="media/disable-debugging-application/apply-button-iis-manager.png" alt-text="Screenshot of the Apply button in IIS Manager." lightbox="media/disable-debugging-application/apply-button-iis-manager.png":::

support/developer/webapps/aspnet/development/media/disable-debugging-application/apply-button-iis-manager.png

@@ -456,7 +456,7 @@ F12 Developer Tools are built into both Microsoft Edge and Chrome. In instances
 
 ### Failed Request Trace (FREB) logs
 
-FREB traces are `.xml` files, and formatted by the `.xsl` stylesheet in the FREB log directory. Use a tool like FrebSbS to view these logs. For more information on how to read a FREB log, see [Reading a FREB log, a Failed Request Tracing: IIS request processing pipeline execution](https://techcommunity.microsoft.com/blog/iis-support-blog/reading-a-freb-log-a-failed-request-tracing-iis-request-processing-pipeline-exec/1349639).
+FREB traces are `.xml` files, and formatted by the `.xsl` stylesheet in the FREB log directory. For more information on how to read a FREB log, see [Reading a FREB log, a Failed Request Tracing: IIS request processing pipeline execution](https://techcommunity.microsoft.com/blog/iis-support-blog/reading-a-freb-log-a-failed-request-tracing-iis-request-processing-pipeline-exec/1349639).
 
 ### Full memory dumps
 
@@ -481,4 +481,3 @@ It's simpler and more understandable to run only one type of analysis rule at a
 > [!NOTE]
 > If a more detailed analysis is needed, use [WinDbg](/windows-hardware/drivers/debuggercmds/windbg-overview) to review dumps.
 
-[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]