Merge pull request #312811 from madhurinms/master

Linking VPC article in main aws s3 article

Author: Carolyn135

articles/storage-mover/cloud-to-cloud-migration.md

@@ -24,6 +24,7 @@ Before you begin, ensure that you have:
 - An AWS account with access to the Amazon S3 bucket from which you want to migrate.
 - An [Azure Storage account](../storage/common/storage-account-create.md) to use as the destination.
 - A [Storage Mover resource](storage-mover-create.md) deployed in your Azure subscription.
+- A [private connection setup on Azure](migrations-requiring-private-connections.md), if your AWS source data is in a Virtual Private Cloud (VPC).
 
 ## Limits
 
@@ -32,7 +33,6 @@ The Cloud-to-Cloud Migration feature in Azure Storage Mover has the following li
 - Each migration job supports the transfer of 500 million objects.
 - A maximum of 10 concurrent jobs is supported per subscription. If you need to run more than 10, you can do so by creating a support request.
 - Azure Storage Mover doesn't support automatic rehydration of archived objects. Data stored in AWS Glacier or Deep Archive must be restored before migration. Migration jobs should only be initiated after the data is fully restored.
-- Private Networking is currently not supported. However, Azure Storage Mover's Cloud-to-Cloud feature securely transfers data by limiting S3 access to trusted Azure IP ranges. This approach ensures secure, controlled connectivity over the public internet.
 
 ## Create a multicloud connector for AWS
 

articles/storage-mover/cloud-to-cloud-private-network-configs.md

@@ -103,10 +103,6 @@ SD-WAN and firewall NVAs can terminate VPN tunnels, perform inspection, and appl
 
 SD-WAN NVAs are commonly licensed as either pay-as-you-go (PAYG) or bring-your-own-license (BYOL). Vendor support varies by deployment option.
 
-PAYG: Pay as you go
-
-BYOL: Bring your own license
-
 #### Example deployment (FortiGate NVA in Azure)
 
 **Select a topology** (single VM, active/passive, or active/active) based on availability and throughput requirements.
@@ -206,7 +202,16 @@ After creating the Direct Connect resource, create a private connection in Stora
 4. Only private connections in **Approved** state can be selected.
 5. Remaining job steps are the same as a public S3-to-Blob migration.
 
+## Architecture
+### Cloud-to-cloud Migration flow (private networking)
+
+:::image type="content" source="./media/cloud-to-cloud-networking/cloud-to-cloud-private-networking.png" alt-text="Screenshot of cloud-to-cloud private networking architecture." lightbox="./media/cloud-to-cloud-networking/cloud-to-cloud-private-networking.png":::
+
+Above diagram shown with private networking to AWS but same applies for other private networking scenarios.
 
+### Cloud-to-cloud Migration flow (public S3 bucket to Azure Blob)
+
+:::image type="content" source="./media/cloud-to-cloud-networking/cloud-to-cloud-public.png" alt-text="Screenshot of cloud-to-cloud public workflow." lightbox="./media/cloud-to-cloud-networking/cloud-to-cloud-public.png":::
 
 
 ## Troubleshooting
@@ -276,3 +281,5 @@ For BGP between Azure and AWS, follow: [Tutorial - Configure a BGP-enabled conne
 
 
 
+
+