Office 365 Groups with IDN e-mail addresess

[Kazzan]

When the user starts creating new Office 365 Group (Microsoft Teams/Yammer) and he chooses international display name of this group in Yammer or Teams app, the group e-mail address is created in international IDN format.

For example, we are in Czech and user choose "Žlutí koníci", it does not offer creating "zluti-konici@tenant" like that, but it create "xn--lutkonci-e2ad10n@tenant" which is not really usable address for external members and to write down and some clients does not support IDN yet.

We can renemae the group, but users creating this and it starts broking naming convention. Is there some option to disable creating names and e-mail address in IDN format for Groups/Teams?

[#2]

This a really great question and I would like to know also the answer because some Spanish caracters and I can think in german ones could fall under the same situation....maybe @TonyRedmond can help here

[#3]

More of an issue for @cfiessinger @Krish Gali to address. Exchange Online doesnt yet support full internationalization afaik, which is probably part of the problem.

[#4]

I have no act or part to play here. Microsoft owns this issue. The long-term solution is to provide better control over the email addresses generated by Groups. The short-term solution is to assign new email addresses to the groups after they are created. This is easily done with Set-UnifiedGroup -PrimarySMTPAddress.

[#5]

Looking at this a little more, I see that I cannot use Žlutí koníci for a group name in my tenant, probably because I don't use Czech for the admin language. The validation for the group identifier (alias) field is probably where the problem lies. If the form highlighted the need to use basic latin characters, the admin would know immediately that they have a problem with the name and can then adjust the identifier as they wish to create a nice email address. Unless I have misunderstood the issue?

[#6]

The issue occur, when the Office 365 Group is created by user in Office 365. Not in Admin Center by admin.

If user choose OWA to creating this, it does not allow special characters. If he/she choose Teams, it translate somehow the characters to Group name. If he/she choose Yammer to create connected Groups, it create the Group with IDN translated form which is wrong for Exchange (mails) and so.

With using IDN, internal mails are working inside Outlook, but external or some connections does not work correctly. We can fix such names with PowerShell and Office 365 Admin Center. But users keep with Czech characters in names, so they creating new Groups wrongly. We tell them, but you know. Users. 😉 We fixing names regularly, but more granular and working integration for naming policies or to restrict this characters will be fine.

[#7]

Hi Petr,

Just to double-check (no pun intended):

Groups created withthe Office 365 Admin Center are OK.

Groups created with OWA are OK (I assume Outlook too)

Groups created with Yammer are not OK (permit local characters in the name and generate IDN email addresses).

Did I get that right? I'm just trying to understand the full extent of the problem.

TR

[#8]

Groups created with the Office 365 Admin Center are OK - Yes, because they do not allow such characters and admin must fix it.
Groups created with OWA are OK (I assume Outlook too) - Yes, they truncate the characters which they do not support and offer the different name or let fix on the user.
Groups created with Yammer are not OK (permit local characters in the name and generate IDN email addresses). - Yes, Yammer and Teams allow creatin with IDN.

As far as tested in our and customer tenant.

[#9]

Right. I see the same results. So, the problem is with Teams and Yammer.  I'm sure the Microsoft folks will follow up.

TR