---
sourceDocument: Brazil ServiceNow AI Platform Administration
sourceDocumentLink: https://www.servicenow.com/docs/r/platform-administration

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Microsoft Azure Translator Service spoke

# Microsoft Azure Translator Service spoke {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 users to detect and translate text dynamically.
It supports both single and multiple text translations and requires activation of the Dynamic Translation plugin or the Microsoft Azure Translator Service Spoke plugin.
This feature is available to customers with ServiceNow subscriptions at the Professional level or above.
Show full answer Show less  

## Key Features

* **Subflows:** Pre-built, published subflows allow detection of input text language and translation into multiple languages. Two versions support API v3 and v4, accommodating different release versions of ServiceNow.
* **Actions:** The spoke provides specific actions---Detect Language and Translate Text---to integrate translation capabilities within custom workflows and automation.
* **Connection and Credential Management:** Uses IntegrationHub aliases to manage Microsoft connection and credential information efficiently across environments, reducing maintenance and configuration overhead.
* **Microsoft Account Requirements:** A registered Microsoft account with appropriate credentials is necessary to use the translation services. Customers should refer to Microsoft's documentation for API details and account setup.

## Practical Implementation

To enable the Microsoft Azure Translator Service spoke, customers must:

* Activate the related plugin (Dynamic Translation or Microsoft Azure Translator Service Spoke).
* Create and configure a credential record for the MicrosoftTranslation alias to authorize actions.
* Create an HTTP connection record for the MicrosoftTranslation alias, using the correct Microsoft API URL, which may vary based on region or network setup.
* Activate the Microsoft translator configuration within ServiceNow to make the translation services available for use.

## What Customers Can Expect

Once set up, customers can incorporate automated language detection and translation into their ServiceNow flows and subflows. This enables enhanced multilingual support for end users and automation scenarios, improving communication and operational efficiency across language barriers.  
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 {#microsoft-translation-spoke__section_vmm_knr_h1c}

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

## Subscription {#microsoft-translation-spoke__section_swc_v2t_3jb}

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

## Supported versions {#microsoft-translation-spoke__section_gbp_mrt_shb}

API version v3 and v4.

## Spoke subflows {#microsoft-translation-spoke__section_ylg_4rt_shb}

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.
{#microsoft-translation-spoke__table_krq_5rt_shb__entry__2}

| 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](https://www.servicenow.com/docs/mtweVFfuzyHUk1E1XN8MFw "Migrate your customized translator configurations to v4 flows. Version 4 flows for Dynamic Translation are available from the Xanadu Patch 3 release."). |
| 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. |
[Table 1. Spoke subflows]

{#microsoft-translation-spoke__table_krq_5rt_shb}

## Spoke actions {#microsoft-translation-spoke__section_uv5_prt_shb}

The spoke provides actions to integrate with Microsoft translation
services.
{#microsoft-translation-spoke__table_jd2_lst_shb__entry__2}

| 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. |
[Table 2. Spoke actions]

{#microsoft-translation-spoke__table_jd2_lst_shb}

## Microsoft account requirements {#microsoft-translation-spoke__section_v4d_dvt_shb}

Ensure that you are registered with Microsoft and obtain the credential information. For more
information, see [Microsoft](https://docs.microsoft.com/en-in/) documentation.

For information on Microsoft Translator Text API, see the [Microsoft](https://docs.microsoft.com/en-us/azure/cognitive-services/translator/) documentation.

## Connection and credential alias requirements {#microsoft-translation-spoke__section_pcy_f5t_shb}

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](https://www.servicenow.com/docs/access?context=r-credentials&version=brazil&pubname=brazil-platform-security&ft:locale=en-US).

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](https://learn.microsoft.com/en-us/azure/ai-services/translator/reference/v3-0-reference) documentation for further details.
{#microsoft-translation-spoke__ul_ivv_kjt_msb} Perform the following tasks to connect to the Microsoft machine translation service.
1. [Create a credential for the MicrosoftTranslation alias](https://www.servicenow.com/docs/E0BHKFiv317p0HSIOL32hw)  
   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](https://www.servicenow.com/docs/vO4tSmTn~1OzK8zg4phW7A)  
   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](https://www.servicenow.com/docs/h4nkbpPPF_ffVm3c_t3o0g)  
   Make the Microsoft translation service available for use by activating the Microsoft translator configuration.