Microsoft 365 Group Naming Policy

What Is It?

A Group Naming Policy ensures all Microsoft 365 groups follow a consistent, structured naming convention.

✅ Helps:

• Identify group purpose (e.g., Sales, HR).

• Locate groups in the address book (GAL) and across workloads (Teams, Outlook, Yammer, SharePoint).

• Prevent inappropriate/confusing group names.

⚠️ Scope:

• Applies only to Microsoft 365 Groups.

• ❌ Does not apply to Distribution Groups (DGs) in Exchange Online (those have their own naming policy).

---

📦 Features of the Naming Policy

1. Prefix-Suffix Naming

• Define rules to add text before/after the group name.

• Can be:

  • Fixed strings → always added, e.g., "GRP_", "_US".

  • User attributes → auto-filled based on creator’s attributes.

✅ Example:
Policy = "GRP [GroupName] [Department]"

• User’s Department = Engineering

• Group created as = "GRP MyTeam Engineering"

Supported attributes:

• [Department]

• [Company]

• [Office]

• [StateOrProvince]

• [CountryOrRegion]

• [Title]

⚠️ Notes:

• Unsupported attributes (like [postalCode]) are treated as plain text.

• Don’t use very long values → may hit name length limits.

---

2. Custom Blocked Words

• Upload a list of restricted words (max 5,000).

• Case-insensitive, exact matches only.

• Prevents sensitive/confusing names.

✅ Example: Block words → CEO, Payroll, HR.

• User tries "Payroll Team" → ❌ rejected.

---

3. Administrator Override

Some roles can bypass the policy:

• Global Administrator

• Partner Tier 1/2 Support

• User Account Administrator

---

🧾 Licensing Requirement

• Requires Microsoft Entra Premium P1 OR Microsoft Entra Basic EDU.

• Must be licensed for each user and guest in a group.

• Licenses don’t need to be directly assigned, but must exist in tenant.

---

🛠️ Setup Steps (Entra Admin Center)

1. Go to Microsoft 365 Admin Center → Identity.

2. In Microsoft Entra Admin Center:

   • Navigate → Groups → Group Settings.

   • Select Naming Policy.

3. Configure:

   • Prefix/Suffix (choose Attribute or String).

   • Blocked Words list.

4. Save.

---

📏 Rules & Considerations

• Total prefix+suffix length ≤ 53 chars.

• Group max length = 264 chars.

• Allowed special chars: ., -, _

• ❌ Yammer restrictions: avoid @, #, [, ], <, >.

• If illegal chars exist in alias → applied only to display name.

---

✅ Best Practices

• Use short suffixes/prefixes.

• Use attributes with values (don’t pick attributes blank for many users).

• Upload blocked words (protect brand image, prevent misuse).

• Don’t make naming conventions overly complex.

---

🔍 Example Policies

Policy 1: Department-based suffix

[GroupName]_[Department]

→ MarketingTeam_Sales

Policy 2: Location prefix + creator’s title suffix

[CountryOrRegion]_[GroupName]_[Title]

→ US_ProjectAlpha_Manager

Policy 3: Fixed + Attribute Mix

GRP_[GroupName]_[Office]

→ GRP_DesignTeam_London

---

📝 Exam/Interview Triggers

• Q: Does it apply to Distribution Groups?
  → ❌ No, DGs need their own policy.

• Q: Which attributes can be used?
  → Only built-ins: Department, Company, Office, StateOrProvince, CountryOrRegion, Title.

• Q: Who can bypass policy?
  → Global Admin, User Account Admin, Partner Support.

• Q: How many blocked words supported?
  → 5,000.