Microsoft Azure Translator Service spoke

  • Release version: Yokohama
  • Updated January 30, 2025
  • 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 in ServiceNow enables detection and translation of user-entered text through Microsoft’s machine translation service. It supports dynamic translation for both single and multiple texts, facilitating multilingual communication within your workflows.

    Show full answer Show less

    To use this spoke, activate either the Dynamic Translation plugin (com.glide.dynamictranslation) or the Microsoft Azure Translator Service Spoke plugin (com.glide.microsofttranslationspoke). The spoke requires a Professional or higher ServiceNow subscription that includes Dynamic Translation capabilities.

    It supports API versions v3 and v4, with v4 available from Xanadu Patch 3 onwards.

    Key Features

    • Spoke Subflows: Pre-built subflows in Published state enable seamless integration with Microsoft Translator services:
      • Detect Language (v3 and v4): Identify the language of input text, with v4 recommended for Xanadu Patch 3 and later releases.
      • Translate Text (v3): Translate input text into multiple target languages.
    • Spoke Actions: Actions to detect language and translate text, allowing these operations to be embedded in custom flows.
    • Connection and Credential Management: Uses IntegrationHub aliases (MicrosoftTranslation alias) to manage connection and credential information efficiently across environments, minimizing maintenance when updates occur.

    Practical Setup and Requirements

    • Microsoft Account: You must register with Microsoft and obtain the necessary credentials to access the Translator Text API.
    • Connection Setup: Create a credential and connection record for the MicrosoftTranslation alias within ServiceNow. The connection typically uses an HTTP connection type with a URL similar to https://api.cognitive.microsofttranslator.com. Note that your API URL and region information may vary based on your Azure subscription and deployment, so verify details in your Azure portal.
    • Activation: After configuring the connection and credentials, activate the Microsoft translator configuration in ServiceNow to enable translation functionality.

    Benefits for ServiceNow Customers

    • Quickly integrate Microsoft’s robust translation capabilities into your ServiceNow workflows to support global audiences.
    • Use standardized subflows and actions to streamline language detection and translation without custom development.
    • Maintain flexible and maintainable integration via credential and connection aliases, simplifying management across multiple environments.
    • Leverage up-to-date API versions to ensure compatibility and access to enhanced translation features.

    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.