Can't provision new incident due to internal Group naming convention

[cll23]

Hi solution team, we have deployed the solution but only one user can provision new incidents. This user is Global admin, who provisions the solution. After reviewing relevant logs, we have found that our internal group naming convention required suffix for Teams group names. Therefore, when users can create SharePoint list items but eventually failed to provisioning Teams site. Is there a way to accept Teams naming convention policy? Any insights would be greatly appreciated!

[v-saikirang]

Hi @cll23, Thanks for reaching out to us.

Can you try customizing the Teams Name from Admin settings screen as shown below by changing the order and the modifying the "Prefix" value and see if it works for you:

Thanks.

[cll23]

Hi @cll23, Thanks for reaching out to us.

Can you try customizing the Teams Name from Admin settings screen as shown below by changing the order and the modifying the "Prefix" value and see if it works for you:

Thanks.

Hi v-saikirang,

Thank you for providing a possible workaround. Unfortunately we have tried that trick and doesn't work. Our group naming policy has a suffix from the creator's department, which is the problem.

Here is our policy:

Here is the error log from browser network activities.

I can see the attempts and deleted /sites/TEOC/Lists/TEOC-IncidentTransaction items in SharePoint list and no Teams site provisioning activities for users so that's what we think the problem is. Any other potential solution for this issue you can recommend is really appreciated! Thank you once again.

[v-saikirang]

Hi @cll23,

Unfortunately there is no other workaround for the policy in your tenant.

The only option is to customize the code from your end.

Thanks.

[cll23]

Hi @cll23,

Unfortunately there is no other workaround for the policy in your tenant.

The only option is to customize the code from your end.

Thanks.

Hi v-saikirang,

Thanks for your quick response. In this case, could you please provide some references about which part of the code recommended to customize for solving this issue? I have asked our developer to review but we are not familiar with this language so any additional documentations or guidance would be greatly appreciated. Thanks!

[v-saikirang]

Hi @cll23,

Customization would require hands on knowledge on teams app development, react and typescript. At this point we are also not sure what code changes are required as it requires some analysis and POCs. Unfortunately we will not be able to support custom versions.

Thanks.

[cll23]

Hi v-saikirang,

Thank you for taking the time to respond to my inquires and for keeping us informed about the situation. While it's not a supported scenario at the moment, hopefully the solution creators will consider this use case in the future release. Thanks again!