AI-900Chapter 18 of 100Objective 4.5

Azure AI Translator

This chapter covers Azure AI Translator, a cloud-based text translation service that uses neural machine translation to convert text between languages. For the AI-900 exam, this topic falls under Domain 4 (Natural Language Processing), Objective 4.5: Describe capabilities of the Azure AI Translator service. Approximately 5-8% of exam questions touch on translation services, including its features, customization options, and integration with other Azure AI services. Understanding the difference between standard and custom translation, language support, and how to call the service via REST API is essential for exam success.

25 min read
Intermediate
Updated May 31, 2026

Azure AI Translator as a Universal Diplomatic Interpreter

Imagine a high-stakes United Nations summit where every diplomat speaks a different language. The UN hires a team of expert interpreters who work in real-time. Each interpreter is specialized: one listens to French and translates to English, another takes English and renders it in Mandarin, etc. But there's a catch—the interpreters don't just swap words; they understand context, idioms, and cultural nuances. They also maintain a shared glossary of key terms (like 'sanctions' or 'climate change') to ensure consistency. When a diplomat speaks, the sound goes to a central audio mixer that routes it to the appropriate interpreter. The interpreter then produces a translation that is fed back into the diplomat's headset. Azure AI Translator works similarly: it uses neural machine translation (NMT) models that consider the entire sentence context, not just word-for-word substitution. It can be customized with a glossary to enforce domain-specific terminology (like medical or legal terms). The service also supports multiple languages simultaneously, can detect the source language automatically, and handles different text formats (plain text, HTML, etc.). Just as UN interpreters must handle rapid-fire dialogue and maintain accuracy under pressure, Azure AI Translator processes requests in milliseconds, scaling to handle thousands of concurrent translation requests from applications worldwide.

How It Actually Works

What is Azure AI Translator?

Azure AI Translator is a cloud-based, RESTful API service that provides real-time text translation between over 100 languages and dialects. It is part of the Azure Cognitive Services family, specifically under the Language services category. The service uses neural machine translation (NMT) technology, which offers high-quality, fluent translations compared to older statistical machine translation methods. NMT models consider the full context of a sentence to produce more accurate and natural-sounding translations.

Why It Exists

Organizations operate globally and need to communicate in multiple languages. Building in-house translation systems is complex, expensive, and requires vast amounts of bilingual data. Azure AI Translator provides a pre-built, scalable solution that can be integrated into applications, websites, and workflows with minimal code. It enables scenarios like:

Localizing user interfaces and content

Real-time chat translation in customer support

Document translation (via Document Translation feature)

Language detection and transliteration

How It Works Internally

When you send a translation request, the following steps occur at a high level: 1. Request Reception: The API endpoint receives the text, source language (optional), target language(s), and optional parameters like profanity filtering or custom glossary. 2. Language Detection (if source not specified): The service uses a language detection model to identify the source language. The model is trained on large corpora and can detect over 100 languages. 3. Pre-processing: The text is cleaned and segmented into sentences or phrases. For HTML input, the service preserves tags and translates only text content. 4. Neural Translation: The segmented text is passed through a neural network model specific to the language pair. The model uses an encoder-decoder architecture with attention mechanisms to produce the translation. 5. Post-processing: The translated text is reassembled, and optional features like profanity masking or custom glossary terms are applied. 6. Response: The API returns a JSON object containing the translation(s), detected language (if requested), and alignment information.

Key Components, Values, and Defaults

