Translator Hub replaces the Collaborative Translation Framework (CTF)

In May 2018, a European privacy law, the General Data Protection Regulation (GDPR), is due to take effect. It imposes new rules on companies, government agencies, non-profits, and other organizations that offer goods and services to people in the European Union (EU) or that collect and analyze data tied to EU residents. The GDPR applies no matter where you are located.

To prepare Microsoft Translator for full compliance with the GDPR, the functionality of the Collaborative Translation Framework (CTF) will become read-only, for both the Microsoft Translator Text API and the Translator Web Widget, on February 1, 2018. The removed functions of the Translator API allowed users to share submissions to the API with anyone, without a specific control over who the submission is shared with or when to stop sharing.

The sharing functions are AddTranslation and AddTranslationArray, which are rarely used.

Microsoft is committed to making Microsoft Translator and Microsoft Cognitive Services fully adhere to the data protection mandate, and this requires changes to the Microsoft Translator API.

Microsoft Translator Hub and the Translator Hub API

The Microsoft Translator Hub and the Translator Hub API provide functionality that is similar to the Collaborative Translation Framework. The Hub functionality is fully GDPR compliant, providing you with full control over who to share data with, and when to stop sharing.

The Translator Hub API differs from the CTF AddTranslation function by taking documents rather than individual sentence pairs. The document format can be any of the Hub-supported document formats (XLIFF, TMX, LCL, DOCX, PDF, HTML, TXT, ALIGN).

In detail, you can:

  • Upload new documents, and obtain the status of your upload.
  • Obtain a list of the documents used in a training.
  • Obtain a list of documents usable for a training, in a project.
  • Create a project.
  • Obtain a list of projects in your workspace.
  • Obtain a list of trainings for a project.
  • Submit a training run. You may specify the documents to use for training, tuning and as a dictionary. You can ask for automatic deployment in the training request.

Submitting files as a dictionary allows you to control the translation of words, phrases and sentences with 100% probability, guaranteeing your translation for the given words in the source language. 

Over the next few months, we’ll have sample code available.

More on changes to the CTF functions and Microsoft Translator API due to GDPR compliance is here


  1. Announcement: Changes to the Collaborative Translation functions
  2. Translator Hub replaces the Collaborative Translation Framework (CTF)
  3. Microsoft Translator Moves to the Azure portal
  4. API - Translator datacenters
  5. API and Hub: Confidentiality
  6. API - Translator Speech: Microsoft Translator Speech API references
  7. API - Translator Text: How to report an issue with the API
  8. API - Translator Text / Speech: Microsoft Translator with IP filtered firewalls
  9. API - Translator Text / Speech: Get a report of your consumption
  10. API - Translator Text / Speech: Using the API key directly in the call. No more token.
  11. API - Translator Text / Speech: Why are there two keys for my API subscription?
  12. API - Translator Text: Hybrid Neural Machine Translation
  13. API - Translator Text: Using Neural MT Systems
  14. API- Translator Text: Standard category languages
  15. API - Translator Text: My CAT tool isn't working and is asking for the Client ID and Client Secret
  16. API - Translator Text: Limits
  17. API - Translator Text: How Microsoft Translator counts characters
  18. API - Translator Text: Gender selection in the Speak() method
  19. API - Translator Text: Trados plugin for Microsoft Translator
  20. API - Translator Text: Java- Using SSL with the Microsoft Translator API
  21. API - Translator Text: European datacenter
  22. API - Translator Text: Languages detected by the Detect() method
  23. API - Translator Text: First few Microsoft Translator API requests succeed, then the calls fail
  24. API - Translator Text: Profanity filtering in the TranslateArray() method
  25. API - Translator Speech: Signal the end of the utterance
  26. Hub: API available
  27. Hub: Translator Hub Resource Guide
  28. Hub: August 2016 Release notes
  29. Hub: Deployment of a custom system requires a Microsoft Translator Text API subscription in the Azure portal
  30. Hub: Capacity of custom Microsoft Translator Hub systems
  31. Hub: Building a custom system using a dictionary only
  32. Business Applications: Security and Privacy in Microsoft Office Products

Feedback and Knowledge Base