Merge branch 'main' into v-sisidhuCI-6690

Author: Simrran1502

.openpublishing.redirection.developer.json

@@ -6718,6 +6718,102 @@
     {
       "source_path": "support/developer/dotnet/framework/installation/patching-framework-fails.md",
       "redirect_url": "/previous-versions/troubleshoot/dotnet/framework/patching-framework-fails"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/service-throws-exception.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/service-throws-exception"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/asynchronous-service-use-wrong-impersonation.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/asynchronous-service-use-wrong-impersonation"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/call-timed-out-aspnet-mvc-controller.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/call-timed-out-aspnet-mvc-controller"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/cannot-validate-run-workflow.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/cannot-validate-run-workflow"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/wcf-extensions-concurrent-request-run-sequentially.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/wcf-extensions-concurrent-request-run-sequentially"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/disconnects-http-bindings.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/disconnects-http-bindings"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/endpoint-address-use-the-discovery-client-channel.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/endpoint-address-use-the-discovery-client-channel"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/error-create-performance-counters.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/error-create-performance-counters"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/error-occurs-remove-an-appfabric-cluster-server.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/error-occurs-remove-an-appfabric-cluster-server"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/error-disable-non-http-activation.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/error-disable-non-http-activation"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/error-service-use-activation.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/error-service-use-activation"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/error-discovery-udp.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/error-discovery-udp"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/fail-install-wif.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/fail-install-wif"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/kerberos-not-used-call-service.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/kerberos-not-used-call-service"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/precompiled-workflow-activation-fails.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/precompiled-workflow-activation-fails"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/rest-generate-metadata-wsdl.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/rest-generate-metadata-wsdl"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/service-does-not-start-automatically.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/service-does-not-start-automatically"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/service-scale-up-slowly.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/service-scale-up-slowly"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/service-operations-use-wrong-impersonation-context.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/service-operations-use-wrong-impersonation-context"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/service-use-a-non-default-etw-provider-id.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/service-use-a-non-default-etw-provider-id"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/socketexception-connection-pooling.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/socketexception-connection-pooling"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/x509certificatevalidator-service-certificate.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/x509certificatevalidator-service-certificate"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/wcf-net-tcp-service-stop-response.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/wcf-net-tcp-service-stop-response"
+    },
+    {
+      "source_path": "support/developer/dotnet/wcf/workflow-service-cannot-receive-messages-in-order.md",
+      "redirect_url": "/previous-versions/troubleshoot/dotnet/wcf/workflow-service-cannot-receive-messages-in-order"
     }
   ]
 }

.openpublishing.redirection.json

@@ -13800,6 +13800,10 @@
       "source_path": "support/sql/tools/error-you-run-sqlmaint-utility.md",
       "redirect_url": "/previous-versions/troubleshoot/sql/tools/error-you-run-sqlmaint-utility",
       "redirect_document_id": false
+    },
+    {
+      "source_path": "support/sql/database-engine/install/windows/error-install-sql-server-2008-r2.md",
+      "redirect_url": "/troubleshoot/sql/database-engine/install/windows/error-install-sql-server"
     }
   ]
 }

support/azure/azure-storage/files/file-sync/file-sync-troubleshoot-managed-identities.md

@@ -3,7 +3,7 @@ title: Troubleshoot Azure File Sync managed identity issues
 description: Troubleshoot common issues when your Azure File Sync deployment is configured to use managed identities.
 ms.service: azure-file-storage
 ms.topic: troubleshooting
-ms.date: 07/22/2025
+ms.date: 07/31/2025
 author: khdownie
 ms.author: kendownie
 ---
@@ -101,7 +101,7 @@ Cloud endpoint:
 - Storage Sync Service managed identity must be a member of the **Storage File Data Privileged Contributor** role on an Azure file share.
 
 Server endpoint:
-- Register server managed identity must be a member of the **Storage File Data Privileged Contributor** role on an Azure file share.
+- Registered server managed identity must be a member of the **Storage File Data Privileged Contributor** role on an Azure file share.
 
 When you run the `Set-AzStorageSyncServiceIdentity` cmdlet or create new cloud and server endpoints, these permissions are granted. If these permissions are removed, operations fail with the errors listed in the following section.
 
