Some report that users are confused (after all, it’s a change in client behavior) while some like the opportunity to have their text checked. The Need for User CommunicationĮxperience with the feature is mixed. Some experiments show that after Teams detects that a conversation is in a specific language, it switches spell check to that language and displays the prompt. MC217362 says “ a user might see a compose notification UI letting them confirm/revert the switch.” The conditional tone of the statement means that it isn’t very clear as what will happen. Microsoft’s text is a little confusing about the prompt shown to users. As you can see, I’m asked “ are you writing in French now” (Figure 1).įigure 1: Teams concludes that it should switch to French for spell checking Teams monitors text as it is entered, and if the client detects enough instances of a specific language, it prompts to allow the user to confirm that the switch should continue. For instance, my PC is configured to use English, but sometimes I might need to chat with someone in French. Their PC is configured for a specific language and keyboard layout, which Teams uses to figure out the default language for spell checking. The idea is simple: users often switch languages to better communicate with co-workers. This change is documented as Microsoft 365 roadmap item 65446, which says “ Users who write different messages in different languages will now see spellchecking relevant to the language they use when typing a message in the Microsoft Teams desktop app.” It’s another step forward to making Teams an app that works well in international settings. Office 365 notification MC217362 of June 26 noted that language-aware spell checking would appear in the Teams Windows desktop client (but not for GCC tenants) with deployment to finish by the end of July. Multilingual Dexterity When Composing Teams Messages

Office 365 email spell check