- API Endpoint: https://api.cognitive.microsofttranslator.com/translate?api-version=3.0 - Authentication: Requires an Azure Cognitive Services resource key or a Translator resource key. Passed via Ocp-Apim-Subscription-Key header. - Region: For regional processing, use the regional endpoint (e.g., https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&region=eastus). If using a global endpoint, region can be set via Ocp-Apim-Subscription-Region header. - Supported Languages: Over 100 languages. Full list available at GET /languages?api-version=3.0. - Text Length Limit: Each request can contain up to 50,000 characters across all text elements. Each individual text element (string) can be up to 10,000 characters. - Rate Limits: Varies by pricing tier. Free tier (F0): 2 million characters per month, 20 requests per minute. Standard tier (S1): up to 1 billion characters per month, 100 requests per minute. - Optional Parameters: - from: Source language (e.g., 'en'). If omitted, language detection is performed. - to: Target language(s). Can specify multiple, e.g., to=fr&to=de. - textType: 'plain' (default) or 'html'. - profanityAction: 'NoAction' (default), 'Marked', or 'Deleted'. - profanityMarker: 'Asterisk' (default) or 'Tag'. - includeAlignment: Boolean, returns alignment information mapping source to target words. - includeSentenceLength: Boolean, returns sentence boundaries. - Custom Glossary: You can provide a glossary as part of the request to enforce specific translations for terms. The glossary is an array of objects with text (source) and translation (target) fields.

Configuration and Verification Commands

To use Azure AI Translator, you must first create a Cognitive Services resource or a Translator resource in the Azure portal. The resource will provide an API key and endpoint. Below is a sample cURL command to perform a translation:

curl -X POST "https://api.cognitive.microsofttranslator.com/translate?api-version=3.0&from=en&to=fr" \
-H "Ocp-Apim-Subscription-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d "[{ 'Text': 'Hello, how are you?' }]"

Response:

[
  {
    "translations": [
      {
        "text": "Bonjour, comment allez-vous ?",
        "to": "fr"
      }
    ]
  }
]

To detect language:

curl -X POST "https://api.cognitive.microsofttranslator.com/detect?api-version=3.0" \
-H "Ocp-Apim-Subscription-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d "[{ 'Text': 'Bonjour' }]"

Response:

[
  {
    "language": "fr",
    "score": 1.0,
    "isTranslationSupported": true,
    "isTransliterationSupported": false
  }
]

For transliteration (converting text between scripts):

curl -X POST "https://api.cognitive.microsofttranslator.com/transliterate?api-version=3.0&language=ja&fromScript=Jpan&toScript=Latn" \
-H "Ocp-Apim-Subscription-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d "[{ 'Text': 'こんにちは' }]"

How It Interacts with Related Technologies

Azure Cognitive Services: Translator is one of many services. It can be combined with Speech Service for speech-to-text translation, or with Language Understanding (LUIS) for multilingual bots.

Azure Bot Service: Translator enables multilingual chatbots by translating user input and bot responses.

Azure Logic Apps & Power Automate: Translator connectors allow automatic translation of text in workflows, e.g., translating emails or social media posts.

Document Translation: A separate feature (part of Translator) for batch translating entire documents while preserving formatting. Uses Azure Blob Storage for input and output.

Custom Translator: An extension of Translator that allows users to train custom NMT models using parallel documents. This is used for domain-specific translation (e.g., legal, medical). The custom model is deployed to a dedicated endpoint.

Custom Translator Details

Custom Translator is a feature that enables users to build translation models tailored to specific terminology and style. It requires a minimum of 10,000 parallel sentences (source-target pairs) in a .tmx or .xlf file. The training process involves:

Uploading parallel documents to the Custom Translator portal.

Training a model (takes hours to days depending on data size).

Testing the model with a test set.

Deploying the model to a category ID, which is then used in API calls via the category parameter.

Custom models are especially useful for companies with proprietary jargon. The exam may test whether you know that Custom Translator requires parallel data, and that it is used for domain-specific translation.

Language Support and Variants

Translator supports multiple language variants, such as 'en-us', 'en-gb', 'pt-br', 'pt-pt'. It also supports transliteration for many languages, converting between scripts (e.g., Arabic to Latin, Japanese Kanji to Romaji). The language list is updated regularly; as of the latest, over 100 languages are supported. The exam may ask about the number of languages or specific language support features.

Security and Compliance

Azure AI Translator is SOC, ISO, HIPAA, and FedRAMP compliant when used with specific configurations. Data is encrypted in transit and at rest. By default, translation data is not stored; however, if you use Custom Translator, the training data is stored in the region of your resource. The service is available in multiple Azure regions, and you can choose a regional endpoint for data residency requirements.

