Microsoft Azure Translator Service spoke

  • Release version: Xanadu
  • Updated January 9, 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 integrates Microsoft’s machine translation capabilities into ServiceNow, enabling detection and translation of user-entered text. It supports dynamic translation for both single and multiple text inputs, utilizing Microsoft Translator Text API versions v3 and v4. Activation requires enabling either the Dynamic Translation plugin or the Microsoft Azure Translator Service Spoke plugin.

    Show full answer Show less

    Key Features

    • Subflows: Pre-published subflows facilitate integration with Microsoft’s translation service, including language detection and text translation. The spoke supports both v3 and v4 API versions, with v4 flows used from Xanadu Patch 3 onward.
    • Actions: Provides discrete actions to detect the language of input text and to translate text into multiple languages, streamlining automation and workflow design.
    • IntegrationHub Aliases: Uses connection and credential aliases to manage Microsoft account credentials and connection information efficiently across environments, minimizing maintenance if credentials or connection details change.

    Practical Implementation

    • Microsoft Account Setup: Customers must register with Microsoft and obtain appropriate credentials to use the Translator Text API.
    • Connection Configuration: Create HTTP connection and credential records using the MicrosoftTranslation alias. The connection URL typically points to Microsoft’s cognitive services endpoint, but customers should verify their regional or custom API URLs in the Azure portal.
    • Activation: After configuring credentials and connection, activate the Microsoft translator configuration within ServiceNow to enable translation capabilities.

    What Customers Can Expect

    By leveraging this spoke, ServiceNow customers can seamlessly incorporate Microsoft’s translation services into their workflows and automation processes. This enables robust multilingual support, enhancing user experience and operational efficiency across global environments. The spoke’s design with subflows and actions allows flexible integration and reuse within broader ServiceNow flow designs.

    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.