logo
Dobble - Company Logo
Main Menu
Get a Quote

Learning Centre

What Is A Shared Mailbox In Microsoft 365?

Learn what a shared mailbox in Microsoft 365 is, how it differs from personal mailboxes, groups and lists, and when it suits team email management for business.

—
On this page

    Definition

    Shared Mailbox in Microsoft 365

    A shared mailbox in Microsoft 365 is a mailbox that multiple approved users can access to read, send and manage email from one shared address, such as info@, accounts@ or support@. It is usually used for team-based communication rather than one person’s private email.

    A shared mailbox is not the same as a personal mailbox, distribution list or Microsoft 365 Group. The right option depends on how the mailbox will be used, who needs access and whether emails need to be sent from the shared address.

    Key Takeaways

    • A Microsoft 365 shared mailbox lets several users manage one business email address without sharing a password.
    • Shared mailboxes are useful for role-based addresses such as info@, sales@, accounts@ and support@.
    • Permissions, naming, security, retention and ownership should be planned before the mailbox becomes business-critical.

    Plain English Explanation

    What a Shared Mailbox Does

    A shared mailbox gives a team access to one email inbox. Instead of forwarding messages between staff or asking people to log in with the same password, approved users open the shared mailbox from their own Microsoft 365 account. For example, a business may use [email protected] for invoices. The finance team can read incoming emails, reply to suppliers and keep the conversation history in one place. If someone leaves the team, their access can be removed without changing the mailbox address. The most common reason businesses use a shared mailbox is continuity. Customers, suppliers and staff can keep using the same email address, while internal access can change as the team changes.
    Shared mailboxes help teams manage role-based email addresses without sharing login details.
    Shared mailboxes help teams manage role-based email addresses without sharing login details.

    How It Works

    How a Microsoft 365 Shared Mailbox Works

    A shared mailbox sits inside Microsoft 365, usually through Exchange Online. It has its own email address, inbox, sent items, folders and calendar, but it is accessed through user permissions rather than a separate shared password. An administrator grants access to individual users. Those users then open the shared mailbox from Outlook on desktop, Outlook on the web or another supported Microsoft 365 email client. Depending on the permissions granted, they may be able to read messages, manage folders, send from the shared address or send on behalf of it. This permission-based model is important. It means each person still signs in with their own account, which supports better access control and accountability. If a staff member changes role or leaves the business, their access can be removed without disrupting the mailbox itself.

    Shared Mailbox Terms Worth Knowing

    Microsoft 365 uses several permission and mailbox terms that sound similar. These are the ones most businesses need to understand before setting up a shared mailbox.

    Full Access
    A permission that lets a user open the shared mailbox and manage its contents, including reading emails, moving messages and using folders.
    Send As
    A permission that lets a user send email so it appears to come directly from the shared mailbox address.
    Send on Behalf
    A permission that lets a user send a message on behalf of the shared mailbox, usually showing both the user and the mailbox name to the recipient.

    Typical Setup

    What Happens When a Shared Mailbox Is Set Up

    The exact setup can vary depending on the Microsoft 365 tenant, security settings and business requirements. In general, a shared mailbox follows this structure.

    1. Create the mailbox and email address

      The shared mailbox is created in Microsoft 365 with a clear role-based address, such as support@, enquiries@ or accounts@. The name should be easy for staff and customers to recognise.

    2. Assign user permissions

      Approved users are granted the right level of access. Some may only need to read and manage messages, while others may also need Send As or Send on Behalf permissions.

    3. Test access, sending and folder behaviour

      The mailbox should be tested in Outlook or Outlook on the web. This helps confirm that users can open it, send correctly and find sent messages where expected.

    Shared Mailbox vs Distribution List vs Personal Mailbox

    These options are often confused, but they solve different email problems. Choosing the wrong one can create clutter, missed replies or poor access control.

    Feature Shared Mailbox Distribution List or Personal Mailbox
    Team access Multiple users can access one central mailbox using their own Microsoft 365 accounts. A distribution list sends copies to users, while a personal mailbox belongs to one person.
    Reply history Replies can remain in one shared location if configured and used consistently. Replies may be scattered across individual mailboxes or tied to one staff member.
    Best use case Role-based business addresses that need shared management, such as info@ or accounts@. Announcements, simple forwarding, or individual staff communication.

    Business Use Cases

    When a Shared Mailbox Makes Sense

    A shared mailbox is useful when the email address represents a role, department or business function rather than one individual. Common examples include general enquiries, accounts payable, sales, recruitment, bookings and internal administration. It can also help when several people need visibility over the same communication trail. If a customer emails support@, the next available team member can see what has already been said and respond with more context. That is much cleaner than relying on forwarded emails. A shared mailbox is less suitable when the work needs structured ticket numbers, formal service level tracking, automation, customer portals or detailed reporting. In those cases, a helpdesk, CRM or workflow system may be more appropriate than a mailbox alone.

    Benefits and Limits of Shared Mailboxes

    Benefits

    • They reduce password sharing because users access the mailbox through their own accounts.
    • They keep role-based communication in one place, which helps when staff responsibilities change.
    • They can make customer, supplier and internal enquiries easier for a team to monitor.

    Limits

    • They are not a complete replacement for a CRM, helpdesk or project-management system.
    • Poor permissions or unclear ownership can lead to missed messages and duplicate replies.
    • Microsoft licensing, storage and feature rules can apply, depending on how the mailbox is used.

    Do Not Share One Password Between Staff

    A shared mailbox should be accessed through individual user accounts with assigned permissions. Sharing one password between staff weakens accountability, makes offboarding harder and can increase security risk.

    Security and Management

    Security Considerations for Shared Mailboxes

    A shared mailbox can improve access control when it is configured properly, but it still needs careful management. The most important rule is to grant access only to people who genuinely need it. Permissions should be reviewed when staff change roles, leave the business or move between departments. Businesses should also consider multi-factor authentication for user accounts, clear internal rules for who replies to messages and a consistent process for filing or archiving important emails. A shared mailbox can quickly become messy if everyone uses it differently. Email authentication also matters. SPF, DKIM and DMARC records help receiving mail servers verify that email from your domain is legitimate. These records do not guarantee inbox placement, but incorrect DNS authentication can contribute to deliverability problems. This is why shared mailbox setup should be considered alongside domain and DNS management, not treated as a standalone inbox task.

    Simple Shared Mailbox Example

    This example shows how a business might structure a shared mailbox for accounts-related communication. It is not a universal setup, but it shows the difference between the mailbox address and the users who have permission to access it.

    text 
    Shared mailbox address: [email protected]

