Forum Discussion

Copper Contributor

Dec 21, 2020

Group naming policy enabled tenant - Not allowing to create 'Teams' through provisioned jobs

Hello All, Actually We have enabled 'Group Naming policy' on our O365 tenant like below: Current Policy: <Group name>(<Company>) It works perfectly fine when we create Teams through Teams Ap...

developer

microsoft teams

Manish-MSFT

Former Employee

Dec 22, 2020

SiddheshwarKohale , There are some strict guidelines that are to be followed when creating a group policy in azure active directory that enforces consistent naming conventions for Microsoft 365 groups created or edited by your users, set up a group naming policy for your organizations in Azure Active Directory (Azure AD).

I would suggest you to refer to your naming policies in your AAD and use the same to create a group using console job. As from your error it's clear that there is some format error in prefix and suffix.

Please follow this article for more details.

Also check if the data is already filled in object in code before creating a team

SiddheshwarKohale

Copper Contributor

Dec 31, 2020

Manish-MSFT - We are already using C# based console job to create Teams. Below are few more details:

Azure AD Group Policy:

Error Message:

Stack Trace:

UnifiedGroupInformation Payload is like this before creating Teams:

Code snippet:

Still we are facing similar issue. Please suggest possible solutions if any.

Thanks.

BR. Sid

Manish-MSFT
Former Employee
Jan 12, 2021
SiddheshwarKohale : We are looking into this issue, and will update you once I receive any update from internal developers team.
- SiddheshwarKohale
  Copper Contributor
  Jan 18, 2021
  Hello Manish,
  
  Thanks for taking this issue in your priority list. We are waiting for your reply on this.
  
  Thanks.
  BR. Sid
  - Manish-MSFT
    Former Employee
    Jan 18, 2021
    SiddheshwarKohale : Hi Sid, can we discuss this over a call? Please write to us microsoftteamsdev@microsoft.com