Plan Site Naming Before a Department Rollout: Best Settings for Microsoft 365

When you roll out Microsoft 365 to a department, each new SharePoint site, team, and group must have a consistent name. Without a naming policy, users create sites with random names, duplicate names, or names that break your internal taxonomy. This causes confusion for search, navigation, and governance. This article explains how to configure the SharePoint site naming policy and the Microsoft 365 Groups naming policy before your department rollout. You will learn the exact settings to enforce a prefix, suffix, blocked words, and a consistent naming rule across all workloads.

Why You Must Set a Naming Policy Before a Department Rollout

A naming policy prevents users from creating sites with inconsistent or inappropriate names. Without a policy, a department rollout can produce sites named “Finance Team,” “FIN-team,” “Finance Dept,” and “Finance 2024.” This makes it impossible to find sites by search or to apply governance rules by name pattern.

The naming policy applies to all Microsoft 365 Groups, which means it covers SharePoint team sites, Microsoft Teams, Outlook groups, and Planner plans. A separate policy called the SharePoint site naming policy covers communication sites and team sites that are not connected to a group.

Both policies are enforced at creation time. If a user tries to create a site or group with a name that violates the policy, the system rejects the name and shows an error message. This eliminates the need for manual review of every new site.

Prerequisites for Configuring Site Naming Policies

Before you change any settings, confirm you have the correct permissions and licenses.

• You must be a Global Administrator or a Groups Administrator in Microsoft 365.
• You must have a Microsoft 365 license that includes Azure Active Directory P1 or P2. The naming policy is an Azure AD feature.
• You must have SharePoint admin access to configure the SharePoint site naming policy.
• Plan your naming convention before you enter the admin center. Decide on a prefix, suffix, and a list of blocked words.

Steps to Configure the Microsoft 365 Groups Naming Policy

This policy applies to all Microsoft 365 Groups, which includes SharePoint team sites connected to a group. Follow these steps to set a prefix, suffix, and blocked words.

1. Open the Microsoft 365 admin center
   Go to https://admin.microsoft.com and sign in with your admin account. In the left navigation, expand Teams & groups and select Active teams & groups.
2. Open the naming policy page
   At the top of the Active teams & groups page, click the Naming policy tab. This opens the Microsoft 365 Groups naming policy settings.
3. Add a prefix attribute
   Under Prefix-Suffix, click Add attribute. Choose an attribute from the dropdown, such as Department, Country, or Office. When a user creates a group, the system inserts the value of that attribute from the user’s Azure AD profile. For a department rollout, select Department so the group name starts with the user’s department name.
4. Add a suffix attribute
   Click Add attribute again and select a second attribute, such as Country or Office. The suffix appears at the end of the group name. If you do not want a suffix, skip this step.
5. Add a custom string prefix or suffix
   If you want a static text prefix like “PROJ-” or a suffix like “-GRP”, type the string in the Custom string field. You can combine custom strings with attributes. For example, set a custom prefix of “DEP-” and an attribute suffix of Department. The resulting group name is “DEP-Sales”.
6. Set blocked words
   Under Blocked words, type each word you want to block on a separate line. Block words like “Admin”, “CEO”, “HR”, or any term that should not appear in group names. Users cannot create a group that contains any blocked word.
7. Save the policy
   Click Save at the bottom of the page. The policy takes effect immediately for all new Microsoft 365 Groups. Existing groups are not affected.

Steps to Configure the SharePoint Site Naming Policy

The SharePoint site naming policy applies to communication sites and modern team sites that are not connected to a Microsoft 365 Group. This policy is separate from the Groups naming policy.

1. Open the SharePoint admin center
   Go to https://admin.microsoft.com/SharePoint and sign in with your SharePoint admin account.
2. Open site naming settings
   In the left navigation, click Policies, then click Site naming.
3. Enable the naming policy
   Toggle Use a naming policy for sites to On.
4. Set the prefix and suffix
   In the Prefix field, type a static string such as “SITE-” or “PROJ-“. In the Suffix field, type a static string such as “-2024” or “-PUBLIC”. You can also leave either field empty.
5. Set the default language
   Under Default language, select the language that appears in the site title by default. This setting does not change the site content language.
6. Save the policy
   Click Save. The policy applies to all new SharePoint sites that are not connected to a group.

If the Naming Policy Blocks a Legitimate Site Name

A naming policy that is too restrictive can block valid site names. For example, if you block the word “IT” but a department named Information Technology needs a site called “IT Help Desk”, the policy rejects it.

To fix this, review the blocked words list in the Microsoft 365 admin center and remove any terms that are needed for business operations. You can also add exceptions by using a custom string prefix that bypasses the blocked word check. For example, change the prefix to “PROJ-” so the site name is “PROJ-IT Help Desk” and the word “IT” is still blocked in other contexts.

When the Groups Naming Policy and SharePoint Naming Policy Conflict

If a user creates a SharePoint team site that is connected to a Microsoft 365 Group, the Groups naming policy takes precedence. The SharePoint site naming policy does not apply to group-connected sites. This can cause confusion if the two policies have different rules.

To avoid conflict, use the same prefix and suffix in both policies. For example, set the Groups naming policy to prefix “DEP-” and the SharePoint site naming policy to prefix “SITE-“. Users who create a group-connected site see “DEP-Sales” while users who create a communication site see “SITE-Sales”. This is acceptable as long as you document the difference for your users.

Item	Microsoft 365 Groups Naming Policy	SharePoint Site Naming Policy
Scope	All Microsoft 365 Groups, Teams, SharePoint team sites connected to a group, Outlook groups, Planner	Communication sites and modern team sites not connected to a group
Prefix options	Custom string or Azure AD attribute (Department, Country, Office, etc)	Custom string only
Suffix options	Custom string or Azure AD attribute	Custom string only
Blocked words	Yes, configurable list	No built-in blocked words
Enforcement time	At group creation	At site creation
Admin location	Microsoft 365 admin center > Teams & groups > Active teams & groups > Naming policy	SharePoint admin center > Policies > Site naming

Common Mistakes When Configuring Site Naming Policies

Using attributes that are empty in user profiles

If you set a prefix or suffix based on an Azure AD attribute like Department, and the user’s profile does not have a value for that attribute, the naming policy fails. The user sees an error and cannot create the group. To prevent this, populate the Department, Office, and Country attributes for all users before the rollout. Use Azure AD Connect or Microsoft 365 admin center to fill in missing values.

Blocking too many words

Blocking common words like “Team”, “Group”, “Project”, or “Site” can prevent users from creating sites with descriptive names. Only block words that are explicitly prohibited by your organization, such as offensive terms, executive names, or reserved terms like “Admin” or “CEO”.

Forgetting to communicate the policy to users

Users who try to create a site and see an error message without context may contact IT support. Send a brief email or create a SharePoint page that explains the naming rules. Include examples of valid and invalid names. This reduces support tickets during the rollout.

Conclusion

You can now configure both the Microsoft 365 Groups naming policy and the SharePoint site naming policy before your department rollout. The Groups naming policy applies to all Microsoft 365 Groups, Teams, and connected SharePoint sites. The SharePoint site naming policy applies to communication sites and standalone team sites. For a smooth rollout, populate user profile attributes, keep the blocked words list short, and communicate the rules to your users. As a next step, test the policy by creating a small number of sites in a test tenant before applying it to your production environment.