Pricing Tiers

Free Tier (F0): 2 million characters per month, 20 requests per minute. Suitable for testing and low-volume scenarios.

Standard Tier (S1): Pay-as-you-go, up to 1 billion characters per month, 100 requests per minute. Higher tiers available for larger volumes.

Custom Translator: Additional cost for training and hosting custom models.

Common Exam Scenarios

The AI-900 exam will test your understanding of:

The difference between standard translation and custom translation.

How to call the Translator API (REST, JSON request/response).

The ability to detect language from text.

The use of glossaries to enforce specific translations.

The integration with other Azure services like Bot Service or Logic Apps.

The fact that Translator supports over 100 languages.

The fact that Custom Translator requires parallel documents for training.

Walk-Through

1

Create a Translator Resource

In the Azure portal, create a new Cognitive Services resource and select 'Translator' as the API type. Choose a pricing tier (F0 for free, S1 for standard). Select a region (e.g., East US) and resource group. After creation, note the endpoint and keys (two keys available for rotation). The endpoint will be either global (`api.cognitive.microsofttranslator.com`) or regional (e.g., `eastus.api.cognitive.microsofttranslator.com`). For the exam, remember that you need a key and endpoint to authenticate.

2

Prepare the Translation Request

Construct a JSON payload containing an array of text objects. Each object has a 'Text' field. Optionally, you can include source language (if known) or omit for auto-detection. Set the target language(s) in the query string. The maximum characters per request is 50,000. For example, to translate 'Hello' to French and German, the URL would include `to=fr&to=de` and the body would be `[{'Text':'Hello'}]`.

3

Send the HTTP POST Request

Use the POST method to the `/translate` endpoint with the required headers: `Ocp-Apim-Subscription-Key` (your key), `Content-Type: application/json`. Optionally, include `Ocp-Apim-Subscription-Region` if using a global endpoint. The request is sent over HTTPS. The service processes the request and returns a JSON response within milliseconds. If the request exceeds rate limits, a 429 (Too Many Requests) status is returned.

4

Parse the JSON Response

The response is a JSON array where each element corresponds to the input text in order. Each element contains a `translations` array with objects having `text` (translated text), `to` (target language), and optionally `alignment` and `sentLen` if requested. For language detection, the response includes `detectedLanguage` object with `language` and `score`. Example: `[{'translations':[{'text':'Bonjour','to':'fr'}]}]`.

5

Handle Custom Translation (Optional)

If using a custom model trained via Custom Translator, include the `category` parameter in the request with the category ID of your deployed model. The service will then use your custom model for translation. Without the category parameter, the standard model is used. Custom models require prior training with parallel documents (minimum 10,000 sentences). The exam may ask about the requirement for parallel data.

What This Looks Like on the Job

Enterprise Scenario 1: Multilingual Customer Support Chatbot

A global e-commerce company wants to provide customer support in 10 languages. They use Azure Bot Service with a multilingual bot. When a customer sends a message in Spanish, the bot uses Azure AI Translator to detect the language and translate the message to English for processing by the backend. The response is then translated back to Spanish. To ensure consistency in product names, they use a custom glossary that maps 'SKU-123' to 'número de artículo 123' across all languages. They also use Custom Translator with historical support chat logs to improve translation accuracy for industry-specific terms. The system handles 10,000 translations per hour, and they chose the S1 tier with a regional endpoint in West Europe to comply with GDPR. A common misconfiguration: forgetting to include the glossary in each request, leading to inconsistent translations.

Enterprise Scenario 2: Document Localization for Legal Contracts

A law firm needs to translate contracts from English to Japanese, French, and German while preserving formatting. They use the Document Translation feature, which processes entire documents (PDF, Word) in batch. They upload documents to an Azure Blob Storage container, then call the Document Translation API. The service translates the text while keeping the layout intact. For legal terms like 'force majeure', they use Custom Translator with a parallel corpus of legal documents. The translation takes about 5 minutes per 100 pages. A common issue: the source document contains images with embedded text; Document Translation does not translate text in images. They must use OCR first via Azure Computer Vision.

