Microsoft Azure Translator Service spoke

Microsoft Azure Translator Service spoke provides subflows and actions to dynamically translate the user-entered texts, and to detect the language of the user-entered texts using the Microsoft translation service. Dynamic Translation supports detection and translation of single text 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.

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.
Translate Text [translate_text_v3]	Contains a set of inputs, actions, and outputs to translate the input text to multiple languages.

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 translation services and use them to dynamically translate your text.

1. Create a credential for the MicrosoftTranslation alias
   Authorize actions of Microsoft Azure Translator Service spoke by creating a credential for the MicrosoftTranslation connection and credential alias.
2. Create a connection for the MicrosoftTranslation alias
   Connect to the Microsoft translation service by creating a connection. Provide information that is used by HTTP(s) actions or activities to connect to that service.
3. Activate the Microsoft translator configuration
   Make the Microsoft translation service available for use by activating the Microsoft translator configuration.