Originally published on PkLavc.
Confirmed facts
On October 16, 2026, AWS announced the general availability of Azure-to-AWS SDK code conversion in AWS Transform, a feature designed to automate migration of Microsoft Azure cloud-native .NET applications to AWS.
The service identifies Azure service code within submitted .NET source code and converts it to equivalent AWS SDK calls, validating that changes are incorporated into the transformed output.
AWS Transform is available in eight AWS Regions: US East (N. Virginia), Asia Pacific (Mumbai, Tokyo, Seoul, Sydney), Canada (Central), and Europe (Frankfurt, London).
Conversion support includes Azure Functions to AWS Lambda, Azure Blob Storage to Amazon S3, and Azure Queue Storage to Amazon SQS. Azure Cosmos DB to Amazon DynamoDB conversion is available in preview status.
Technical analysis
The feature operates through an assessment phase where AWS Transform discovers Azure SDK usage in the submitted codebase, presenting conversion options in both an assessment report and modernization plan. Developers can accept these options or modify them before execution.
This approach addresses a significant engineering challenge in cross-cloud application modernization by automating what was previously manual code refactoring. The service's ability to translate service calls between cloud providers reduces migration complexity for .NET applications leveraging serverless and storage services.
The regional availability across eight AWS Regions suggests the service is designed for global enterprise use, though the announcement does not disclose processing requirements, data residency handling, or transformation accuracy metrics. The preview status of Cosmos DB to DynamoDB conversion indicates ongoing refinement of that specific mapping.
Supported conversions: Azure Functions → AWS Lambda, Azure Blob Storage → Amazon S3, Azure Queue Storage → Amazon SQS
Cosmos DB to DynamoDB conversion is in preview
Service requires .NET application source code submission for analysis
Continue reading: Full technical article on PkLavc
Explore more technology articles: PkLavc Tech Blog
Top comments (0)