Built for business, Microsoft Translator is a proven, customizable, and scalable solution for automatic translation. Microsoft Translator’s cloud-based APIs can help make your business or app competitive in an increasingly globalized business environment.

We appreciate feedback and use it to guide our product direction, thanks to you!

Ideas and feedback -

Use this forum to give feedback or share your ideas on how we can improve Microsoft Translator:
• Speech API
• Text API
• Translator Hub

The list of languages offered can be found here:
If you have a suggestion for a new language or language feature please go to: How do I get my language supported?

Support -

• For free technical support go to Stack Overflow
• For free Azure subscription and billing support go to Azure and select “Support” from the menu bar.
• For all other questions click “Contact us” to the right of this page.

To learn more about getting a subscription to Microsoft Translator through the Azure portal go to Translator getting started.

For support with the Microsoft Translator apps for Windows, iOS, and Android; the Microsoft Translator Edge extension;; or other consumer products please go to Microsoft Translator support.

How can we improve Translator?


Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 1008 - Too many binary messages.

    in some case we are getting 1008 error code on websocket.

    in the documentation (, there are some error codes, like 1001, 1011, but not 1008.

    it seems for us that Azure closes the websocket connection, with this error code, in certain cases. the question is why this happens?


    2 votes
    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)

      We’ll send you updates on this idea

      1 comment  ·  API - Speech Translation  ·  Flag idea as inappropriate…  ·  Admin →

      Translator closes the websocket connection after a period of inactivity. You will want to silently recreate the websocket connection when you receive this error.

      That is generally a good thing, because you won’t be charged for the time the connection is not open.

      The docs could be better in documenting the techniques for keeping the connection alive and the associated messaging. I’ll see to making that happen.

      Chris Wendt
      Microsoft Translator

    • Don't see your idea?

    Feedback and Knowledge Base