Prompt
Microsoft Translator glossary support
Latest observation
Nov 2, 2026
OpenAI APIWeb search: off
Microsoft Translator does not offer a true “upload a glossary” feature in the same way some translation platforms do, but it does support terminology consistency through a couple of related options:
1) Custom Translator
- You can train custom models with your own bilingual data.
- Useful if you want the service to prefer certain translations for domain-specific terms.
- Best for larger, recurring use cases.
2) Dictionary / phrase handling in the Translator API
- The Microsoft Translator Text API has limited support for terminology control using dictionary-style examples in some workflows.
- This is not a full glossary manager, but it can help bias translations for specific terms or phrases.
3) Document translation with glossary-like behavior
- Depending on the document translation workflow, you may be able to influence terminology using custom models or pre/post-processing.
- Not equivalent to a formal glossary feature.
4) Post-editing / terminology QA
- Common workaround: translate first, then automatically replace approved terms using a term list.
- Often used in enterprise pipelines.
Important caveat
If you mean:
- “Can I upload a CSV/TMX glossary and have Microsoft Translator always apply it?”
Then the answer is generally no, not as a native glossary feature.
If you want, I can also give you:
- the current Microsoft-supported alternatives,
- an example of how to enforce terminology in code, or
- a comparison with DeepL / Google / Amazon glossary support.