Users with Full Access:
- [email protected]
- [email protected]
- [email protected]

Users with Send As permission:
- [email protected]
- [email protected]

    The users keep their own sign-ins, while the mailbox remains a central business address.

    Shared Mailbox Planning Checklist

    Before creating a shared mailbox, it is worth planning how it will be used. This helps avoid duplicated replies, missing access and messy folder structures later.

    • Confirm the business purpose

      Decide whether the mailbox is for enquiries, accounts, support, bookings or another clear function. Avoid creating vague inboxes that no one owns.

    • List who needs access

      Separate users who need to read messages from those who also need to send from the shared address.

    • Document the mailbox rules

      Agree who monitors the inbox, how messages are assigned, how folders are used and when access should be reviewed.

    Common Shared Mailbox Mistakes

    Most shared mailbox problems come from unclear ownership or weak configuration, not from the mailbox technology itself.

    Giving too many people access

    Do this instead

    Only grant access to users who need it. Review permissions when staff leave, change roles or no longer need visibility.

    Using a shared mailbox as a helpdesk

    Do this instead

    Use a shared mailbox for simple shared communication. If you need ticket numbers, assignment rules and reporting, consider a dedicated support or CRM system.

    Ignoring sent item behaviour

    Do this instead

    Test where sent messages are stored. Teams need to know whether replies appear in the shared mailbox, the user’s sent items, or both.

    Common Problems With Microsoft 365 Shared Mailboxes

    If a shared mailbox is not behaving as expected, the issue is often related to permissions, Outlook behaviour, DNS, or user expectations.

    A user cannot see the shared mailbox in Outlook

    Likely cause

    The user may not have Full Access permission, Outlook may not have refreshed yet, or the mailbox may need to be opened manually.

    Solution

    Check permissions in Microsoft 365, allow time for changes to apply, then test access through Outlook on the web as a clean comparison.

    Emails sent from the shared mailbox look like they came from the wrong person

    Likely cause

    The user may have Send on Behalf permission instead of Send As permission, or Outlook may be using the wrong From address.

    Solution

    Review the permission type and test sending from the correct From address. Choose Send As when the email should appear to come directly from the shared mailbox.

    The shared inbox is disorganised or messages are missed

    Likely cause

    The issue may be operational rather than technical. Several users may be reading, moving or replying to emails without agreed rules.

    Solution

    Define mailbox ownership, folder rules and response processes. If the work has grown beyond email, consider whether a CRM or helpdesk system is needed.

    Dobble Approach

    How We Approach Microsoft 365 Business Email

    We primarily use Microsoft 365 for business email hosting, with other reputable third-party providers used where client requirements call for them. When we assist with email hosting and management, we look beyond the mailbox itself. Business email depends on the domain, DNS records, authentication settings, user access and migration planning. For shared mailboxes, that means considering who needs access, how the address fits into the business, and whether the setup supports reliable day-to-day communication. We also pay attention to SPF, DKIM and DMARC because email deliverability is affected by more than the inbox platform. Microsoft 365 and other email platforms remain third-party services, so availability, policy changes and technical limitations are subject to the provider. We can help configure and manage the environment where appropriate, but no provider can guarantee email delivery, inbox placement or uninterrupted email availability.

    Related Service

    Email Hosting and Management

    If your business needs Microsoft 365 email, shared mailboxes, DNS authentication or migration support, we can help review the setup and manage the technical details.

    View Email Hosting

    Shared Mailbox FAQs

    These answers cover common practical questions businesses ask before using shared mailboxes in Microsoft 365.

    Does a Microsoft 365 shared mailbox need its own licence?
    In many Microsoft 365 environments, a standard shared mailbox may not need its own licence if it stays within Microsoft’s included limits and does not use licensed features. Licensing rules can change and depend on the tenant, storage, compliance and feature requirements, so they should be checked before relying on this.

    Can users log in directly to a shared mailbox?
    A shared mailbox should normally be accessed through the user’s own Microsoft 365 account and assigned permissions. Direct shared login is not recommended because it weakens security and accountability.

    Is a shared mailbox the same as an alias?
    No. An alias is an extra address attached to an existing mailbox. A shared mailbox is a separate mailbox that multiple users can access and manage with permission.

    Summary

    A Shared Mailbox Is Useful When It Is Planned Properly

    A shared mailbox in Microsoft 365 is a practical way for a team to manage one role-based email address. It can reduce password sharing, improve continuity and keep customer or supplier communication in one place. The key is planning. A shared mailbox needs clear ownership, appropriate permissions, sensible naming, secure user access and a process for monitoring messages. It should also fit within the wider email setup, including domain records, Microsoft 365 configuration and email authentication. If the mailbox has become central to your business operations, it is worth reviewing the setup before small email issues turn into missed messages or access problems.

    Need Help With Microsoft 365 Shared Mailboxes?

    We can review your business email setup, configure shared mailboxes, check DNS authentication and help plan email migrations where needed. If your email, domain and website systems are managed by different providers, we can help bring the technical pieces into a clearer structure.

    Discuss Your Email Requirements View Email Hosting

    Keep learning

    Related articles

    See all articles
    Tap to call
    Enquire now

    Ask Dobble

    Ask a question

    Send us your question and the Dobble team will get back to you.

    Prefer to talk to us directly?

    0423 016 104 [email protected]

    Get in touch

    Contact us

    Tell us about your project and the Dobble team will be in touch shortly.

    Prefer to talk to us directly?

    0423 016 104 [email protected]