RSS – PostsMicrosoft announced at Inspire this week the release of message translation of chat messages to the recipient’s native tongue.
In order to use this feature, administrators must enable this on your tenant. You can do this using the Messaging Policy. As yet this option does not appear in the Teams Admin Portal, but you can use (SfBO) PowerShell to enable it.
In my example, I am turning this on for the global policy
Set-CsTeamsMessagingPolicy -Identity Global -AllowUserTranslation $true
The policy takes a few minutes to apply, users may be required to log out and back into Teams.Now when a user types in a message the recipients have the option to translate. You can do this by clicking the elypsis on the message and clicking Translate Message
If the language is supported then the translation will work like so:
You’ll notice a little icon appear next to the time on a translated message. If you want to revert the translation, go to the elypsis again and click see original message
Teams automatically translates to the language set for the user in their Teams client. To change this go into the user settings and change the language as needed
Mark is an Independent Microsoft Teams Consultant with over 15 years experience in Microsoft Technology. Mark is the founder of Commsverse, a dedicated Microsoft Teams conference and former MVP. You can follow him on twitter @UnifiedVale
I updated Powershell on my Win7 to the latest version, installed SkypeOnlinePowershell, but the Import-Module skypeonlineconnector allways failes with : The specified module ‘skypeonlineconnector’ was not loaded because no valid module file was found in any module directory. I googled a lot, but found no solution. Any hint ?
Hi, You shouldn’t need to manually load the module once installed. Have you tried just typing in
$session = New-CsOnlineSession -Credential (Get-Credential)?[…] https://blog.valeconsulting.co.uk/2018/07/18/microsoft-teams-adds-message-translation-here-is-how-yo… […]
[…] Mark has done a great post on how to enable this here: https://blog.valeconsulting.co.uk/2018/07/18/microsoft-teams-adds-message-translation-here-is-how-yo… […]
Hi Mark, great blogging about Teams lately. Looking into this command from my Teams powershell Set-CsTeamsMessagingPolicy -Identity Global -AllowUserTranslation $true The Identity is not an parameter yet in Norway from what i can see, but GroupID is, and what is the groupID?
Hi
I’m not sure why you don’t have identity. Perhaps try doing a get and pipe it into set? The feature is GA so it should be standardised
works nice now
[…] https://blog.valeconsulting.co.uk/2018/07/18/microsoft-teams-adds-message-translation-here-is-how-yo… […]
i get this error.
Set-CsTeamsMessagingPolicy : The term ‘Set-CsTeamsMessagingPolicy’ is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ Set-CsTeamsMessagingPolicy -Identity Global -AllowUserTranslation $tr …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Set-CsTeamsMessagingPolicy:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
Hi
Are you running this in Skype for Business Online PowerShell?
My command works fine
Thanks worked great for me, tested with our China team last night.
Now to figure out how to script the Teams language setting so we can push it out for the users not expecting them to go in and change it 🙂