Microsoft

API - Translator Text: European datacenter

Microsoft Translator is served out of multiple datacenters. These datacenters are located in the United States, east and west coast, in Europe (Dublin, Ireland) and in Asia (Hong Kong). 
Requests to the Microsoft Translator API are handled by the datacenter that is closest to where the request originated. 

Here are two references to Microsoft's Dublin datacenter:


To force the request being handled by the datacenter in Dublin, change the API calls to go to the service endpoint directly, instead of the load balancer:
  • api-db4.microsofttranslator.com, instead of api.microsofttranslator.com.
  • db4 means Dublin Datacenter #4.
Important information:
  • Customized systems using the Microsoft Translator Hub and collaborative functions (CTF) are not available when calling the Dublin datacenter directly.
  • If you call the Dublin datacenter as described above, the call will be processed exclusively by the Dublin datacenter. If the Dublin datacenter is not available at the time, the call will fail. The call will not be redirected elsewhere. The metadata only, no content, will be transferred to and processed in the United States.

Last update September 12, 2017

Translator

  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