Merge pull request #8711 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/SupportArticles-docs (branch main)

Author: simonxjx

support/azure/azure-container-instances/configuration-setup/error-codes-spot-container-creation.md

@@ -1,11 +1,11 @@
 ---
 title: Error codes for Spot container creation in Container Instances
 description: Provides a solution to common Spot container errors.
-ms.date: 01/30/2024
+ms.date: 04/14/2025
 author: tysonfms
 ms.author: tysonfreeman
 editor: v-jsitser
-ms.reviewer: v-weizhu, v-leedennis
+ms.reviewer: edneto, v-weizhu, v-leedennis
 ms.service: azure-container-instances
 ms.custom: sap:Configuration and Setup
 #customer intent: As a user of Azure Container Instances, I want find details and solutions to common user errors that involve Spot containers so that I can create Spot containers successfully.

support/azure/azure-container-instances/configuration-setup/long-image-pulls.md

@@ -1,12 +1,12 @@
 ---
 title: Image pull takes a long time to run
 description: Learn about troubleshooting steps that you can take if an image pull takes a long time to run on Azure Container Instances.
-ms.date: 12/28/2023
+ms.date: 04/14/2025
 ms.service: azure-container-instances
 author: tysonfms
 ms.author: tysonfreeman
 editor: v-jsitser
-ms.reviewer: v-leedennis
+ms.reviewer: edneto, v-leedennis
 ms.custom: sap:Configuration and Setup
 #Customer intent: As a user of Azure Container Instances, I want to learn why an image pull takes a long time to run so that I can create and use container groups successfully.
 ---

support/azure/azure-kubernetes/connectivity/cannot-view-resources-kubernetes-resource-viewer-portal.md

@@ -1,8 +1,8 @@
 ---
 title: Can't view resources in Kubernetes resource viewer on Azure portal
 description: Troubleshoot why you can't view resources in the Kubernetes resource viewer in the Azure portal for a cluster configured with API server-authorized IP ranges.
-ms.date: 11/12/2024
-ms.reviewer: chiragpa, nickoman, jaewonpark, v-leedennis
+ms.date: 04/14/2025
+ms.reviewer: edneto, chiragpa, nickoman, jaewonpark, v-leedennis
 ms.service: azure-kubernetes-service
 keywords:
 #Customer intent: As an Azure Kubernetes user, I want to troubleshoot the inability to view resources in the Kubernetes resource viewer in the Azure portal so that I can use authorized IP address ranges to access my AKS cluster that's configured with an API server.

support/azure/azure-storage/blobs/connectivity/copy-blobs-between-storage-accounts-network-restriction.md

@@ -67,20 +67,22 @@ Here's the full process of this mechanism for the two scenarios:
 4. The client sends PutBlockList to the destination storage to commit the blocks and finish the process after receiving a success response code from the request.
 
 ## Copy blobs between storage accounts in a Hub-spoke architecture using private endpoints
-A 403 Error occurs when using AzCopy to copy blobs between Storage accounts connected to private endpoints in different Spoke VNets from a VM in a Hub VNet. You can find a "403 This request is not authorized to perform this operation - CannotVerfiyCopySource" error in the AzCopy logs or in the Azure Storage logs. The following architecture diagram shows the scenario in which the error occurs.
+A 403 Error occurs when using AzCopy to copy blobs between Storage accounts connected to private endpoints in different Spoke VNets from a VM in a Hub VNet. You can find a "403 This request is not authorized to perform this operation - CannotVerifyCopySource" error in the AzCopy logs or in the Azure Storage logs. The following architecture diagram shows the scenario in which the error occurs.
 
 :::image type="content" source="media/copy-blobs-between-storage-accounts-network-restriction/hub-spoke-network-topology-architecture.png" alt-text="Diagram that shows the 403 error of copying blobs between storage accounts in a Hub & Spoke architecture using Private Endpoints.":::
 
 ### Workaround 1: Create a private endpoint for the destination storage account in the source VNet
-A Possible workaround is to create a private endpoint for the destination storage account in the source VNet. This configuration allows the VM to successfully copy the blobs between the storage accounts by using AzCopy. The following architecture diagram shows the process of copying blobs between storage accounts in the Workaround 1.
+A possible workaround is to create a private endpoint for the destination storage account in the source VNet. This configuration allows the VM to successfully copy the blobs between the storage accounts by using AzCopy. The following architecture diagram shows the process of copying blobs between storage accounts in Workaround 1.
 
 :::image type="content" source="media/copy-blobs-between-storage-accounts-network-restriction/hub-spoke-network-topology-architecture-mitigation-1.png" alt-text="Diagram that shows the process of copying blobs between storage accounts in Workaround 1.":::
 
-### Workaround 2: Place the VM in the same VNet as the source storage account and peer the VNet with the destination VNet
-Another option is to place the VM within the same VNet as the source storage account. Then, establish peering between this VNet and the destination VNet. The following architecture diagram shows the process of copying blobs between storage accounts in Workaround 2.
+### Workaround 2: Place the VM in the same VNet as the source storage account and configure VNet peering between the source and destination VNets
+Another option is to place the VM within the same VNet as the source storage account and set up [virtual network peering](/azure/virtual-network/virtual-network-peering-overview) between this VNet and the destination VNet. This peering needs to be directly between the two VNets and cannot be done through the hub VNet. The following architecture diagram shows the process of copying blobs between storage accounts in Workaround 2.
 
 :::image type="content" source="media/copy-blobs-between-storage-accounts-network-restriction/hub-spoke-network-topology-architecture-mitigation-2.png" alt-text="Diagram that shows the process of copying blobs between storage accounts in Workaround 2.":::
 
+More information, see [Virtual network peering FAQ](/azure/virtual-network/virtual-networks-faq#virtual-network-peering).
+
 ### Workaround 3: Use a temporary staging account to copy the data
 If you're unable to implement the previously mentioned workarounds or are restricted from changing the existing network configuration of the storage account or VNet, you can use a temporary staging account to copy the data: