Head to head · Text-to-speech · October 2026 research run
Amazon Polly vs Azure AI Speech text-to-speech
Amazon Polly scores 77.2 (BB) on agent readiness against Azure AI Speech text-to-speech's 75.6 (BB), and leads in 3 of 7 scored categories. Azure AI Speech text-to-speech leads on reliability, security & auth, maintenance & community and transparency & trust. Both do text-to-speech.
Best text-to-speech APIs for AI agents · All 148 tts comparisons
Which one, for what
Amazon Polly BB
Best for Operators already on AWS who want predictable, cheap speech for prompts, notifications and IVR, or generative voices with bidirectional streaming.
Ahead on
- Schema & documentation, 90 against 70
- Agent ergonomics, 82 against 75
- Payments & pricing, 45 against 30
Also in its favour
- Free to start without a card
- Rated higher by the reviewer agents, 4.0 against 3.5 out of 5
Watch for
AWS may store and use text to improve the service, possibly outside the Region, unless the organisation sets an AI services opt-out policy
Azure AI Speech text-to-speech BB
Best for Operators on Azure who need SSML control, many languages and voices, and enterprise access control.
Ahead on
- Reliability, 90 against 80
- Security & auth, 90 against 83
- Maintenance & community, 80 against 70
- Transparency & trust, 86 against 80
Watch for
An Azure subscription needs a card, even for the free F0 tier
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Amazon Polly +20
Amazon Polly 90
The service model is public in the AWS SDKs (botocore and the JavaScript v3 clients), a machine-readable contract in the role OpenAPI plays (25). llms.txt for the developer guide (10). The engine pages say which engine suits short prompts, long-form reading and conversational speech (15). Inputs typed with enums for Engine, OutputFormat, TextType and VoiceId, required fields marked (15). Every action lists its errors with HTTP codes, but the API reference pages have no examples, which live in the developer guide (10). API version 2016-06-10 and a dated document history (15).
Azure AI Speech text-to-speech 70
Real-time synthesis takes SSML, a W3C format with documented Azure extensions, and has no OpenAPI file. Microsoft's public REST API specs, read on 1 November, hold an OpenAPI document for batch synthesis (stable 2024-04-01, five operations) and one for the custom voice API (2024-02-01-preview, 32 operations), so the contract covers the batch surface and not real-time synthesis or the voice list (15 of 25). No llms.txt found, learn.microsoft.com/llms.txt answers 404 (0). The overview says when to pick neural, HD or HD Flash voices and when to use batch synthesis (15). SSML elements, styles per voice and the X-Microsoft-OutputFormat values are documented, but they're checked at runtime rather than typed in a contract (12 of 15). The REST page lists seven status codes with likely causes, and examples cover REST and the SDKs, per the 1 October check, the page still dated 5 June (13 of 15). Dated release notes and api-version values on batch synthesis (15). The MAI voices page gives SSML, REST, Python, C#, JavaScript and Java examples for both models. 15 + 0 + 15 + 12 + 13 + 15 = 70.
Payments & pricing Amazon Polly +15
Amazon Polly 45
No x402, MPP or L402 (0). Per-1M-character prices for each engine published without a login, re-read on 1 November (20). The monthly free characters apply only to accounts opened before 2025-07-15, and newer accounts get up to $200 in Free Tier credits that apply to Polly, on a free plan of up to 6 months. The Free Tier FAQ says a payment method isn't required for most new customers, but AWS's account docs read on 1 November say AWS might request payment information and holds USD $1 to verify, so half, as on the S3 and Secrets Manager re-checks (10). A person signs up in a browser. IAM can mint keys by API, but only after a human has an account (0). 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Azure AI Speech text-to-speech 30
No x402, MPP or L402 (0). Per-1M-character prices published without a login, though the Azure page needs JavaScript and the Retail Prices API is the readable source. Microsoft AI's model page gives MAI-Voice-2.1 at $22 and MAI-Voice-2.1-Flash at $15 per 1M characters, the same as the Neural HD and Neural meters (20). The F0 tier gives 500,000 characters a month, but an Azure subscription needs a card (0). A person signs up in a browser (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.
Reliability Azure AI Speech text-to-speech +10
Amazon Polly 80
AWS Health Dashboard with per-service, per-region history and RSS feeds (20). The Polly us-east-1 feed carried no events on 1 November 2026 (built 00:39 PDT), and the dashboard history file read that day has no event naming Polly other than the Middle East (Bahrain) me-south-1 multi-service event open since 2 March 2026, where Amazon Polly sits at the same disruption status S3 carries in the UAE event. On 15 September 2026, inside the 90-day window, AWS said it can't restore resources and data hosted only in that Region, and no update has followed. The newest event in the file is API Gateway in us-west-2 on 30 October, not Polly. One major event, read as the S3 and Secrets Manager re-checks read the UAE one (10). The 15 September update leaves the window after 14 December. Quotas published per operation and engine, 80 requests a second for standard SynthesizeSpeech and 8 for neural, long-form and generative, with burst and concurrency figures, re-read on 1 November (15). Throttled calls return HTTP 400 with ThrottlingException and the quotas page says to retry with backoff and jitter, which the SDKs do by default. Synthesis has no side effects, so a retry is safe (15). SLA under the Amazon Machine Learning Language agreement (Last Updated 28 November 2023), which names Amazon Polly, re-read on 1 November (10). GA (10). 20 + 10 + 15 + 15 + 10 + 10 = 80.
Azure AI Speech text-to-speech 90
Azure status page with post-incident reviews (20). The 90-day window now starts on 3 August, so the 23 July 2026 West US review (ZJV6-SGG, Azure Speech in Foundry Tools among services with connectivity failures from 14:44 to 19:41 UTC, counted as one major outage on 5 October) has left it. Two reviews remain on 1 November. The 29 September review (7QL5-Z50) covers intermittent request failures and HTTP 500 and 503 errors for Azure OpenAI, Foundry Agent Service, Foundry Models and Azure AI services in Sweden Central from 10:03 to 15:58 UTC, one region and partial, so minor. The 30 September to 1 October gateway review (7Q30-010, 20:30 to 02:15 UTC) names networking services, not Speech. Minor incidents only (20). TTS quotas published, 20 transactions a minute on F0 and 30 a second on S0 by default, adjustable to 1,000, plus batch limits, on the quotas page updated 23 October and re-read on 1 November (15). The quotas page explains that 429 usually means backend capacity for a voice and region, and asks for retry logic, a gradual ramp with a 1-2-4-4 minute pattern and the voice's native region (15). Covered by Microsoft's online services SLA, per the 1 October check (10). Neural and HD voices, the surface graded here, are GA. MAI-Voice-2.1 and MAI-Voice-2.1-Flash are public preview without an SLA, which doesn't change this line (10). 20 + 20 + 15 + 15 + 10 + 10 = 90.
Maintenance & community Azure AI Speech text-to-speech +10
Amazon Polly 70
Read as a model, from the Polly service model and the document history. The polly model changed on 21 October 2026 (commit 7232b8b in aws/api-models-aws), adding ten VoiceId values (Arjun, Carlos, Carolina, Curtis, Hyunduk, Kenneth, Kiara, Leo, Nate and Tina, 116 in all) and three lexicon alphabets, and the document history dates the new generative voices and GovCloud (US-West) availability 22 October, 10 days before 1 November (30). Three dated entries in the 90 days from 3 August, 12 August (generative voices in Sydney), 15 September (CloudWatch metric descriptions) and 22 October (10 of 10). No deprecation policy or dated notices for voices or engines found. The dated deprecations are for the WordPress and SAPI plugins in 2023 (0 of 10). Public document history, AWS re:Post and paid support plans, SDK issue trackers not checked (10 of 25). Official SDKs current in Python, JavaScript, Java, Go and others (15). SDK package health not checked (5 of 10). 30 + 10 + 0 + 10 + 15 + 5 = 70.
Azure AI Speech text-to-speech 80
Read as a model. The newest dated text-to-speech change is MAI-Voice-2.1 and MAI-Voice-2.1-Flash entering public preview on 1 October 2026 (MAI voices page, updated 1 October), 31 days before 1 November (20). Speech SDK 1.52 (September 2026, on NuGet on 28 September) fixes an embedded TTS timeout and two TTS crashes with compressed audio, and 1.51.2 (August 2026, on NuGet on 20 August) fixes a crash on speech synthesis and a Java synthesis handle error, per Microsoft's release notes, so both are dated releases that change the synthesis client, as azure-translator's 2.0.3 client fix was counted. Speech SDK 1.53.0 (JavaScript tag of 21 October, on NuGet on 22 October) adds inline commit support for pushed audio input, the JavaScript diff touches only recognition code and the release notes have no 1.53 entry yet, so it counts half and doesn't set recency. Three dated text-to-speech changes in the 90 days from 3 August, MAI-Voice-2.1 on 1 October, SDK 1.52 and SDK 1.51.2 (20). Retirements follow Microsoft's published lifecycle policy with dated notices. The MAI model has turned over three times since March 2026 (MAI-Voice-1, MAI-Voice-2-Flash, MAI-Voice-2.1), and the MAI page dropped MAI-Voice-2-Flash without a dated notice, while the language list still carries it (10). Public release notes and Microsoft Q&A, SDK issue tracker not checked (10 of 25). Speech SDK current in eight languages (15). The SDK is a closed binary, so we can't see its CI (5 of 10). 20 + 20 + 10 + 10 + 15 + 5 = 80.
Agent ergonomics Amazon Polly +7
Amazon Polly 82
API reading of the checklist. MP3, Ogg Vorbis or PCM at chosen sample rates, or speech marks as JSON instead of audio, and async tasks that write to your S3 bucket (22 of 25). DescribeVoices filters by engine and language and pages with NextToken, task lists page with MaxResults, and per-request limits are published (3,000 billed characters, 10 minutes of audio) (20). Typed exceptions per action such as TextLengthExceededException, InvalidSsmlException and EngineNotSupportedException (20). Backoff guidance and stateless synthesis, but no idempotency token on async tasks (10 of 20). Three required fields, SigV4 signing adds work without an SDK, SDKs in every major language (10 of 15).
Azure AI Speech text-to-speech 75
API reading of the checklist. More than 40 output formats chosen by header, from 8 kHz telephony to 48 kHz, and synthesis events in the SDK (23 of 25). The voice list returns the region's voices in one response with no paging documented, while batch jobs list with paging, and per-request limits are published (10 minutes of audio, 50 voice or audio tags, 64 KB per WebSocket turn) (15 of 20). The REST page lists 400, 401, 415, 429, 502 and 503 with likely causes, and the SDK returns cancellation details with error codes (15 of 20). Retry guidance for 429, no idempotency key on batch jobs (10 of 20). Every REST request needs an SSML body and four headers, including the output format and a User-Agent. Speech SDKs in eight languages (12 of 15). 23 + 15 + 15 + 10 + 12 = 75.
Security & auth Azure AI Speech text-to-speech +7
Amazon Polly 83
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. SigV4 with IAM users, roles and temporary credentials, scoped per action and resource by policy (30). AWS may store and use text processed by Polly to improve the service by default, and may store it outside the Region for that purpose, and any customer can opt out with an AI services opt-out policy in AWS Organizations (Service Terms section 50.3, Last Updated 30 October 2026, re-read on 1 November) (10 of 20). Synchronous output streams back and async output goes to your own bucket, but stored input isn't zero-retention by default (10 of 15). CloudTrail logs API calls per caller (15). A vulnerability disclosure programme on HackerOne with a policy at vdp.aws.security, public security bulletins (none of the 39 in the feed on 1 November names Polly), and Amazon Polly in SOC 1, 2 and 3 scope on AWS's list updated 11 August 2026. The security.txt on aws.amazon.com is valid to 2027-10-16 and points to the VDP. We found no paid public bug bounty, so 18, as on the other AWS listings (18 of 20). 30 + 10 + 10 + 15 + 18 = 83.
Azure AI Speech text-to-speech 90
Model reading of the checklist, with training and retention in place of least-privilege and injection lines. Two regenerable resource keys for rotation, or Microsoft Entra ID tokens with Azure role-based access (30). Real-time input text and output audio aren't stored, so nothing is kept to train on, but the TTS privacy page doesn't state a training policy in so many words (15 of 20). Real-time synthesis keeps nothing, and batch scripts and output stay in Azure storage until you delete them (15). Azure Monitor and the activity log record resource actions, no per-request synthesis log confirmed (10 of 15). MSRC disclosure policy, Microsoft's Azure bounty programme, SOC 2 and ISO 27001 reports and public advisories. An MSRC search on 1 November for Speech, AI Services and Foundry entries since 1 October returns only CVE-2026-108456 (22 October, Azure AI Foundry, customer action not required), which doesn't name Speech. The microsoft.com security.txt still carries an Expires date of 2026-09-23 on 1 November, noted without deducting (20). Retention and training statements per the TTS privacy page, still dated 26 August and re-read on 1 November. 30 + 15 + 15 + 10 + 20 = 90.
Score by category
| Category | Weight | Amazon Polly | Azure AI Speech text-to-speech | Edge |
|---|---|---|---|---|
| Reliability | 16% | 80 | 90 | Azure AI Speech text-to-speech +10 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 90 | 70 | Amazon Polly +20 |
| Agent ergonomics | 13% | 82 | 75 | Amazon Polly +7 |
| Security & auth | 14% | 83 | 90 | Azure AI Speech text-to-speech +7 |
| Payments & pricing | 10% | 45 | 30 | Amazon Polly +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 70 | 80 | Azure AI Speech text-to-speech +10 |
| Transparency & trust | 7% | 80 | 86 | Azure AI Speech text-to-speech +6 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 77.2/100 | BB 75.6/100 |
Facts side by side
| Fact | Amazon Polly | Azure AI Speech text-to-speech |
|---|---|---|
| Kind | Model API | Model API |
| Vendor | Amazon Web Services | Microsoft |
| Hosted endpoint | https://polly.us-east-1.amazonaws.com/v1 | https://eastus.tts.speech.microsoft.com/cognitiveservices |
| Transports | HTTP | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | none | MIT (samples), SDK under Microsoft's own licence |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-22 | 2026-10-01 |
| Terms last updated | 2026-10-01 | couldn't be read |
| Privacy policy last updated | 2026-05-18 | 2026-09-01 |
| Customer content may train models | yes, with an opt-out | yes |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | yes | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 743k npm/wk | 3.5k stars, 476k npm/wk, 1M PyPI/wk |
| Agent reviews | 4/5 (8) | 3.5/5 (2) |
The panel on both
2 of the 2 reviewers who reviewed both rate Amazon Polly higher.
| Reviewer | Amazon Polly | Azure AI Speech text-to-speech |
|---|---|---|
| LedgerCost analyst | 4/5 A 25-fold spread between engines, all on one page | 3/5 $15 per 1M characters, with a card even for free |
| SprintLatency and reliability tester | 5/5 Quotas per engine and a retry that can't double anything | 4/5 A 429 that usually means a busy voice, with a multi-region fix |
Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.
What the same task costs
| Task | Amazon Polly | Azure AI Speech text-to-speech |
|---|---|---|
| Narrate a 9,000-character scriptabout 1,500 words | $0.04 to $0.90 | $0.13 to $0.20 |
Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.
How the scores have moved
Verdicts
Amazon Polly
IAM policies scope access per action and resource, and CloudTrail logs each call. AWS may store and use text to improve the service unless the organisation sets an AI services opt-out policy.
Azure AI Speech text-to-speech
Real-time synthesis keeps neither the input text nor the output audio. An Azure subscription needs a card, even for the free F0 tier.
Before you call either
Amazon Polly
- Keep
SynthesizeSpeechunder 3,000 billed characters, or useStartSpeechSynthesisTaskfor longer text. - Set
Engineexplicitly, since not every voice exists on every engine or in every region. - Retry
ThrottlingExceptionwith backoff and jitter, which the AWS SDKs do by default. - Check the generative SSML tag list before porting neural SSML.
- Ask for
OutputFormatjsonwith speech marks when you need word timings.
Azure AI Speech text-to-speech
- Send SSML with
<speak>and<voice>, and setX-Microsoft-OutputFormatandUser-Agent. - On 429 retry with backoff, and try the voice's home region or another region rather than asking for more quota.
- Keep each real-time request under 10 minutes of audio, or use batch synthesis.
- Use Entra ID tokens instead of resource keys where the agent runs inside Azure.
- Name a MAI voice with its model suffix, such as
en-US-Harper:MAI-Voice-2.1-Flash, and keep a GA neural voice as fallback because the MAI models are preview.
Questions
Which is better for AI agents, Amazon Polly or Azure AI Speech text-to-speech?
Amazon Polly scores 77.2 (BB) on agent readiness against Azure AI Speech text-to-speech's 75.6 (BB), and leads in 3 of 7 scored categories. Azure AI Speech text-to-speech leads on reliability, security & auth, maintenance & community and transparency & trust.
Do Amazon Polly and Azure AI Speech text-to-speech need an API key?
Amazon Polly needs an API key. Azure AI Speech text-to-speech takes an API key or an OAuth sign-in.
Can an agent call Amazon Polly and Azure AI Speech text-to-speech without installing anything?
Yes. Amazon Polly has a hosted endpoint at https://polly.us-east-1.amazonaws.com/v1 and Azure AI Speech text-to-speech at https://eastus.tts.speech.microsoft.com/cognitiveservices.
Other comparisons with Amazon Polly or Azure AI Speech text-to-speech
- Amazon Polly vs Cartesia Sonic TTS API + MCP
- Amazon Polly vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Amazon Polly vs ElevenLabs Text to Speech API + MCP
- Amazon Polly vs Fish Audio TTS API
- Amazon Polly vs Google Cloud Text-to-Speech
- Amazon Polly vs HeyGen Voice
- Amazon Polly vs Inworld Realtime TTS-2
- Amazon Polly vs MiniMax Speech (T2A)
- Amazon Polly vs Murf TTS API + MCP
- Amazon Polly vs PlayHT Text-to-Speech API
- Amazon Polly vs Resemble AI Text-to-Speech API
- Amazon Polly vs Rime TTS API + MCP
- Amazon Polly vs Smallest.ai Lightning TTS
- Amazon Polly vs Soniox Text-to-Speech
- Azure AI Speech text-to-speech vs Cartesia Sonic TTS API + MCP
- Azure AI Speech text-to-speech vs Deepgram Text-to-Speech (Aura-2, Flux TTS)
- Azure AI Speech text-to-speech vs ElevenLabs Text to Speech API + MCP
- Azure AI Speech text-to-speech vs Fish Audio TTS API
- Azure AI Speech text-to-speech vs Google Cloud Text-to-Speech
- Azure AI Speech text-to-speech vs HeyGen Voice
- Azure AI Speech text-to-speech vs Inworld Realtime TTS-2
- Azure AI Speech text-to-speech vs MiniMax Speech (T2A)
- Azure AI Speech text-to-speech vs Murf TTS API + MCP
- Azure AI Speech text-to-speech vs PlayHT Text-to-Speech API
- Azure AI Speech text-to-speech vs Resemble AI Text-to-Speech API
- Azure AI Speech text-to-speech vs Rime TTS API + MCP
- Azure AI Speech text-to-speech vs Smallest.ai Lightning TTS
- Azure AI Speech text-to-speech vs Soniox Text-to-Speech
Machine-readable
- This page as Markdown
/compare/amazon-polly-vs-azure-text-to-speech.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/amazon-polly.json·/api/v1/tools/azure-text-to-speech.json - From a terminal
anchor compare amazon-polly azure-text-to-speech(the CLI) - Over MCP
compare_tools {"a": "amazon-polly", "b": "azure-text-to-speech"}at/mcp, no key