Forum Discussion

TH_'s avatar
TH_
Copper Contributor
Feb 11, 2022

Cannot create any groups - Naming policy

Hi,

Is anyone else experiencing this in their tenant? (I have checked three different tenants so far. Same issue in all of them. Northern Europe.)

We are currently unable to create any M365 groups with a group naming policy in place. Our policy applies a simple suffix string+attribute (department) and has been working fine for several years. Up until now.



The weird thing is that if one were to type in the actual attribute value (e.g. SomeRandomTeamName-Finance) .....it creates the group without any problem. But only if the current user actually belongs to that specific department. It doesn't work if one were to type another department they don't belong to in the AD. Oh yeah, we are syncing our premise AD, if that makes any difference. But I've seen it occur in pure Azure AD environments as well.

Is this a bug or what? Haven't seen anything about in the Health Center (as of right now at least anyway) :smile:

 

 

 

microsoft 365
  • VasilMichev's avatar
    VasilMichev
    MVP
    Feb 12, 2022
    Looks like a bug/issue to me, try creating the group from a different endpoint such as OWA. Or the M365 admin center, if you have sufficient permissions.
    • TH_'s avatar
      TH_
      Copper Contributor
      Feb 13, 2022
      An admin will always override the naming policy, so no issues there.
      But regardless of the service OWA, or client application used to create the group, nothing seems to work.