SOFTWARE / SYSTEMS / AIEngineering news. Technical depth.
NEWS / Cloud · 2 MIN READ

AWS Transform adds Azure-to-AWS code conversion for .NET

AWS Transform's Azure-to-AWS .NET code conversion is generally available for functions, blob storage and queues. Cosmos DB conversion is in preview.

Announcement: · From AWS

AWS announced general availability of Azure SDK-to-AWS SDK application code conversion in AWS Transform on October 16, 2026. The capability targets Microsoft Azure cloud-native .NET applications. According to the AWS announcement, Transform’s .NET modernization agent identifies Azure service code and converts it to corresponding AWS service code.

Supported services and availability

The launch covers three generally available conversion paths:

  • Azure Functions to AWS Lambda functions
  • Azure Blob Storage to Amazon S3
  • Azure Queue Storage to Amazon SQS

Azure Cosmos DB-to-Amazon DynamoDB conversion is available in preview, not generally available.

The launch notice also lists AWS Transform as available in eight AWS Regions: US East (N. Virginia), Asia Pacific (Mumbai, Tokyo, Seoul, Sydney), Canada (Central), and Europe (Frankfurt, London).

Review the assessment before conversion

According to AWS’s workflow description, Transform discovers Azure SDK usage in submitted source code and presents conversion options in an assessment report and modernization plan. Engineers can accept or adjust those options before running modernization.

AWS says Transform then converts the identified Azure service code to AWS SDK calls and validates that the changes are incorporated into the transformed code.

Separate code conversion from behavioral verification

AWS describes validation here in terms of checking that changes were incorporated into the code. Engineers should assess runtime behavior separately: test authorization, function triggers, retry behavior and failure handling against application requirements rather than treating a completed rewrite as proof of production readiness.

For the preview Cosmos DB-to-DynamoDB path, also review data-model and query assumptions before choosing it for a migration.

The useful planning step is the opportunity to review proposed conversions before modernization runs. Treat that plan as an input to migration decisions, not as a substitute for application-level testing.

SOURCES & CONTEXT

See the original announcement for availability and release details.