@@ -169,7 +169,6 @@ Set-AzStorageSyncServerEndpointPermission -ResourceGroupName <string> -StorageSy
 > [!NOTE]
 > The `-Name` parameter is the name of the server endpoint. It's a GUID, not the friendly name that's displayed in the Azure portal. To get the server endpoint name, run the [Get-AzStorageSyncServerEndpoint](/powershell/module/az.storagesync/get-azstoragesyncserverendpoint) cmdlet.
 
-
 ### Sync Session fails with the ECS_E_AUTH_IDENTITY_NOT_FOUND error
 
 The `ECS_E_AUTH_IDENTITY_NOT_FOUND` error occurs when the server's managed identity used to communicate with the Azure File Sync service has changed, but the Azure File Sync service is still expecting the previous one, causing authentication to fail.
@@ -181,24 +180,24 @@ This issue often occurs in the following situations:
 - Azure Arc resource deletion and recreation.
 - Turning off and then re-enabling the system-assigned managed identity on an Azure virtual machine.
 
-When the managed identity changes, the File Sync agent tries to use the new identity, but the Azure File Sync service is still configured to authorize the previous one. This mismatch causes requests to fail with the `ECS_E_AUTH_IDENTITY_NOT_FOUND` error.
+When the managed identity changes, the File Sync agent tries to use the new identity, but the Azure File Sync service is still configured to authorize the previous one. This mismatch causes requests to fail and return the `ECS_E_AUTH_IDENTITY_NOT_FOUND` error.
 
 To resolve this issue: 
 
-First, ensure the server is configured to use a managed identity. 
+Make sure that the server is configured to use a managed identity. 
 
-You can verify this by:
-- Checking the **Settings** > **Managed identities** details in your storage sync service, or
-- Running the following PowerShell command:
+To verify this configuration:
+- Check the **Settings** > **Managed identities** details in your storage sync service, or
+- Run the following PowerShell command:
 
 ```powershell
 Get-AzStorageSyncServer -ResourceGroupName <ResourceGroupName> -StorageSyncServiceName <StorageSyncServiceName>
 ```
-> [!NOTE]
-> This error can occur whether the server is using managed identity (MI) or certificate-based authentication, so confirming the identity type is important.
 
+> [!NOTE]
+> This error can occur whether the server is using managed identity (MI) or certificate-based authentication. Therefore, it's important to verify the identity type.
 
