Merge branch 'main' into v-liuamson-CI6611-update

Author: Amson Liu

.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

@@ -13830,5 +13830,10 @@
       "source_path": "support/azure/azure-monitor/activity-logs/config-export/understanding-and-transitioning-from-legacy-to-diagnostic-settings.md",
       "redirect_url": "/troubleshoot/azure/azure-monitor/activity-logs/config-export/transition-from-legacy-to-diagnostic-settings"
     }
+    ,
+    {
+      "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"
+    }
   ]
 }

SharePoint/SharePointOnline/administration/errors-when-renaming.md

@@ -5,7 +5,7 @@ author: Cloud-Writer
 ms.reviewer: PramodBalusu
 ms.author: meerak
 manager: dcscontentpm
-ms.date: 02/14/2025
+ms.date: 07/24/2025
 audience: Admin
 ms.topic: troubleshooting
 ms.custom: 
@@ -51,12 +51,13 @@ This article lists common error messages that you might receive when you change
 |-1077|There is no applicable tenant rename scheduled in your organization. |Tenant rename isn't scheduled. |Run the `Start-SPOTenantRename` cmdlet, and then try again.|
 |-1078|Prioritizing sites cannot be performed since the tenant rename is in progress. |Prioritization isn't allowed when a rename is in progress.|None. |
 |-1086| The limit on the number of prioritized sites has been reached. No further sites can be added unless some are removed first. |The 4,000-site limit for prioritization was reached.|Remove a site that was already prioritized, and then try again to prioritize the desired site. For more information, see [prioritizing sites](/sharepoint/change-your-sharepoint-domain-name#prioritizing-sites).|
-|-1081|Prioritization for root sites is not supported. |Root sites can't be prioritized.|None.| 
+|-1081|Prioritization for root sites is not supported. |Root sites can't be prioritized.|None.|
 |-1082|The site is locked. Please unlock the site and try again.|A rename can't be done on a locked site. |[Unlock the site](/sharepoint/manage-lock-status).|
 |-1080|The specified site does not exist. Please check the URL and try again.| The specified site doesn't exist. |Check whether the site exists, or whether there are any typos in the URL. |
 |-15|This site URL is invalid. Please double-check your site URL.|The specified URL has an invalid format.|Check the format of the specified URL. |
-|1095|The rename cannot be scheduled currently since alternate URLs exist in the tenant.| The tenant has alternate URLs configured for which renames aren't supported. These likely remain from earlier SharePoint on-premises implementations.| The alternate URLs must be removed before you try again to schedule a rename. Submit a support request by selecting [Rename a SharePoint Tenant with Alternate URLs](https://admin.microsoft.com/AdminPortal/?searchSolutions=Rename%20a%20SharePoint%20Tenant%20with%20Alternate%20URLs).
+|1095|The rename cannot be scheduled currently since alternate URLs exist in the tenant.| The tenant has alternate URLs configured for which renames aren't supported. These likely remain from earlier SharePoint on-premises implementations.| The alternate URLs must be removed before you try again to schedule a rename. Submit a support request by selecting [Rename a SharePoint Tenant with Alternate URLs](https://admin.microsoft.com/AdminPortal/?searchSolutions=Rename%20a%20SharePoint%20Tenant%20with%20Alternate%20URLs).|
 |1089|Max no. of allowed sites exceeded.|During a tenant rename, the maximum number of sites allowed by the standard rename has been exceeded.|For larger organizations, use [Advanced Tenant Rename](https://aka.ms/AdvancedTenantRename).|
+|1104|Renames to older domains are not supported. Please try again with a different domain.| Renaming to a domain that has been used previously is not supported.|Use a new domain name.|
 
 **Note:** You might encounter different errors about individual site renaming if the actions fail as part of the domain renaming. For more information, see [Errors when you rename a SharePoint site address](https://support.microsoft.com/office/errors-when-you-rename-a-sharepoint-site-address-165b7c11-1325-4813-b160-ecbe87bc1a86).
 

support/azure/azure-kubernetes/connectivity/basic-troubleshooting-outbound-connections.md

@@ -150,7 +150,7 @@ To determine if traffic is blocked to the endpoint due to Azure network resource
 
 1. Navigate to your cluster in the Azure portal. In the sidebar, navigate to the Settings -> Node pools blade.
 2. Identify the nodepool you want to run a connectivity analysis from. Click on the nodepool to select it as the scope.
-3. Select "Connectivity analysis (Preview)" from the toolbar at the top of the page. If you don't see it, click on the three dots "..." in the toolbar at the top of the page to open the expanded menu. <img width="626" alt="image" src="https://github.com/user-attachments/assets/b2f05947-f753-49b9-9536-98d0b998ab52" />
+3. Select "Connectivity analysis (Preview)" from the toolbar at the top of the page. If you don't see it, click on the three dots "..." in the toolbar at the top of the page to open the expanded menu.
 4. Select a Virtual Machine Scale Set (VMSS) instance as the source. The source IP addresses are populated automatically.
 5. Select a public domain name/endpoint as the destination for the analysis, one example is `mcr.microsoft.com`. The destination IP addresses are also populated automatically.
 6. Run the analysis and wait up to 2 minutes for the results. In the resulting diagram, identify the associated Azure network resources and where traffic is blocked. To view the detailed analysis output, click on the "JSON output" tab or click into the arrows in the diagram.

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