New Teams client suddenly not allowing specific characters from M365 Group naming policy

[ajc196]

Since we deployed Teams a few years ago, we have had an M365 Group naming policy that appends " (UserCreated)" as a suffix for anything created by an end user/non-admin. There have been no changes since. Starting a few days ago, we got reports that users were getting an error of The team prefix or suffix is incorrect, please try again whenever creating a new team.

After testing myself and reproducing the problem what I found is that if you're using the v2 client ("new" Teams on Windows/macOS, or https://teams.microsoft.com/v2 for the web client), it kicks back with the above error. If using a classic/v1 desktop client or the non-updated web client, the issue is not reproducible.

v2 client + no parentheses in naming policy = SUCCESS - https://imgur.com/a/fun0klN

v2 client + parentheses in naming policy = FAILURE - https://imgur.com/a/ZeADI6E

v1 client + parentheses in naming policy = SUCCESS - https://imgur.com/a/jYae7l8

Currently unaware if this is a bug or new behavior that went unannounced, but there's at least a few other recent complaints of the same out in the community.

https://answers.microsoft.com/en-us/msteams/forum/all/naming-teams/ebb29b25-20df-4642-8fcf-ffc67896e...

[#2]

No one else seeing this? Still very reproducible for us, and there's no mention of parentheses not being supported in a Group naming policy so far as Teams is concerned.

https://learn.microsoft.com/en-us/microsoft-365/solutions/groups-naming-policy?view=o365-worldwide#t...

[#3]

***** The team prefix or suffix is incorrect, please try again***

having the same issue with some being unable to create new teams. The user was able to create a new team using the old UI - I can create new teams in either the new teams or the old.

[#4]

We can confirm the same behavior and hope very much for a solution.

[#5]

@ajc196 This is a bug on the New Teams client. Microsoft is working on the bug right now and the fix deployment can take several weeks to be fully deployed to Public/General ring, as there are some code freezes on these dates and release process is considerably slower than usual due to the Holidays.

[#6]

Same issue within out (education) tenant, is there any official topic / post about this current bug being recognized by Microsoft?

[#7]

Microsoft support confirmed the bug this morning through our support ticket. The anticipated fix is expected in February.

[#8]

Well that's embarrassing for Microsoft. "Teams" can't make a (checks notes) team. Leaving it that way for almost 2 months is acceptable?

[#9]

And what makes it worse in my humble opinion is the fact that it isn't on the list of known issues found here: https://learn.microsoft.com/en-us/microsoftteams/new-teams-known-issues

[#10]

Still an issue.

Respectfully, Microsoft needs to expedite this fix. Because right now, we have to do one of the following:

1) Undo our M365 Group naming policy and blow up expected logic for way more M365 services than just Teams.

2) Leave users unable to create teams in Teams, and hope they reach out to us. Since we are a university with a user count in the 5-figures, this is a very bad option.

[#11]

Anything new on this issue? Can't find that much news related to this. We couldn't figure out what the main reason is.
Not using parentheses in GorupNamingPolicy, still not working.

[#12]

Is there any new information?
A customer of ours has exactly this problem while using the attribute "department" for their group naming policy

[#13]

We're well into February with no fix, and there's still never been an advisory or incident in the M365 message center for this. So I'm a little dubious about the statement of Microsoft's awareness higher up in this thread.

[#14]

The issue seems to be resolved for our Tenant. Mind you, the entirety of February I have not tested if it is possible to create new Teams yet (using Teams 2.0).

I just now created a new Teams with the Teams 2.0 Desktop client.

I have not tested the web version of Teams 2.0