A practical map from Azure services to AWS equivalents (App Service, Functions, AKS, Azure SQL, Cosmos DB, Service Bus, Key Vault, Azure OpenAI), what usually stays on Microsoft (Entra ID, Microsoft 365, Power BI), how egress is handled, and a migration order that avoids running two half-finished platforms.
Companies move from Azure to AWS for the usual reasons: an acquisition, a team that knows AWS better, a product that needs AWS services, or consolidation onto one cloud. The move is rarely all of Microsoft. Identity, email and productivity usually stay, and the migration is about the application platform.
Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Entra ID as the identity provider. Federate it to IAM Identity Center for AWS access, with SCIM provisioning, so people keep one login.
Microsoft 365, Teams and SharePoint Online.
Power BI, which connects to Redshift, Athena and RDS.
Azure DevOps, if teams are happy with it; pipelines can deploy to AWS with OIDC. Or move to GitHub when convenient.
Since 2024 Microsoft and AWS have both offered to waive data transfer charges for customers moving their data off their clouds, on request and subject to conditions. Ask before moving large datasets. AWS also funds qualifying migrations through the Migration Acceleration Program, with credits for assessment and migration work.
Build the AWS landing zone with Entra ID federated, networking (including a private link between the clouds for the transition) and logging.
Move stateless services first, pointing at Azure data over the private link if needed.
Move each database with its applications, using DMS for replication and a short cutover window.
Move integrations and pipelines last, rebuilt against the new services.
Shut Azure subscriptions down per application as each finishes, so you never pay for two full platforms for long.
Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.
Book a free 30-minute call about it. Bring your setup and your bill; you'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.
Or keep reading
Every AWS Service Retiring in 2026 and 2027, and What to Move To
Amazon Pinpoint ended on October 30, 2026, and App Mesh, Proton, WAF Classic and Greengrass V1 before it. Q Developer's IDE plugins, WorkMail, DevOps Guru and Infrastructure Composer end in 2027, and App Runner, Audit Manager, CloudTrail Lake, Kendra, Q Business and the original Bedrock Agents are closed to new customers. The full list from AWS's lifecycle pages, with the replacements AWS names.
Read
Rehost, Replatform, Refactor, Rebuild: The Migration Strategies, With How to Choose
AWS lists seven migration strategies (retire, retain, rehost, relocate, repurchase, replatform, refactor) and Gartner's older five include rebuild. What each means, what it costs in effort and risk, the AWS tools for each, and how to pick per application rather than for a whole estate.
Read
As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.