Enterprise Scenario 3: Real-Time News Aggregation

A news aggregator app collects articles from global sources and translates them into English. They use the Translator API with language detection to automatically identify the source language. They set profanityAction=Marked to flag offensive content. The app processes 500 articles per minute, requiring high throughput. They use multiple API keys and distribute requests across regions to avoid rate limits. A performance consideration: each article may exceed the 50,000 character limit, so they break articles into chunks and reassemble after translation. If misconfigured, the app might hit rate limits and return 429 errors, causing delays.

How AI-900 Actually Tests This

What AI-900 Tests on Azure AI Translator

Objective 4.5: Describe capabilities of the Azure AI Translator service.

The exam focuses on high-level understanding rather than deep technical details. You need to know:

What the service does (real-time text translation, language detection, transliteration).

That it supports over 100 languages.

The difference between standard translation and custom translation (Custom Translator).

That Custom Translator requires parallel documents for training.

That you can provide a glossary for specific term translations.

That the service can be integrated with other Azure services like Bot Service, Logic Apps, and Power Automate.

That it uses neural machine translation.

The concept of Document Translation for batch processing.

Common Wrong Answers and Why Candidates Choose Them

1. Wrong Answer: 'Translator can translate speech in real time.' - Why chosen: Candidates confuse Translator with Speech Service. Translator is for text; Speech Service handles speech-to-text and text-to-speech. The exam may pair them, but Translator alone does not process audio. 2. Wrong Answer: 'Custom Translator requires no training data.' - Why chosen: Candidates assume it's automatic. In reality, Custom Translator needs parallel documents (source-target sentence pairs). Without data, it cannot improve translation. 3. Wrong Answer: 'Translator supports only 50 languages.' - Why chosen: Outdated knowledge. The service supports over 100 languages; the exact number may change, but the exam expects 'over 100'. 4. Wrong Answer: 'You must specify the source language.' - Why chosen: Many APIs require source language. Translator can auto-detect if omitted, but some candidates think it's mandatory.

Specific Numbers, Values, and Terms

Over 100 languages.

Maximum 50,000 characters per request.

Maximum 10,000 characters per text element.

Free tier: 2 million characters/month, 20 requests/minute.

Standard tier: up to 1 billion characters/month, 100 requests/minute.

Custom Translator requires minimum 10,000 parallel sentences.

API version: 3.0.

Authentication: Ocp-Apim-Subscription-Key header.

Endpoint: api.cognitive.microsofttranslator.com.

Edge Cases and Exceptions

HTML translation: The service can translate HTML content while preserving tags. Set textType=html.

Profanity filtering: Options: NoAction, Marked (replace with asterisks), Deleted.

Language detection confidence score: The score is between 0 and 1. A low score may indicate ambiguous text.

Regional endpoints: If using a regional endpoint, you must also set the region in the header when using the global endpoint. The exam may ask about data residency.

How to Eliminate Wrong Answers

If an answer says 'Translator can translate spoken language', eliminate it because Translator is text-only.

If an answer says 'Custom Translator works out of the box', eliminate it because it needs training data.

If an answer gives a specific language count like '50', it's likely outdated; look for 'over 100'.

If an answer says 'source language is required', remember that auto-detection is possible.

Key Takeaways

Azure AI Translator translates text between over 100 languages using neural machine translation.

The service supports language detection, transliteration, and optional custom glossaries.

Custom Translator requires a minimum of 10,000 parallel sentences to train a domain-specific model.

Maximum request size is 50,000 characters; each text element max 10,000 characters.

Authentication is via Ocp-Apim-Subscription-Key header; regional endpoints require region header.

Free tier (F0) allows 2 million characters/month; Standard (S1) up to 1 billion/month.

Translator can be integrated with Azure Bot Service, Logic Apps, Power Automate, and Document Translation.

The exam expects you to know that Translator is text-only, not speech.

Easy to Mix Up