-If the server is using managed identity and the identity has changed, run the following command to update the server registration:
+If the server uses managed identity and the identity was changed, run the following command to update the server registration:
 
 ```powershell
 Set-AzStorageSyncServer -ResourceGroupName <ResourceGroupName> -StorageSyncServiceName <StorageSyncServiceName> -Identity

support/azure/virtual-machines/linux/custom-dns-configuration-for-azure-linux-vms.md

@@ -27,7 +27,7 @@ This article provides instructions to configure custom DNS servers and search do
 2. Configure custom DNS servers at the Azure virtual network or network interface level. For more information, see [Steps to change DNS servers at virtual network/network interface level](/azure/virtual-network/manage-virtual-network#change-dns-servers).
 
     > [!NOTE]
-    > In Azure, you can set custom DNS servers at the virtual network level or the network interface level. If you set custom DNS servers at the network interface level, it will override the the custom DNS servers configuration in the virtual network.
+    > In Azure, you can set custom DNS servers at the virtual network level or the network interface level. If you set custom DNS servers at the network interface level, it will override the custom DNS servers configuration in the virtual network.
 
 3. Restart the `NetworkManager` service, and then check the `/etc/resolv.conf` file. The file should contain the DNS servers that you configured in the step 2.
 
@@ -79,38 +79,45 @@ This article provides instructions to configure custom DNS servers and search do
 
     :::image type="content" source="./media/custom-dns-config-images/rhel-dns-6.png" alt-text="Screenshot showing the search domain.":::
 
-## [Ubuntu 20.04/22.04](#tab/Ubuntu)
+## [RHEL 10](#tab/RHEL10)
+
+Guidance for configuring custom DNS on **RHEL 10** is currently being developed in collaboration with Red Hat. This section will be updated once validated instructions are available. Please check back for the latest information.
+
+## [Ubuntu 20.04/22.04/24.04](#tab/Ubuntu)
 
 ### Configure DNS servers
 
 1. The initial configuration of the `/etc/resolv.conf` file in an Azure Ubuntu VM is as shown in the following screenshot.
 
-   :::image type="content" source="./media/custom-dns-config-images/ubuntu-dns-1.png" alt-text="Screenshot of default resolv.conf file in Ubuntu.":::
+    :::image type="content" source="./media/custom-dns-config-images/ubuntu-dns-1.png" alt-text="Screenshot of default resolv.conf file in Ubuntu.":::
 
-2. Configure custom DNS servers at the Azure virtual network or network interface level. For more information, see [Steps to change DNS servers at virtual network/network interface level](/azure/virtual-network/manage-virtual-network#change-dns-servers).
+2. Starting with Ubuntu 20.04, `resolv.conf` file is a symbolic link to `/run/systemd/resolve/stub-resolv.conf`. For more information about this stub file, significance and usage of different `resolv.conf` files, and `systemd-resolved` service, see [systemd-resolved](https://manpages.ubuntu.com/manpages/bionic/man8/systemd-resolved.service.8.html#:~:text=systemd%2Dresolved%20is%20a%20system,an%20LLMNR%20resolver%20and%20responder)
+   
+    :::image type="content" source="./media/custom-dns-config-images/ubuntu-dns-2.png" alt-text="Screenshot of resolv.conf file linked to stub-resolv.conf file":::
+
+3. Configure custom DNS servers at either the Azure virtual network or network interface level. For more information, see [Steps to change DNS servers at virtual network/network interface level](/azure/virtual-network/manage-virtual-network#change-dns-servers).
 
     > [!NOTE]
-    > In Azure, you can set custom DNS servers at the virtual network level or the network interface level. If you set custom DNS servers at the network interface level, this will override the the custom DNS servers configuration in the virtual network.
-3. Run the following command to apply the configuration of the custom DNS servers:
+    > In Azure, you can set custom DNS servers at the virtual network level or the network interface level. If you set custom DNS servers at the network interface level, this will override the custom DNS servers configuration in the virtual network.
+
+4. Run the following command to apply the custom DNS configuration:
 
    ```bash
    sudo netplan apply
-
-4. Check the `/run/systemd/resolve/stub-resolv.conf` file. The file should contain the DNS servers that you configured in step 2.
-  
-    Starting is Ubuntu 20, `resolv.conf` file is a symbolic link of `/run/systemd/resolve/stub-resolv.conf` file. This makes sure that the updated DNS servers are reflected in **/run/systemd/resolve/resolv.conf** file. For more information, see [systemd-resolved](https://manpages.ubuntu.com/manpages/bionic/man8/systemd-resolved.service.8.html#:~:text=systemd%2Dresolved%20is%20a%20system,an%20LLMNR%20resolver%20and%20responder).
+   ```
+5. Verify the contents of `/run/systemd/resolve/resolv.conf` file. It should list the DNS servers configured in step 3.
 
-   The following screenshot shows an example of `/run/systemd/resolve/stub-resolv.conf` after you configure custom DNS server.
+   The following screenshot shows an example of `/run/systemd/resolve/resolv.conf` after configuring custom DNS servers.
 
    :::image type="content" source="./media/custom-dns-config-images/ubuntu-dns-3.png" alt-text="Screenshot of non-stub Resolv.conf file after you make changes at portal level":::
 
-5. Run the following command to check whether the custom DNS servers are successfully added to the network interface:
+6. Since `/etc/resolv.conf` is still linked to stub file, unlink and create a new link to `/run/systemd/resolve/resolv.conf`, so that DNS queries the updated custom DNS servers.
 
    ```bash
-   sudo resolvectl status
-   ```
-
-   The following screenshot shows an example of the network interface after you configure the search domain:
+    unlink /etc/resolv.conf
+    ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
+    ```
+   The following screenshot shows an example output of the `resolvecl status` command:
 
    :::image type="content" source="./media/custom-dns-config-images/ubuntu-dns-4.png" alt-text="Screenshot of resolvectl status command output.":::