Heads up - regarding using Groups/Plans with multiple languages and notifications

Silver Contributor

If you have a Group and the default language is Portuguese, and you are in Planner using Portuguese language (pt-PT), then you switch over to another plan (while viewing the Portuguese language version fo Planner) and the other plan's default langauge is English (en-EN), and then you start making a bunch of updates, then all of the users will start receiving a bunch of emails in Portuguese.


Have a ticket with Premier right now, and we just figured out what is happening, (and why our users are starting to get bombarded with different language emails).


Planner doesn't respect Group-level language settings, it only cares about what language the current user happens to be using in the browser at that moment.


Additionally, the only way to change languages is to know what the language codes are and manually change them in the URL.


I'm not sure if Microsoft will view this as a bug or a "feature", but I certainly view it as a bug.

3 Replies
Another good example of inconsistency...and this is not only happening in Planner...but in Teams they have provided a way to choose your language for the UI....it could be great to have same concept in Planner and even in Groups
Disappointing answer from the product group (below), hopefully not just shrugged off:


This seems to be a by design behavior for now.

Planner does not seem to respect the language settings in the group. Planner sends emails in the language of the person who either posted the message or took the action that created the activity feed. The user’s email either comes from Office 365 via the suite navigation or if that isn’t present the browser setting.

• When we are on tasks.office.com page accessing the URL : https://tasks.office.com/PJONA.onmicrosoft.com/en-US/Home/ProjectsList/ or via groups or emails.
• We need to be careful of the language setting it is following by looking at the highlighted section in the url. Yes for now it is a manual method which can be a little difficult for end user however we are trying to make it better.
• If it does not have the correct language being set we should try and change it manually so that headers or notification emails formed are not in the wrong language for now.
• We are also trying to update an article which talks about the same thing.

Yeap, this is not the kind of answer I should expect from a Microsoft Product Group...it seems they have other priorities or simply it's not a priority to solve this kind of unexpected "by design" issues @Brian-Smith @Dave Heller