Fix link to private connection setup for AWS migration

Author: madhurinms

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](loud-to-cloud-private-network-configs.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