Microsoft Azure Translator Service spoke

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Microsoft Azure Translator Service Spoke

    The Microsoft Azure Translator Service Spoke enables users to detect and translate text using Microsoft’s machine translation service. It supports both single and multiple text translations through its Dynamic Translation capabilities. This spoke is available for ServiceNow customers with a Professional subscription or higher.

    Show full answer Show less

    Key Features

    • Subflows:
      • Detect Language [detectlanguagev3]: Detects the language of input text using v3 flows.
      • Detect Language V4 [detectlanguagev4]: Detects language with v4 flows, applicable for releases after Xanadu Patch 3.
      • Translate Text [translatetextv3]: Translates input text to multiple languages using v3 for both pre- and post-Xanadu Patch 3.
    • Actions:
      • Detect Language [detectlanguagev3]: Identifies the language of the provided text.
      • Translate Text [translatetextv3]: Converts the provided text into various languages.

    Connection and Credential Management

    To utilize the Microsoft Azure Translator Service, customers must have a registered Microsoft account and obtain necessary credentials. IntegrationHub simplifies connection management through the use of aliases, which allows for streamlined configuration across multiple environments.

    • Connection Alias: The spoke uses the alias MicrosoftTranslation to authorize actions.
    • Connection Requirements:
      • Connection type: HTTP
      • Connection URL: Typically https://api.cognitive.microsofttranslator.com, but may vary based on customer setup.

    Next Steps

    To connect to the Microsoft machine translation service, follow these steps:

    • Create a credential for the MicrosoftTranslation alias.
    • Create a connection for the MicrosoftTranslation alias.
    • Activate the Microsoft translator configuration to enable its usage.

    Microsoft Azure Translator Service spoke provides subflows and actions to detect and translate user-entered text, using the Microsoft machine translation service. Dynamic Translation supports detection and translation of single texts and multiple texts.

    Activation

    Activate the Dynamic Translation plugin (com.glide.dynamic_translation) or the Microsoft Azure Translator Service Spoke plugin (com.glide.microsoft_translation_spoke).

    Subscription

    This spoke requires any ServiceNow subscription that is Professional or above, and includes Dynamic Translation.

    Supported versions

    API version v3 and v4.

    Spoke subflows

    The spoke provides subflows in the Published state to integrate with Microsoft translation service. These subflows can be used as part of other subflows and flows.

    Table 1. Spoke subflows
    Subflow Description
    Detect Language [detect_language_v3] Contains a set of inputs, actions, and output to detect the language of the input text. Releases before Xanadu Patch 3 use v3 flows.
    Detect Language V4 [detect_language_v4] Contains a set of inputs, actions, and output to detect the language of the input text. Releases from Xanadu Patch 3 use v4 flows. For more information about v4 flows, see Migrate customized Translator Configurations to v4 flows.
    Translate Text [translate_text_v3] Contains a set of inputs, actions, and outputs to translate the input text to multiple languages. This subflow uses v3 for releases before and after Xanadu Patch 3.

    Spoke actions

    The spoke provides actions to integrate with Microsoft translation services.

    Table 2. Spoke actions
    Action Description
    Detect Language [detect_language_v3] Detects the language of the input text.
    Translate Text [translate_text_v3] Translates the input text to multiple languages.

    Microsoft account requirements

    Ensure that you are registered with Microsoft and obtain the credential information. For more information, see Microsoft documentation.

    For information on Microsoft Translator Text API, see the Microsoft documentation.

    Connection and credential alias requirements

    IntegrationHub uses aliases to manage connection and credential information. Using an alias eliminates the need to configure multiple credentials and connection information profiles when using multiple environments. If the connection or credential information changes, you do not need to update any actions that use the connection. For more information, see Credentials and connection information.

    To use the spoke connection aliases, create an associated connection record and a credential record for each alias.

    This spoke uses the MicrosoftTranslation alias (sn_ms_trans_spoke.MicrosoftTranslation) to authorize actions.

    The following are the connection alias requirements.
    • Connection type: HTTP
    • Connection URL: For example, https://api.cognitive.microsofttranslator.com.
      Note:
      The URL provided here is a sample only. Microsoft translation customers may need to use custom API URLs or virtual network type API URLs, even when they do not subscribe to a virtual network. Microsoft customers who use multi-service or regional translation services also need to know their Ocp-Apim-Subscription-Region attribute, and their API URL may contain a regional reference. Check your Azure portal for this information. Refer to the Microsoft documentation for further details.

    Perform the following tasks to connect to the Microsoft machine translation service.