Quick answer
Azure Functions is cheaper than AWS Lambda for 50M requests a month and 500M requests a month and costs the same for 5M requests a month. For 50 million requests a month at 200 ms, 512 MB and 10 ms of CPU each in US East, it costs $83.40 a month against $86.47, and it is cheaper in all 12 regions covered. Playxoft's comparison uses official list prices checked October 14, 2026, with the always-free allowances applied.
- Official list prices
- 3 usage levels
- 12 regions
- Feature comparison
- Free calculator
How to compare AWS Lambda and Azure Functions costs
- 1Pick a usage level (5M requests, 50M requests, 500M requests), then change the numbers or add more items with the + buttons.
- 2Choose the Region where your users are. Prices differ by region.
- 3Adjust the numbers in each card. Every field has an i tip explaining it.
- 4Compare the two monthly totals, then open Cost breakdown to see exactly how AWS Lambda and Azure Functions bill each line.
Which is cheaper, AWS Lambda or Azure Functions?
Monthly list prices in US East with the always-free allowances applied:
| Usage per month | AWS Lambda | Azure Functions | Cheaper |
|---|---|---|---|
| 5M requests: 100 ms, 256 MB, 10 ms CPU each | $0.80 | $0.80 | Same |
| 50M requests: 200 ms, 512 MB, 10 ms CPU each | $86.47 | $83.40 | Azure Functions by $3.07 |
| 500M requests: 200 ms, 1 GB, 20 ms CPU each | $1,759.80 | $1,693.40 | Azure Functions by $66.40 |
Azure Functions is cheaper for 50M requests a month in all 12 regions the calculator covers. Azure Functions is priced on the Consumption plan, which bills each execution like Lambda.
What are the Lambda and Azure Functions unit prices?
List prices in AWS us-east-1 (N. Virginia) and Azure eastus (East US), read on October 14, 2026:
| Price (US East, on-demand) | AWS | Azure |
|---|---|---|
| Serverless, per million requests | $0.20 | $0.20 |
| Serverless compute | $0.0000166667 per GB-s | $0.000016 per GB-s |
Is AWS Lambda or Azure Functions cheaper in your region?
50 million requests a month at 200 ms, 512 MB and 10 ms of CPU each, priced in each of the 12 regions the calculator covers:
| Region | AWS Lambda | Azure Functions | Cheaper |
|---|---|---|---|
| US East | $86.47 | $83.40 | Azure Functions |
| US West | $86.47 | $83.40 | Azure Functions |
| Canada | $86.47 | $83.40 | Azure Functions |
| Brazil (São Paulo) | $86.47 | $83.40 | Azure Functions |
| Ireland | $86.47 | $83.40 | Azure Functions |
| UK (London) | $86.47 | $83.40 | Azure Functions |
| Germany (Frankfurt) | $86.47 | $83.40 | Azure Functions |
| India | $86.47 | $83.40 | Azure Functions |
| Singapore | $86.47 | $83.40 | Azure Functions |
| Japan (Tokyo) | $86.47 | $83.40 | Azure Functions |
| South Korea (Seoul) | $86.47 | $83.40 | Azure Functions |
| Australia (Sydney) | $86.47 | $83.40 | Azure Functions |
How do AWS Lambda and Azure Functions compare on features?
| AWS Lambda | Azure Functions | |
|---|---|---|
| Billing | Requests + duration × memory, per 1 ms | Executions + duration × memory (Consumption plan) |
| Maximum run time | 15 minutes | 10 minutes (Consumption); HTTP responses 230 s |
| Memory | 128 MB to 10,240 MB | Up to 1.5 GB (Consumption) |
| Free tier | 1M requests + 400,000 GB-s a month | 1M executions + 400,000 GB-s a month |
| Requests per instance | 1 at a time | Many (HTTP default 100) |
| Where code runs | One AWS region | One Azure region |
| Languages | Node.js, Python, Java, .NET, Ruby | C#, JavaScript, TypeScript, Python, Java, PowerShell |
Facts from each provider's own documentation, checked October 14, 2026.
What are the key differences between AWS Lambda and Azure Functions?
- Rounding. Lambda bills the memory you configure, per millisecond. Azure's Consumption plan rounds observed memory up to the next 128 MB and bills at least 100 ms per execution.
- Limits. Lambda runs up to 15 minutes with up to 10,240 MB; the Consumption plan up to 10 minutes with 1.5 GB, and HTTP responses within 230 seconds.
- Plans. Microsoft now calls the Consumption plan legacy and recommends Flex Consumption for new Linux apps; Linux Consumption apps retire on September 30, 2028.
- Free tier. Identical: 1 million requests and 400,000 GB-seconds a month.
Should you choose AWS Lambda or Azure Functions?
Choose AWS Lambda if
- your functions finish in well under 100 ms
- you need more than 1.5 GB of memory or runs up to 15 minutes
- you build on AWS event sources
Choose Azure Functions if
- you write C# and .NET and use Visual Studio tooling
- you integrate with Microsoft 365, Entra ID or Azure services
- you want Durable Functions for long workflows
More comparisons: AWS vs Azure · Amazon EC2 vs Azure Virtual Machines · AWS Lambda vs Cloudflare Workers · AWS Lambda vs Google Cloud Run · Google Cloud Run vs Cloudflare Workers · Amazon S3 vs Azure Blob Storage · Amazon RDS vs Azure Database for PostgreSQL · Amazon DynamoDB vs Azure Cosmos DB.
Where do these prices come from?
Both sides use the provider's own published price list, read on October 14, 2026, for the same region, with the always-free allowances applied.
- AWS: AWS Lambda pricing
- Azure: Azure Functions pricing
Prices are in US dollars, on-demand, for Linux, with no commitments. Every figure on this page is generated from the same price snapshot as the calculator, and automated tests check each claim whenever the prices change. A month is 730 hours and 1 TB is 1,024 GB. Providers change prices from time to time, so for a purchase decision confirm the final figure in the provider's console.
Moving between AWS Lambda and Azure Functions?
Playxoft builds and runs production backends on AWS, Google Cloud, Azure and Cloudflare, and plans migrations between them with no surprise downtime, including white-label work for agencies. Send us your architecture or last month's invoice and we will tell you, free, which side is cheaper for your real usage. Get a free cloud cost review.
Frequently asked questions
Last updated by the Playxoft engineering team.