How to Create a Microsoft 365 Group for Support Email
This guide walks you through creating a Microsoft 365 group that serves as a shared support inbox, covering prerequisites, each configuration step, and the mistakes that often cause delivery issues.
On this page
- Step 1: Sign in to the Microsoft 365 admin center
- Step 2: Navigate to Groups and add a new group
- Step 3: Choose Microsoft 365 as the group type
- Step 4: Name the group and set the primary email address
- Step 5: Set privacy and ownership
- Step 6: Configure email delivery settings
- Step 7: Verify routing to a shared inbox
- Step 8: Set up automatic replies and tagging (optional)
You can turn a Microsoft 365 group into a shared support mailbox that multiple agents can monitor and reply from. Before you begin, make sure you have admin access to the Microsoft 365 admin center and a custom domain verified in the tenant.
Step 1: Sign in to the Microsoft 365 admin center
Open admin.microsoft.com and sign in with a global admin or Exchange admin account. This portal is the only place where groups can be created and configured for email routing.
Step 2: Navigate to Groups and add a new group
In the left navigation, select Groups > Active groups, then click Add a group. Choosing the correct group type here determines whether the group can receive email and be used as a shared inbox.
Step 3: Choose Microsoft 365 as the group type
Select Microsoft 365 (not Distribution list or Security group). A Microsoft 365 group provisions a mailbox, a shared calendar, and a SharePoint site, which together enable collaborative email handling.
Step 4: Name the group and set the primary email address
Enter a display name such as Support Team and an email address like support@yourdomain.com. The address becomes the destination customers will use. If you need additional aliases (e.g., help@, info@), see How to Create Email Aliases for a Support Address.
Step 5: Set privacy and ownership
Choose Private if you want only members to see conversations, or Public for broader visibility. Add at least one owner (usually the support lead) and the agents who will manage tickets. Owners can later adjust settings and membership.
Step 6: Configure email delivery settings
After the group is created, open its settings and enable Allow external senders to email this group. Without this, messages from customers outside your organization will be rejected. Also turn on Send copies of group conversations to members so every agent receives a copy in their own inbox.
Step 7: Verify routing to a shared inbox
Send a test email from an external address to the group address. Confirm that the message appears in the group mailbox and in each member's inbox. For a deeper walk‑through of routing options, refer to Create a Support Email That Routes to a Shared Inbox.
Step 8: Set up automatic replies and tagging (optional)
In the group mailbox settings you can add an automatic reply that acknowledges receipt. Consider creating categories or tags for common issue types; this helps agents triage faster. For high‑volume environments, review Best Practices for Managing High Volume Support Email.
Common mistakes to avoid
- Creating a distribution list instead of a Microsoft 365 group — distribution lists lack a shared mailbox.
- Forgetting to allow external senders, which blocks customer emails.
- Leaving the group without an owner, so no one can manage membership or settings later.
- Using a personal mailbox as the support address, which prevents collaboration.
- Not testing the flow with an external address before announcing the address to customers.
When you’re ready to turn that group mailbox into tracked tickets, try NeuraDesk free.
Try NeuraDesk free and see if it fits your team.
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free