--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # Microsoft Azure OEM for Dynamic Translation in Now Assist # Microsoft Azure OEM for Dynamic Translation in Now Assist {#ariaid-title1} Release version: Australia Updated July 31, 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 OEM for Dynamic Translation in Now Assist The Microsoft Azure OEM translator service, included with the Generative AI Controller, enables multi-language input support for Now Assist applications by dynamically translating user inputs and responses. This service detects the input language, translates it to English for processing by Now Assist, and then translates the English response back to the user's preferred language for display. Show full answer Show less ## Key Features * **Dynamic Translation Workflow:** User input is auto-detected, translated to English, processed by Now Assist, and the English response is translated back to the user's language. * **Automatic Activation:** Microsoft Azure OEM requires Dynamic Translation tables and will activate Dynamic Translation within Generative AI Controller if not already active. * **Pre-configured and Non-editable:** The Microsoft Azure OEM translator configuration appears as a non-editable record in the Translator Configurations table with connection credentials pre-configured for immediate use. * **Regulated Market Support:** From the Zurich release, support for specific regulated markets is available under certain conditions. * **Integration Updates:** With Xanadu Patch 3, support for the Exclusion Framework in Dynamic Translation is added and the translation API is updated to v4. * **Supported Languages:** Supports all ServiceNow platform language packs except I18N: Latin American Spanish Translations; self-localized languages are not supported. ## Customization and Alternatives * You can replace Microsoft Azure OEM with another machine translation service by configuring your preferred provider within Generative AI Controller. * To switch providers, create and configure the new translation service, copy its sysid, and set it via a system property to override the default Microsoft Azure OEM translator. * Alternatively, Dynamic Translation can be disabled in this context through a system property if translation is not desired. ## Practical Considerations for ServiceNow Customers * This integration facilitates seamless multilingual interaction within Now Assist applications, improving user experience across different languages. * Activation and setup are streamlined since the Microsoft Azure OEM translator is included and pre-configured with Generative AI Controller. * Customers in regulated markets should review specific conditions to ensure compliance. * For customers wishing to use a different translation provider, ServiceNow provides clear configuration steps to customize or disable the translation service. Support multi-language input in Now Assist applications with the Microsoft Azure OEM translator service included in Generative AI Controller. ## Multi-language support for Now Assist applications {#dynamic-translation-na-ms-azure-oem__section_dj1_l3q_4bc} When dynamic translation in the Generative AI Controller is enabled, your users' input text is handled by Microsoft Azure OEM (com.snc.microsoft_oem_translation_spoke) as follows: 1. The language of the text is detected. 2. The text is dynamically translated to English, then provided to Now Assist. 3. Now Assist returns a response in English. 4. The English response is translated to the user's preferred language and displayed in the UI. {#dynamic-translation-na-ms-azure-oem__ol_yf2_s2r_4bc} For more information about enabling dynamic translation in this context, see [Configure multilingual service for ServiceNow Otto applications](https://www.servicenow.com/docs/rRNqxEDtHIMEoVbC8eThBg "Turn on multilingual service for user-entered text with native translation or Dynamic Translation in ServiceNow Otto applications.") and [Enable Dynamic Translation for capabilities in Generative AI Controller](https://www.servicenow.com/docs/IujUmkowTtk74ISGVtlYAQ "Use Dynamic Translation to add multiple language support for generative AI capabilities to support users who speak languages other than English."). From the Zurich release, this spoke has available support for specific regulated markets, subject to conditions. For information see [KB0743854](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0743854) on the Now Support portal. ## Activation {#dynamic-translation-na-ms-azure-oem__section_h1s_vfr_4bc} The Microsoft Azure OEM translator service is included with Generative AI Controller. Microsoft Azure OEM requires Dynamic Translation tables, so Generative AI Controller activates Dynamic Translation if it isn't already active. Microsoft Azure OEM appears as a row in the Translator Configurations (sn_dt_translator_configuration) table. This record is not editable. The connection credentials of this translator service are already configured. For more information about this integration, see . If you try to update this record in the Translator Configurations table, the following error is displayed: "The Microsoft Azure OEM translator configuration is used in Generative AI flows. It cannot be edited". With the Xanadu Patch 3 release, the Microsoft Azure OEM translator includes support for [Exclusion Framework in Dynamic Translation](https://www.servicenow.com/docs/access?context=dyn-translation-exclusion-framework&version=australia&pubname=australia-platform-administration&ft:locale=en-US). Also the API used by flows and subflows is automatically updated to v4. The application scope for Microsoft Azure OEM is sn_ms_oem. For more information, see [Dynamic Translation](https://www.servicenow.com/docs/access?context=dynamic-translation-overview&version=australia&pubname=australia-platform-administration&ft:locale=en-US). ## Languages supported {#dynamic-translation-na-ms-azure-oem__section_h3n_zh2_ckc} The Microsoft Azure OEM service supports all of the languages available as language packs on the ServiceNow platform, except I18N: Latin American Spanish Translations. Self-localized languages (languages other than the default language packs) aren't supported. For the list of available language packs, see [Activate a language](https://www.servicenow.com/docs/access?context=t_ActivateALanguage&version=australia&pubname=australia-platform-administration&ft:locale=en-US). ## Alteration or deactivation {#dynamic-translation-na-ms-azure-oem__section_bxn_jmk_2jc} You can use a different machine translation service in Generative AI Controller, rather than the provided Microsoft Azure OEM translator configuration. If you want to switch to a translation service provider of your choice, you can update a system property as follows. 1. With the admin role, create an account with a third-party machine translation service provider and configure it in your instance. For details see [Integration with other translation services](https://www.servicenow.com/docs/access?context=integration-with-other-translation-services&version=australia&pubname=australia-platform-administration&ft:locale=en-US). 2. Open the record for your translation service provider by navigating to the Translator Configurations \[sn_dt_translator_configuration\] table, then selecting the appropriate row. 3. Copy the sys id of the record by opening the form context menu ![]() and selecting Copy sys_id. 4. Navigate to the sys_properties table and select New to create a system property. 5. Enter values in the System Property - New record form as follows.{#dynamic-translation-na-ms-azure-oem__table_k3p_wmn_fjc__entry__2} | Field | Value | |-|-| | Name | com.snc.gen_ai.translator_configuration.sys_id | | Value | Enter the translator configuration sys id that you copied in the previous step. | [Table 1. System Property - New record form] {#dynamic-translation-na-ms-azure-oem__table_k3p_wmn_fjc} 6. Select Submit. Alternatively, you can deactivate Dynamic Translation in this context using another sys property. For information see [Disable Dynamic Translation for LLM Virtual Agent conversations](https://www.servicenow.com/docs/1G4VQK0B0h9ZxH29nHCMTg "Enable dynamic translation of chat messages into English before they are sent to the large language model in generative AI topics to support users who speak other languages."). **Related concepts** * [Multilingual service for Now Assist](https://www.servicenow.com/docs/7AoBkgcn1QjvpMq6GsOFQw "Now Assist applications use the multilingual capabilities of large language models (LLMs) to translate user-generated content.") **Related reference** * [Generative AI Controller](https://www.servicenow.com/docs/QiWnE6U8Q1Zhlhb1IOImwA "Use Generative AI Controller to integrate your ServiceNow applications with third-party large language models (LLMs) and manage how generative AI requests are governed, protected, and logged.") **Related topics** * [Dynamic Translation](https://www.servicenow.com/docs/access?context=dynamic-translation-overview&version=australia&pubname=australia-platform-administration&ft:locale=en-US)