These come up on the exam all the time. Here's how to tell them apart.

Standard Translation

Uses pre-built neural machine translation models.

No training data required; works immediately.

Suitable for general-purpose translation.

Cannot enforce domain-specific terminology without a glossary.

Lower accuracy for specialized fields like legal or medical.

Custom Translation (Custom Translator)

Uses a custom model trained on user-provided parallel documents.

Requires minimum 10,000 parallel sentences for training.

Ideal for domain-specific translation with proprietary jargon.

Allows fine-tuning of style and terminology.

Higher accuracy for the specific domain but needs ongoing maintenance.

Azure AI Translator

Translates text only.

Input and output are text.

REST API with JSON payload.

Supports over 100 languages.

Can detect language from text.

Azure Speech Service (Speech Translation)

Translates speech in real time.

Input is audio; output can be text or synthesized speech.

Uses SDK or REST API for streaming.

Supports fewer languages for speech translation (around 60).

Includes speaker diarization and voice synthesis.

Watch Out for These

Mistake

Azure AI Translator can translate speech in real time.

Correct

Translator is a text translation service. For speech translation, you need Azure Speech Service, which can integrate with Translator for text output. The exam distinguishes between text and speech services.

Mistake

Custom Translator works without any training data.

Correct

Custom Translator requires a minimum of 10,000 parallel sentences (source-target pairs) to train a custom model. Without data, it cannot improve over the standard model.

Mistake

You must always specify the source language in a translation request.

Correct

The source language is optional. If omitted, the service automatically detects the language. However, specifying it can improve accuracy and speed.

Mistake

Translator supports only 50 languages.

Correct

As of the latest update, Translator supports over 100 languages and dialects. The exact number grows over time; the exam uses 'over 100'.

Mistake

Translator stores all translated data for Microsoft to improve models.

Correct

By default, Microsoft does not store customer translation data. Data is only stored if you use Custom Translator and upload training data. The service is compliant with data privacy standards.

Do You Actually Know This?

Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.

Frequently Asked Questions

How many languages does Azure AI Translator support?

Azure AI Translator supports over 100 languages and dialects. The exact number is regularly updated; as of the latest, it is more than 100. For the exam, remember 'over 100' rather than a specific number. You can get the current list via the GET /languages endpoint.

What is the difference between Azure AI Translator and Custom Translator?

Standard Translator uses pre-trained neural models for general translation. Custom Translator allows you to train a custom model using your own parallel documents (source-target sentence pairs) to improve translation for domain-specific terminology. Custom Translator requires a minimum of 10,000 parallel sentences and is accessed via the same API with a category parameter.

Can Azure AI Translator translate entire documents?

Yes, via the Document Translation feature, which is part of the Translator service. It can translate batch documents (PDF, Word, etc.) while preserving formatting. You upload documents to Azure Blob Storage and call the Document Translation API. It supports multiple languages and can process large volumes asynchronously.

Does Azure AI Translator require a source language?

No, the source language is optional. If omitted, the service automatically detects the language from the text. However, specifying the source language can improve accuracy and reduce latency, especially for short texts.

How do I authenticate to Azure AI Translator?

You authenticate using a subscription key passed in the Ocp-Apim-Subscription-Key header. For regional endpoints, you may also need to provide the Ocp-Apim-Subscription-Region header. Alternatively, you can use Azure Active Directory authentication with a managed identity or service principal.

What is the character limit for a translation request?

Each request can contain up to 50,000 characters across all text elements. Each individual text element (string) can be up to 10,000 characters. If you exceed these limits, you need to split the text into multiple requests.

Can I use Azure AI Translator for real-time chat translation?

Yes, the Translator API is designed for low-latency requests, making it suitable for real-time chat translation. You can integrate it into a chat application to translate messages on the fly. For speech-to-speech translation, you would need to combine with Azure Speech Service.

Terms Worth Knowing

Ready to put this to the test?

You've just covered Azure AI Translator — now see how well it sticks with free AI-900 practice questions. Full explanations included, no account needed.

Done with this chapter?