Introduction
Translation isn’t just converting words—it’s enabling global communication. Yet for businesses operating worldwide, achieving accuracy, speed, and domain-specific terminology has been a persistent challenge. Market trends show that 70% of consumers prefer content in their native language, and enterprises are under pressure to deliver real-time multilingual experiences without sacrificing quality.
That’s why we’re introducing Adaptive Custom Translation (AdaptCT) in Microsoft Foundry Tools—a breakthrough that redefines how translation systems are customized. Instead of retraining models from scratch, AdaptCT leverages existing LLMs like GPT-4o, combined with tiny datasets and smart indexing, to deliver instant, domain-specific translations.
The Problem with Traditional Custom Translation
For years, building high-quality custom translation models has been resource-heavy and slow. Traditional approaches require:
- Massive human-curated datasets (10,000+ sentence pairs)
- Long training cycles (a day to several days)
- Manual deployment processes
- Retraining for every update
This works for static, high-volume content like legal documents. But for rapidly changing content—support tickets, product updates, technical documentation—traditional solutions fall short.
Adaptive Custom Translation: A Market-Driven Game-Changer
Adaptive Custom Translation flips the script. Instead of building a new model, it enhances existing LLMs using a small dataset and indexing.
Think of it this way:
- Traditional Custom Translator: Builds a custom car from scratch.
- Adaptive Custom Translation: Takes a Ferrari and fine-tunes it for your specific track.
Why it matters in today’s market
Speed and simplicity are critical for global communication. AdaptCT delivers both by removing the heavy overhead of traditional systems. It enables customization with minimal data—starting from just five parallel sentences and scaling up to 10,000—making it ideal for niche industries and rapid prototyping. Updates happen in minutes: refresh your dataset, rebuild the index, and go live instantly without retraining or redeployment. With zero maintenance requirements, enterprises can simply upload datasets, create indexes, and call translate APIs, turning translation into a strategic advantage rather than a bottleneck.
AdaptCT Real-World Impact
AdaptCT delivers tangible impact across critical business scenarios. For customer support, launching a new SaaS feature becomes effortless—upload 50–500 aligned sentence pairs, create an index in minutes, and translations instantly reflect updated terminology, compared to traditional workflows that require 10,000+ pairs and 24–48 hours of retraining. In e-commerce, AdaptCT enables continuous product updates by maintaining a living dataset, ensuring instant multilingual consistency across channels. For technical documentation, frequent API changes across multiple languages are no longer a bottleneck—small datasets of technical terms can be indexed and updated on demand, guaranteeing accuracy and consistency at scale. This agility transforms translation from a time-consuming process into a strategic enabler for global growth.
How It Works
AdaptCT streamlines the process by leveraging existing LLMs with intelligent indexing. When a translation request is submitted, it includes the language pair and a dataset index. adaptCT then applies few-shot learning to retrieve the most relevant sentence pairs, enabling the LLM to generate translations that are not only accurate but also tailored to your domain-specific terminology and style. This approach ensures precision and agility without the overhead of traditional retraining.
Quick Start Code
Step 1: Create a Project
curl -X POST "https://<your-resource>.cognitiveservices.azure.com/translator/customtranslator/api/texttranslator/v1.0/workspaces" \ -H "Ocp-Apim-Subscription-Key: <your-key>" \ -H "Content-Type: application/json" \ -d '{ "name": "my-translation-project", "subscription": { "billingRegionCode": "<billing-region>", "subscriptionKey": "<your-key>" } }'
Step 2: Upload Your Translation Pairs (e.g., English to French)
curl -X POST "https://<your-resource>.cognitiveservices.azure.com/translator/customtranslator/api/texttranslator/v1.0/documents/import?workspaceId=<workspace-id>" \ -H "Authorization: Bearer <token>" \ -F "DocumentDetails=[{ \"DocumentName\": \"product-terms\", \"DocumentType\": \"Adaptive\", \"FileDetails\": [{ \"Name\": \"translations.tmx\", \"LanguageCode\": \"en\", \"OverwriteIfExists\": true }] }]" \ -F "FILES=@translations.tmx"
Step 3: Create the Index
curl -X POST "https://<your-resource>.cognitiveservices.azure.com/translator/customtranslator/api/texttranslator/v1.0/index?workspaceId=<workspace-id>" \ -H "Content-Type: application/json" \ -d '{ "documentIds": ["123456"], "IndexName": "product-index", "SourceLanguage": "en", "TargetLanguage": "fr" }'
Step 4: Translate with Your Dataset Index
- Use the New Microsoft Foundry:
- Select the resource you used to create the dataset index
- Select Models > Select AI Services > Select Azure Translation – Text translation
- Ensure your current resource has GPT-4o or GPT-4o-mini deployment
- In Deployed model dropdown, select gpt-4o or gpt-4o-mini
- In Configuration, select Adaptive customization
- Select Use dataset index ID > Select your index from the dropdown
- Type text to translate and select target language (to/from English is only supported)
- Use Text Translation API with your dataset index ID. Your translations will automatically be adapted based on your dataset index.
Data Format: Keep It Simple
- TMX Format (Translation Memory eXchange)
<?xml version="1.0" encoding="UTF-8"?> <tmx version="1.4"> <body> <tu> <tuv xml:lang="en"> <seg>Click the submit button</seg> </tuv> <tuv xml:lang="fr"> <seg>Cliquez sur le bouton soumettre</seg> </tuv> </tu> </body> </tmx>
- TSV Format (Tab-Separated Values)
en fr Click the submit button Cliquez sur le bouton soumettre Upload your file Téléchargez votre fichier
When to Use AdaptCT vs. Custom Translator
Here’s a decision matrix:
| Your Scenario | Choice |
| Low-volume, frequently changing content | AdaptCT |
| Need updates within minutes | AdaptCT |
| Limited translation data (< 10K pairs) | AdaptCT |
| Support tickets, chat, dynamic content | AdaptCT |
| High-volume, consistent content | Custom Translator |
| Legal/medical with strict terminology | Custom Translator |
| Large dataset available (> 10K pairs) | Custom Translator |
| Content changes infrequently | Custom Translator |
Good Practices from the Trenches
- Start Small, Iterate Fast – Begin with your most critical 50-100 sentence pairs. Test, measure, and expand.
- Organize by Domain – Create separate indexes for different domains: customer-support-index, product-docs-index, marketing-content-index, etc.
- Quality Over Quantity – 5 perfect sentence pairs are more impactful than 500 mediocre ones. Focus on high-impact terminology.
- Version Your Datasets – Use naming conventions, e.g, product-v1, product-v2-holiday-season, product-v3-new-features, etc.
- Monitor and Measure – Track which translations are working through user feedback, translation accuracy and coverage of your terminology.
- Avoid Common Pitfalls – Achieving high-quality translations requires disciplined practices:
- Do not treat the process like Custom Translator by uploading thousands of sentence pairs “just in case.” Instead, start small with 50–500 in domain high-value pairs and expand based on identified gaps.
- Maintain proper alignment between source and target sentences using TMX or carefully aligned TSV files, supported by rigorous quality checks.
- Provide full sentence context rather than isolated words and phrases to preserve meaning and usability.
- Use blind-testset to validate every index update before full deployment to prevent costly errors.
The Future is Adaptive
Adaptive Custom Translation represents a shift in how we approach translation customization. Instead of building heavyweight solutions for every scenario, we’re using smart indexing and few-shot learning to adapt powerful models on the fly.
What This Means for You
- Faster time-to-market for multilingual features
- Lower costs (less data, less training time)
- More agile translation workflows
- Better user experiences with up-to-date terminology
Resources
- Check out our GitHub Repository
- Watch our demo on YouTube
- Azure AI Translator Documentation
- Text Translation API Preview
- Azure AI Foundry
- Custom Translator Overview

0 comments
Be the first to start the discussion.