Naming Conventions

[alexc-MSFT]

Summary With this release the app template will have the ability to define multiple conventions at the global level (apply to all Teams) and at the template level.

The global level will work in the same way that the out of the box Azure AD group naming policy works.

The template level will allow you to define a specific naming convention per teams template that you create. You can also create templates using the 'standard' template with no additional content, this way you can effectively define 'types' of teams and apply a unique naming convention.

Intended Outcome To be able to define multiple naming conventions for Teams created through the Request-a-team app template.

How will it work You will be able to define a single global naming convention for all created Teams e.g. GRP_Purchasing_Contoso. Where 'GRP' is the Prefix, 'Purchasing' is the team name and 'Contoso' is the company AND a template level convention.

There will be the ability to use the following user attributes for the Prefix and/or Suffix:

• Department
• Company
• Office
• StateOrProvince
• CountryOrRegion
• JobTitle

Text can also be used in combination with these attributes to achieve a naming convention similar to the above.

Global naming conventions will be defined in the 'Team Request Settings' list.

Template naming conventions will be defined in the 'Teams Templates' list.

[garrytrinder]

I see support for naming conventions as a high value feature for customers, this is regularly requested by customers that I have demonstrated this solution to.

[technomensch]

@alexc-MSFT , I see that you moved this into "Completed".

Where is the documentation on how to implement/leverage this feature? I cannot find "prefix" anywhere in the Deployment Guide?

Is it possible to customize these prefixes to leverage our own SharePoint lists as opposed to Active Directory?

Thank you in advance.