[Music] dynamic translation allows you to integrate a cloud-based translation service of your choice like ibm watson google cloud or microsoft azure the translator service spoke you set as the default translator will detect the language of the input text and translate it for your end users this can be done by configuring the correct credentials and connection aliases and activating them in dynamic translation logged in as system administrator we will set up the credentials and connections for one of these translator services if you haven't done so already install and activate the dynamic translation plugin on your instance as well as the translator service spoke you will be configuring both microsoft and ibm are available by default with the dynamic translation plugin google translator must be downloaded from the store app and installed before it can be integrated with the service provider next set up the translation alias here we see three aliases one for google cloud one for ibm translator and one for microsoft azure translator for this demo we will look at microsoft azure but the steps will be similar when setting up the other aliases to acquire the alias credentials for the microsoft azure translator we need to have an existing microsoft azure account here on the home page we navigate to cognitive services and search for translator which will give us the option to start a free account or buy a trial version once that is set up navigate to the reference page to find the base url and authentication key information related to your azure account this information will be needed for integrating the translator in your instance use the global url if you have a global account or the regional url if your account is region specific likewise use the subscription key as the password for setting up your translator service the region subscription key will be optional depending on which account you've purchased you can consult with your manager or microsoft admin to decide which is best for your instance back in dynamic translation click on microsoft translation to open up the application the connection is being saved in the microsoft azure translator service spoke but it's currently set up as a global application we can edit this record and create a new connection and credential you want to make sure you give a name that will be easy to identify when you add the credential api key make sure the right type of credential is being created in this case it's api key credential name the credential and add the api key after that is completed copy and paste the url link provided for microsoft translator in this field if you have procured the region subscription along with your microsoft account copy and paste that here after the credentials are set up activate the translator in your plugin navigate to translator configurations which will be added here in the navigator once dynamic translation is installed in your instance notice that microsoft ibm and google are not active by default when we click open microsoft we can configure the settings fields are set by default for the microsoft translator configuration select microsoft to make the translator available let's go ahead and make it our default translator to do this select default microsoft azure translation is now active and set as the default translator in your instance this is just one example of how you can integrate and activate any translation service provider in dynamic translation visit product documentation to learn more about configuring other translation service spokes for more information see our product documentation knowledge base or podcast or ask a question in the servicenow community you