How to Create a Microsoft 365 Shared Mailbox Without a License

You can create a Microsoft 365 shared mailbox without buying a separate license for the mailbox itself. The usual setup is to create an address such as support@yourcompany.com, add licensed employees as members, grant the correct permissions, keep direct sign-in blocked, and configure Sent Items so the whole team can see replies.
The no-extra-license rule has limits: the shared mailbox can store up to 50 GB, and each person who accesses it must already have a licensed Exchange Online mailbox. Archiving, litigation hold, storage above 50 GB, and some advanced compliance features require additional licensing.
What is a Microsoft 365 shared mailbox?
A shared mailbox gives several people access to one business email address and its calendar. Common examples include info@, support@, sales@, billing@, and reception@. Team members open it from their own Microsoft 365 accounts rather than signing in with a shared password.
When configured with Send As, a reply appears to come from the shared address instead of the employee. This creates a consistent customer experience and keeps incoming messages in one place. Microsoft’s official shared mailbox overview recommends this model for company information, support, reception, and other addresses used by multiple employees.
When does a shared mailbox need a license?
A shared mailbox normally does not need its own license if it stays within the standard conditions. Microsoft currently documents a 50 GB unlicensed storage limit.
| Scenario | Separate mailbox license? |
|---|---|
| Shared mailbox using 50 GB or less | Usually no |
| Members accessing it from licensed Exchange Online mailboxes | The members need licenses; the shared mailbox usually does not |
| Mailbox needs up to 100 GB | Yes—Microsoft specifies Exchange Online Plan 2 |
| In-place archiving or auto-expanding archive | Yes—an eligible Exchange Online license or archiving add-on is required |
| Litigation hold | Yes—an eligible Exchange Online license is required |
| Advanced Defender, Purview, retention, or eDiscovery features | May require additional user or mailbox licensing |
Your organization also needs a Microsoft 365 business plan that includes Exchange Online email. Microsoft 365 Apps for business alone does not include hosted email, while plans such as Microsoft 365 Business Standard do. Check the current licensing page for your tenant and region before purchasing or removing a license.
Before you create the mailbox
Make four decisions first:
- Address: Choose a durable address such as
support@company.com, not an employee’s name. - Owners: Assign at least two responsible internal users so access does not depend on one person.
- Sending identity: Decide whether replies should show only the shared address or “Person on behalf of Shared Mailbox.”
- Operating rules: Define who monitors the inbox, expected response times, folders or categories, and how completed messages are handled.
A shared mailbox centralizes email, but it is not a complete help-desk system. It does not provide advanced ticket ownership, service-level reporting, collision detection, or a full customer history by itself. Use dedicated support software when those controls become important.
How to create a Microsoft 365 shared mailbox
1. Sign in with the correct admin role
Open the Microsoft 365 admin center with an account that has the Exchange administrator role. If your company runs a hybrid Exchange environment, Microsoft advises creating and managing the shared mailbox from the on-premises Exchange admin center instead.
2. Add the shared mailbox
In the admin center, go to Teams & groups → Shared mailboxes. If the navigation is collapsed, select Show all first.
- Select + Add a shared mailbox.
- Enter a descriptive display name, such as “Customer Support.”
- Review the proposed email address and change it if needed.
- Select Save changes.
Microsoft notes that provisioning can take a few minutes. Wait for the mailbox to finish creating before adding members or troubleshooting missing controls. The current steps are documented in Microsoft’s shared mailbox setup guide.
3. Add members
Under Next steps, choose Add members to this mailbox, select the employees who need access, and save. Only users inside your organization can be assigned direct shared-mailbox access; Microsoft does not support granting it to an external Gmail or other outside account.
Each member must access the shared mailbox through their own licensed Exchange Online mailbox. Do not distribute a common password or ask people to sign in directly as support@.
Choose the right mailbox permissions
Membership alone does not explain what a person can do. Review these permissions carefully:
Full Access
Full Access, sometimes labeled Read and manage, lets the user open the mailbox, read and modify messages, manage folders, and use the shared calendar. It does not independently allow the user to send from the shared address.
Send As
Send As makes a message appear to come directly from the shared mailbox. A customer sees “Customer Support” or support@company.com as the sender. This is usually the clearest option for a public-facing team address.
Send on Behalf
Send on Behalf shows the individual and the shared mailbox, such as “Alex on behalf of Customer Support.” Choose it when the organization wants the employee’s identity visible.
For normal shared-mailbox operation, Microsoft recommends granting both Full Access and the appropriate sending permission. In the Microsoft 365 admin center, open the mailbox and use Manage mailbox permissions. The Exchange admin center also exposes delegation under Recipients → Mailboxes.
Keep direct sign-in blocked
A shared mailbox has an associated Microsoft 365 user object, but it is not intended to be used as a normal user account. New shared mailboxes have sign-in blocked by default. Leave it blocked.
Users should authenticate with their individual accounts, where your organization can enforce multifactor authentication, Conditional Access, device policies, and offboarding. A shared password removes individual accountability and increases the chance that access survives after an employee leaves.
Review the mailbox’s account under Users → Active users and confirm that sign-in is blocked. Also review the member list regularly and remove former employees promptly. Access changes can take time to replicate, so do not treat a delay of a few minutes as proof that the permission failed.
Make sent replies visible to the whole team
This is the setting most administrators miss. By default, a message sent from the shared mailbox is stored in the sender’s personal Sent Items folder, not in the shared mailbox’s Sent Items folder. Other team members may therefore be unable to see that a customer already received a reply.
To change this:
- Go to Teams & groups → Shared mailboxes.
- Select the mailbox.
- Find Sent items and choose Edit.
- Enable the options that copy messages sent as—or on behalf of—the mailbox into its Sent Items folder.
- Save the change and test both sending modes.
Microsoft documents this default and the available settings in its shared mailbox configuration guide.
Configure automatic replies, forwarding, and email apps
Automatic replies
You can configure text-only automatic replies for senders inside or outside the organization. A useful support reply confirms receipt, provides working hours, gives an expected response window, and directs urgent issues to the correct channel. Avoid promising an exact response time that the team cannot maintain.
Email forwarding
A shared mailbox can forward incoming email without a separate mailbox license. However, external forwarding introduces security, privacy, and compliance risks. Microsoft warns that forwarding does not stop spam, phishing, or malware from reaching the outside recipient; that destination needs its own filtering. Prefer membership and controlled internal access unless there is a documented business reason to forward.
Allowed email apps
Under Email apps, choose which clients and protocols members can use. Disable legacy or unnecessary access methods according to your organization’s security policy. Changes should match the controls applied to normal user mailboxes.
Add the mailbox to Outlook
Classic Outlook and Outlook on the web
With automapping enabled, the shared mailbox normally appears in Outlook after the user receives Full Access, closes Outlook, and reopens it. Microsoft says automapping is enabled by default in most environments.
If the mailbox does not appear, first wait for permission replication, then restart Outlook. In Outlook on the web, the user can open another mailbox or add the shared folder, depending on the interface available to the tenant.
Automapping works with permissions assigned directly to users. If access is granted through a security group, the mailbox may not be automatically mapped. The user may need to add it manually.
New Outlook for Windows
In new Outlook, go to Settings → Accounts → Shared with me. An automapped mailbox can be converted to an account, or a permitted mailbox can be added manually. Microsoft notes that adding a shared mailbox as a full account is still rolling out and has known gaps for some calendar, contacts, tasks, archive, and add-in features. See the current new Outlook shared-mailbox guidance before standardizing the workflow.
Outlook for iOS and Android
In Outlook mobile:
- Sign in to the employee’s primary work account.
- Open the account menu and choose Add Account.
- Select Add a Shared Mailbox.
- If several accounts are present, choose the licensed account that has permission.
- Enter or select the shared address.
The mailbox and the user’s primary mailbox must be in Exchange Online and use Microsoft’s supported sync technology.
Use the shared calendar correctly
Creating a shared mailbox also creates a shared calendar. Members can add and manage appointments from Outlook, which is useful for customer visits, team coverage, or shared equipment bookings.
Use it for appointments owned by the team, not for every employee’s personal focus schedule. If the organization uses Google Calendar for individual time protection, our guide to scheduling Focus Time and automatically declining meetings explains that separate workflow.
Shared mailbox vs distribution list vs Microsoft 365 Group
| Tool | Best use | Important limitation |
|---|---|---|
| Shared mailbox | Several employees read and reply from one business address | Members can modify or delete mailbox content; it is not a ticketing system |
| Distribution list | Deliver one message to several individual inboxes | No central inbox or shared Sent Items history |
| Microsoft 365 Group | Broader collaboration with group conversations and connected Microsoft 365 resources | Different sending and mailbox behavior from a traditional shared address |
Microsoft currently recommends considering a Microsoft 365 Group if more than 25 users need the mailbox. It also advises using a group when outside participants or restrictions on message deletion are important. Choose the collaboration model before moving years of operational email, because Microsoft says a shared mailbox cannot be migrated directly into a Microsoft 365 Group.
Build a simple operating process
A mailbox only works when the team agrees on ownership. Create a lightweight process:
- Use folders or categories such as New, In Progress, Waiting for Customer, and Resolved.
- Assign responsibility through a documented convention rather than assuming someone else replied.
- Keep sent replies in the shared mailbox.
- Use signatures that identify the employee when appropriate.
- Schedule a daily check for unread and aging messages.
- Review members and permissions monthly.
For a billing inbox, include the transaction or project reference in the subject. If your service business accepts online payments, pair the inbox with a clearly defined checkout flow such as the one in our guide to creating a Stripe Payment Link for a service business.
Troubleshoot common shared mailbox problems
The mailbox does not appear in Outlook
Confirm the user has Full Access, wait for Microsoft 365 to replicate the change, close Outlook completely, and reopen it. If access comes from a security group, automapping may not work; add the mailbox manually or assign the permission directly where appropriate.
The user can read email but cannot send
Full Access does not include sending rights. Grant Send As or Send on Behalf, then allow time for replication. Microsoft says a newly created mailbox or new sending permission can take roughly an hour to become usable across its data centers.
Replies are missing from the shared Sent Items folder
Enable the shared mailbox’s Sent Items options in the admin center. Test both Send As and Send on Behalf because they have separate controls.
The mailbox stopped sending or receiving
Check storage first. An unlicensed shared mailbox is limited to 50 GB. Microsoft warns that a mailbox at its limit can stop sending and eventually stop receiving, resulting in non-delivery reports. Reduce data safely or assign the correct license before increasing the quota.
An external contractor cannot be added
Direct shared-mailbox access is limited to people inside the organization. Do not share credentials as a workaround. Use a supported Microsoft 365 Group, a help-desk platform, or another collaboration design that supports external participants and your security requirements.
Send As fails after hiding the mailbox
Microsoft notes that Send As and Send on Behalf can fail in Outlook desktop when the shared mailbox is hidden from the Global Address List. Make it visible while adding it to profiles and testing permissions, then assess whether hiding it is compatible with the required workflow.
Security and maintenance checklist
- Direct sign-in remains blocked for the shared mailbox account.
- Every member uses an individual licensed account with MFA and organizational security policies.
- Only necessary users have Full Access and sending permission.
- Shared Sent Items copies are enabled.
- External forwarding is disabled unless formally approved.
- Storage remains below the unlicensed 50 GB limit.
- Licensing covers archives, holds, retention, and advanced compliance features.
- Former employees are removed immediately during offboarding.
- The team has a clear monitoring, ownership, and escalation process.
Frequently asked questions
Is a Microsoft 365 shared mailbox free?
It does not usually need a separate license when it uses 50 GB or less and does not require licensed archive, hold, or advanced compliance features. The organization needs an Exchange Online subscription, and every person accessing the mailbox needs a licensed Exchange Online mailbox.
Can users sign in directly to a shared mailbox?
They should not. Microsoft says a shared mailbox is not intended for direct sign-in, and its associated account should remain blocked. Users access it through their own accounts and delegated permissions.
Can a shared mailbox receive email from outside the company?
Yes, when your Exchange settings allow it. The restriction applies to who can be granted access to use the mailbox: direct members must be inside the organization.
Can more than 25 people use one shared mailbox?
Microsoft documents a maximum of 25 supported users and warns that heavier simultaneous access can cause connection failures or duplicate messages. For a larger audience, consider a Microsoft 365 Group or dedicated support platform.
What happens when the mailbox reaches 50 GB?
An unlicensed shared mailbox can lose the ability to send and later receive email. Reduce its storage or assign the eligible Exchange Online license required for a larger quota.
Why are sent messages stored in an employee’s mailbox?
That is the default behavior. Enable the shared mailbox’s Sent Items options so copies of messages sent as or on behalf of the address are visible to the team.
A correctly configured shared mailbox gives a small team a professional public address without an unnecessary mailbox license. The key is to respect the storage and licensing limits, grant both reading and sending permissions deliberately, preserve the shared reply history, and never replace individual authentication with a common password.


