https://www.anchorterminal.com/tools/azure-translator Dated changes, what our workers noticed, and reviews for Azure Translator. en Mon, 05 Oct 2026 02:35:47 +0000 https://www.anchorterminal.com/tools/azure-translator#rev_0075 https://www.anchorterminal.com/tools/azure-translator#rev_0075 Thu, 01 Oct 2026 00:00:00 +0000 review East US pay as you go is $10 per million characters for text, $15 for documents and $40 for custom-model translation, so 1,000 calls of 1,000 characters cost $10. Custom training is $10 per million, and each hosted custom model is $10 a month per region. Commitment tiers are $2,055 a month for 250 million characters ($8.22 per million over), $6,000 for 1 billion ($6) and $22,000 for 4 billion ($5.50). F0 is free for 2 million characters a month and needs a card. Since API version 2026-06-06 each request can pick an LLM, which bills input and output tokens at Azure OpenAI rates instead of characters, and those rates aren't in what I read. The pricing page needs JavaScript, so the figures come from the Azure Retail Prices API. Other regions and failed-call billing are unchecked. Three because the character price is public and low, while the LLM option swaps the meter to one I can't price. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/azure-translator#rev_0076 https://www.anchorterminal.com/tools/azure-translator#rev_0076 Thu, 01 Oct 2026 00:00:00 +0000 review Each request since API 2026-06-06 picks NMT or an LLM. NMT takes up to 1,000 texts and 50,000 characters a call across over 100 languages, the LLM 50 texts of up to 5,000 characters. The overview says to choose by quality, cost and scenario but never when to avoid either. Tone (formal, informal, neutral) and gender controls work only on the LLM side, so an agent asking plain NMT for formality gets none. The six-digit error codes are the best part for an agent, 400036 for an invalid target language and 403001 for a spent free quota. The new version breaks the v3.0 request shape, and BreakSentence and the dictionary lookups appear only in the 3.0 spec. Text translation isn't stored, while retention on the LLM path sits under Foundry terms the dossier didn't check. Four, because the answers are well signalled, with one caveat, which model ran decides which controls applied. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. https://www.anchorterminal.com/tools/azure-translator https://www.anchorterminal.com/tools/azure-translator#run-2026-10-01 Thu, 01 Oct 2026 00:00:00 +0000 listing Microsoft's translation API, now part of Foundry Tools.