Naming conventions are used to enforce a consistent naming strategy for teams created by end users in your organization. This helps in identifying the function of the team, membership, geographic region, or who created the team. It can also be helpful in categorizing teams and underlying groups in the address book.
Intrinsically, naming conventions are a combination of values and expressions that are evaluated against a user profile and a request form, which defines the final value of fields.
You can use available tags (see below) in each of these areas:
Team Name
Team Description
M365 Group email
Welcome message
Available tags
To get access to the tags, in the template settings under the tab "Name", at the "Naming Convention" level, simply type a letter and you'll get suggestions.
Request Form
here are all the available tags you can use from the user request form.
Tag | Description |
Request: Team Name | Requested team name |
Request: Team Description | Requested team description |
Request: Team Welcome Message | Requested team welcome message |
Request: Template Name | Requested template name |
Request: Requester Name | Requester name (Same as user.displayName) |
Request: Requester Email | Requester email (user.mail) |
User Profile (Entra ID / Asure Active Directory attributes)
Tag | Description |
User: Display Name | User full name. (for example "Bob Dirac") |
User: Principal Name | User UPN. In Active Directory, a User Principal Name (UPN) is the name of a system user in an email address format. A UPN (for example: "[email protected]") consists of the user name (logon name), separator (the @ symbol), and domain name (UPN suffix). ❗ A UPN is not the same as an email address. Sometimes, a UPN can match a user's email address, but this is not a general rule. |
User: Mail | User email (for example: "[email protected]") |
User: Preferred Language | User preferred language in Microsoft 365. Language and locale codes are limited to those in the ISO 639-1 standard. |
User: Given Name | User given name (for example: "Bob") |
Userc: Country | User country (for example: "France") |
User: Company Name | User company name (for example: "Contoso") |
User: Department | User department (for example: "Marketing") |
User: City | User city (for example: "Paris") |
User: Jobtitle | User job title (for example: "Product Manager") |
User: surname | User surname (for example: "Dirac") |
User: Usage Location | Office 365 usage location. (for example: "US") Rely on the ISO 3166-1 alpha-2 country codes... |
User: Preferred Data Location (PDL) | In case of a Multi Geo organization |
User: On-premises extension attribute | from 1 to 15, any extension attribute |
Examples
Fixed Naming Convention
"Add a "PRJ-" prefix to project management team with the name of the project
"Add a "-MKT" suffix to teams related to the marketing team"
Dynamic naming convention
"Add country as a suffix to teams names based on the requester location"
For team name:
For team description
Conditional naming convention
You may want to implement a conditional naming convention such as : if this user is from this department then put XYZ. This is totally possible, don't hesitate to reach the support for this, we'll help you build this.
<%= request.team.name %> -
<% if (user.mail.includes('@contoso.fr')) { %>
CT France // Use "CT France" instead of contoso.fr
<% } else { %>
<%= user.mail.replace(/.*@/, '') %> // Extract domain name from user email address
<% } %>