AWS Lambda VS Azure Functions_
As of 4 November 2026, Azure Functions is named by 1,300 companies and AWS Lambda by 3,623; AWS Lambda skews to companies under 200 people (47% vs 34%), Azure Functions to companies over 1,000 (39% vs 27%).
As of 4 November 2026 · refreshed daily · counts move as websites, DNS and career sites are re-read.
The website-and-DNS footprint is not comparable between a marketing suite and a CRM: AWS Lambda's script and mail records show on hundreds of thousands of small sites, Azure Functions rarely leaves a trace outside its own apps. Compare on the job-posting numbers; use the footprint for reach.
- AWS Lambda: 2–200 employees
- 47%
- Azure Functions: 2–200 employees
- 34%
- AWS Lambda: 1,000+ employees
- 27%
- Azure Functions: 1,000+ employees
- 39%
- Postings per company, 90 days
- 3.0 · 2.8
- Website or DNS footprint
- 0 · 0
Who chooses which
Share of each tool's companies in every segment. "Leans" marks a gap of more than two points.
| Segment | AWS Lambda | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| Self-employed | 108 | 3% | 24 | 2% | even |
| 2-10 employees | 293 | 8% | 70 | 5% | AWS Lambda |
| 11-50 employees | 580 | 16% | 150 | 12% | AWS Lambda |
| 51-200 employees | 842 | 23% | 228 | 18% | AWS Lambda |
| 201-500 employees | 484 | 13% | 183 | 14% | even |
| 501-1000 employees | 335 | 9% | 133 | 10% | even |
| 1001-5000 employees | 498 | 14% | 220 | 17% | Azure Functions |
| 5001-10000 employees | 136 | 4% | 75 | 6% | Azure Functions |
| 10,001+ employees | 347 | 10% | 217 | 17% | Azure Functions |
| Segment | AWS Lambda | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| Technology & software | 1,951 | 54% | 569 | 44% | AWS Lambda |
| Business & finance services | 771 | 21% | 296 | 23% | even |
| Manufacturing & industry | 238 | 7% | 119 | 9% | Azure Functions |
| Media & content | 135 | 4% | 30 | 2% | even |
| Consumer services & leisure | 111 | 3% | 37 | 3% | even |
| Commerce & trade | 82 | 2% | 47 | 4% | even |
| Utilities & infrastructure | 69 | 2% | 49 | 4% | even |
| Public, community & associations | 53 | 1% | 33 | 3% | even |
| Transport, logistics & rental | 45 | 1% | 28 | 2% | even |
| Automotive | 44 | 1% | 14 | 1% | even |
| Health care | 42 | 1% | 29 | 2% | even |
| Property & construction | 40 | 1% | 34 | 3% | even |
| Segment | AWS Lambda | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| United States | 2,261 | 62% | 699 | 54% | AWS Lambda |
| United Kingdom | 280 | 8% | 110 | 8% | even |
| Germany | 136 | 4% | 60 | 5% | even |
| India | 132 | 4% | 40 | 3% | even |
| Canada | 85 | 2% | 49 | 4% | even |
| France | 66 | 2% | 28 | 2% | even |
| Australia | 61 | 2% | 34 | 3% | even |
| Brazil | 50 | 1% | – | – | outside top 12 |
| Singapore | 41 | 1% | – | – | outside top 12 |
| Netherlands | 39 | 1% | 31 | 2% | even |
| Japan | 34 | 1% | – | – | outside top 12 |
| Italy | 33 | 1% | – | – | outside top 12 |
| Sweden | – | – | 25 | 2% | outside top 12 |
| Belgium | – | – | 22 | 2% | outside top 12 |
| Spain | – | – | 14 | 1% | outside top 12 |
| Portugal | – | – | 11 | 1% | outside top 12 |
| Segment | AWS Lambda | share | Azure Functions | share | Leans |
|---|---|---|---|---|---|
| Software engineering | 7,588 | 54% | 2,375 | 52% | even |
| Data & AI | 2,937 | 21% | 786 | 17% | AWS Lambda |
| IT operations & business systems | 1,562 | 11% | 705 | 16% | Azure Functions |
| Product, program & project management | 224 | 2% | 18 | 0% | even |
| Customer service & success | 124 | 1% | 5 | 0% | even |
| Engineering (non-software) | 120 | 1% | 84 | 2% | even |
| Sales | 59 | 0% | 12 | 0% | even |
| General management & consulting | 29 | 0% | 16 | 0% | even |
| Unclassified | 29 | 0% | 3 | 0% | even |
| Finance & accounting | 17 | 0% | 6 | 0% | even |
| Education & training | 16 | 0% | – | – | outside top 12 |
| Legal, compliance & risk | 14 | 0% | 2 | 0% | even |
| research and science | 13 | 0% | – | – | outside top 12 |
| Quality, safety & environment | 11 | 0% | 5 | 0% | even |
| skilled trades and field service | 10 | 0% | 3 | 0% | even |
| construction and civil | 9 | 0% | 2 | 0% | even |
| arts media and entertainment | 8 | 0% | – | – | outside top 12 |
| Marketing & communications | 8 | 0% | 3 | 0% | even |
| Human resources | 6 | 0% | – | – | outside top 12 |
| Design & UX | 5 | 0% | – | – | outside top 12 |
| Business development & strategy | 4 | 0% | 4 | 0% | even |
| Administration & office | 2 | 0% | 1 | 0% | even |
| facilities cleaning and security | 1 | 0% | – | – | outside top 12 |
| hospitality and food service | 1 | 0% | 3 | 0% | even |
| procurement and purchasing | 1 | 0% | – | – | outside top 12 |
| manufacturing and production | – | – | 1 | 0% | outside top 12 |
The companies behind each column
Companies using AWS Lambda →
Companies using Azure Functions →
paas serverless ranked →
Quote the sentence with the date and the link. The numbers change daily; the link always shows the current ones.
Azure Functions is named by 1,300 companies in job postings and AWS Lambda by 3,623; 0 name both. (Breaknorm, 4 November 2026, https://breaknorm.co/compare/aws-lambda-vs-azure-functions)
Read from the source, not self-reported
Every number on this page can be traced to a page we crawled or a posting we read. Full methodology →
- Job postingsRead hourly from career sites. A tool counts when the employer's own text names it as the team's system; both tools can count for one company.
- Website and DNSScripts and embeds on the company's pages, plus SPF, DKIM, MX and CNAME records of its domain that point at the vendor.
- SegmentsCountry, size and industry from the company profile built from its website.
- Not a reviewNo ratings, prices or feature claims. For those, read the vendors.
AWS Lambda vs Azure Functions: questions
Which is more used, AWS Lambda or Azure Functions?
By companies naming it in their own job postings, AWS Lambda (3,623) over Azure Functions (1,300). By website-and-DNS footprint, Azure Functions (0 vs 0), because its scripts and mail records sit on many small company sites.
Who chooses AWS Lambda?
47% of AWS Lambda companies have 2 to 200 employees, against 34% for Azure Functions. 27% of AWS Lambda companies have over 1,000 employees, against 39% for Azure Functions.
Do companies run both?
0 companies name both in their postings, usually AWS Lambda in marketing and Azure Functions in sales, or during a migration.
Where do these numbers come from?
From the employer's own text in job postings read hourly from career sites, and from scripts found on company websites in our crawl. No vendor data, no surveys.
Get either list your way
The same data as a search, over MCP and the API, as bulk files, or pushed to you as it changes.
Every company on either tool,
with the person who owns it
Filter on AWS Lambda or Azure Functions, and get 1,000 records free.