Deskhero
English
Start free

← Back to articles

Outlook Shared Mailbox: Setup, Use, and Troubleshooting

Outlook Shared Mailbox: Setup, Use, and Troubleshooting

An Outlook shared mailbox is a centrally managed mailbox that multiple licensed Microsoft 365 users can access to send and receive email from a shared address — no separate license required for the mailbox itself. To get started, ask your Microsoft 365 admin to create the mailbox, add you as a member, and grant Full Access plus Send As permissions. The shared mailbox account itself should stay blocked from direct sign-in at all times, per Microsoft’s own guidance.

Quick TL;DR checklist:

  • Admin action required: Create the mailbox in the Microsoft 365 admin center (Teams & groups > Shared mailboxes)
  • Permissions to request: Full Access (to open and read) + Send As (to reply as the shared address)
  • Sign-in: Keep the shared mailbox account blocked from direct login
  • Outlook client support: New Outlook for Windows, Classic Outlook desktop, Outlook on the web (OWA), Outlook for Mac, and Outlook mobile (iOS/Android) all support shared mailboxes
  • Help: Microsoft Support and Microsoft Learn are the authoritative references for setup and troubleshooting

Table of Contents

What is a shared mailbox and when should you use one?

A shared mailbox is a delegation-based mailbox tied to a common email address — think support@yourcompany.com, info@, or reception@ — that any authorized team member can open, read, and reply from without needing a separate login. It is not a distribution list (which only forwards mail) and not a personal mailbox with shared access. It is a distinct mailbox object in Exchange Online that multiple people manage together.

Common use cases:

  • Customer support: — A support@ address where agents triage and respond to incoming tickets

Where a shared mailbox works well, it works very well. A small support team of two to five people handling a manageable volume of email can run entirely out of a shared inbox with no additional tooling.

That said, there are scenarios where a shared mailbox is the wrong tool. If you need to send newsletters or announcements to a large audience, a Microsoft 365 group or distribution list is a better fit. For teams with strict litigation hold, advanced compliance, or e-discovery requirements, a licensed mailbox with Exchange Online Plan 2 is more appropriate. And if your team needs ticket assignment, collision detection (knowing when two agents are replying to the same email), SLA tracking, or customer history across conversations, a dedicated helpdesk platform handles those needs in ways a native shared mailbox simply cannot.

How does an admin create a shared mailbox in Microsoft 365?

Creating a shared mailbox takes about five minutes in the Microsoft 365 admin center. Here are the exact steps:

  1. Sign in to the Microsoft 365 admin center at admin.microsoft.com
  2. Go to Teams & groups > Shared mailboxes
  3. Click + Add a shared mailbox
  4. Enter a display name and email address for the mailbox
  5. Click Save changes
  6. On the next screen, click Add members and search for the users who need access
  7. Select each member and click Save

After saving, automapping kicks in automatically for most users. Within about 30 minutes (sometimes up to an hour), the shared mailbox will appear in Outlook desktop without any manual steps from the user. The catch: automapping only works when permissions are granted directly to the individual user, not through a security group. If you add members via a security group, they will need to add the mailbox manually.

The shared mailbox account is blocked from direct sign-in by default, and that is intentional. Do not unblock it. If someone needs to sign in directly to manage the mailbox (for example, to set up rules in OWA), they should use their own credentials and open the shared mailbox from there.

Converting an existing user mailbox to a shared mailbox is also possible — useful when an employee leaves and you want to preserve their email address as a team inbox. In the admin center, go to Users > Active users, select the user, and choose Convert to shared mailbox from the Mail tab. Remove the user’s license afterward, since a shared mailbox does not need one (up to the 50 GB storage limit).

Pro Tip: To add many members at once via PowerShell, run: Add-MailboxPermission -Identity "support@contoso.com" -User "jsmith@contoso.com" -AccessRights FullAccess -AutoMapping $true and repeat for each user, or pipe a list. To block sign-in for the shared account from PowerShell, run: Set-MsolUser -UserPrincipalName "support@contoso.com" -BlockCredential $true

How does an admin create a shared mailbox in Microsoft 365? — overview diagram

What do Full Access, Send As, and Send on Behalf actually mean?

Permissions are where most shared mailbox confusion starts. There are three distinct permission types, and they do different things.

Full Access lets a user open the shared mailbox, read messages, move items, and manage folders. It does not allow the user to send email. Without a separate send permission, a user with only Full Access will see the mailbox but cannot reply from it.

Send As lets the user send email that appears to come directly from the shared address. The recipient sees support@yourcompany.com in the From field, with no indication of which individual sent it. This is the standard choice for most support and team inboxes.

Send on Behalf lets the user send email where the From field reads “Sender Name on behalf of Shared Mailbox Name.” The recipient can see both addresses. This is useful when transparency about who sent the message matters — for example, an executive assistant sending on behalf of a department head.

Permission Can open mailbox Can send as shared address Recipient sees
Full Access only Yes No N/A
Send As No (unless paired with Full Access) Yes Shared address only
Send on Behalf No (unless paired with Full Access) Yes (with attribution) “Agent on behalf of Shared Mailbox”
Full Access + Send As Yes Yes Shared address only

Recommended default for support teams: Grant Full Access + Send As to every agent. This gives them full read/write access and lets them reply as the shared address without any visible attribution.

A few practical notes on automapping behavior:

  • Automapping is enabled by default when you grant Full Access
  • It only works for direct user assignments, not security group assignments
  • To disable automapping for a specific user (useful when someone manages many shared mailboxes), use PowerShell: Add-MailboxPermission -Identity "support@contoso.com" -User "jsmith@contoso.com" -AccessRights FullAccess -AutoMapping $false
  • Send As and Send on Behalf permissions are set separately from Full Access and do not trigger automapping

How do you add a shared mailbox in each Outlook client?

The steps differ by client, and knowing which one you are using saves a lot of frustration. Here is what to do in each, based on Microsoft’s client-specific guidance.

New Outlook for Windows

If automapping is enabled, the shared mailbox appears automatically after you restart Outlook. If it does not show up within an hour:

  • Go to View > View settings > Accounts > Email accounts
  • Click Add account > Add a shared mailbox
  • Enter the shared mailbox email address and click Add

Classic Outlook desktop

Automapping handles this in most cases. If the mailbox does not appear after restarting:

  • Go to File > Account Settings > Account Settings
  • Select your Exchange account and click Change
  • Click More Settings > Advanced tab > Add
  • Type the shared mailbox name or email address and click OK

Outlook on the web (OWA)

To open a shared mailbox in OWA, click your profile picture in the top right, then select Open another mailbox. Type the shared mailbox address and click Open. This opens the mailbox in a separate browser tab. To add it as a persistent folder in your left nav, right-click Folders in the left panel, choose Add shared folder or mailbox, and enter the address.

Outlook for Mac

Outlook for Mac does not support automapping. Every user must add the shared mailbox manually:

  • Go to Tools > Accounts
  • Click the + button and select Open Shared Mailbox
  • Enter the shared mailbox email address and click Add

Troubleshooting checklist if the mailbox does not appear:

  • Restart Outlook and wait up to one hour for automapping to propagate
  • Confirm the admin granted Full Access directly to your user account (not via a security group)
  • Try adding the mailbox manually using the steps above for your client
  • In Classic Outlook, try clearing the Outlook cache: close Outlook, delete the .ost file, and reopen
  • Verify the mailbox is visible in the Exchange admin center and that your account is listed as a member

How do you use a shared mailbox on Outlook mobile?

Outlook for iOS and Android both support shared mailboxes, but the experience works a bit differently than desktop. The official mobile add flow is straightforward:

  1. Open the Outlook mobile app and tap your profile icon in the top left
  2. Tap Add account
  3. Select Add a Shared Mailbox
  4. Enter the shared mailbox email address
  5. Tap Add Mailbox

The shared mailbox then appears as a separate account in your Outlook mobile app, with its own inbox, sent items, and folders.

Push notifications on mobile behave differently than on desktop. When you add the shared mailbox as an account (using the steps above), you will receive push notifications for new messages. If you only have Full Access granted through a security group and the mailbox is not added as a separate account, notifications may not work reliably.

Pro Tip: Pin the shared mailbox inbox to your Favorites in Outlook mobile so it appears at the top of your account list. On iOS, long-press the folder and tap “Add to Favorites.” On Android, tap the three-dot menu next to the folder and select “Add to Favorites.” This keeps critical shared folders visible without switching accounts constantly. For high-volume inboxes, use the mobile web version of OWA as a fallback when the app’s notification behavior is inconsistent.

How does sending and Sent Items work in a shared mailbox?

When composing a new message or replying from a shared mailbox, Outlook lets you choose the From address. In Classic Outlook, click From in the compose window and select the shared mailbox address. In New Outlook and OWA, the From field appears automatically when you compose from within the shared mailbox folder.

Outlook defaults to your personal address when you reply from your main inbox, even if the original message was sent to the shared address. Always check the From field before sending.

Sent Items behavior is one of the most common pain points. By default, a sent message may land in the sender’s personal Sent Items folder rather than the shared mailbox’s Sent Items, making it invisible to other team members. Microsoft has addressed this with a setting that copies sent messages to the shared mailbox Sent Items folder. An admin can enable this via PowerShell:

Set-Mailbox -Identity "support@contoso.com" -MessageCopyForSentAsEnabled $true -MessageCopyForSendOnBehalfEnabled $true

Once enabled, replies sent as the shared address appear in the shared Sent Items folder, so the whole team can see what was sent and by whom.

Signature limitations and workarounds:

  • Outlook desktop does not support automatic signatures for shared mailboxes the same way it does for personal accounts
  • Each user must manually create a signature for the shared mailbox address in their Outlook settings
  • In OWA, you can set a mailbox-level signature under Settings > Mail > Compose and reply while signed in as the shared mailbox (requires temporary sign-in unblock, then re-block)
  • A practical workaround: create a shared signature template in the team’s internal knowledge base and ask agents to paste it manually, or use a third-party signature management tool like Exclaimer or CodeTwo

Server-side rules set in OWA are another useful tool. Rules created inside the shared mailbox (not in a personal account) apply to all incoming mail regardless of which agent is logged in, making them far more reliable than client-side rules for routing, auto-categorizing, or auto-forwarding specific message types.

What are the storage limits and when do you need a license?

Shared mailboxes are free up to 50 GB of storage without requiring a dedicated license. That covers the vast majority of small and mid-sized team inboxes. Once the mailbox approaches that threshold, or when you need features beyond basic email storage, a license becomes necessary.

Scenario License needed? Storage available
Basic shared inbox under the standard free storage limit No license needed storage according to Microsoft guidelines
Inbox exceeding the standard free storage limit Exchange Online Plan 1 license required additional archive storage available
Archive mailbox (In-Place Archive) Exchange Online Plan 1 or Plan 2 —
Litigation hold or In-Place Hold Exchange Online Plan 2 Unlimited hold storage
Advanced compliance / eDiscovery Microsoft 365 E3/E5 or add-on Varies by plan

The decision is straightforward: if your shared mailbox is under 50 GB and you do not need archiving or legal holds, leave it unlicensed. If you are approaching 50 GB, assign Exchange Online Plan 1 to unlock the archive. If your legal or compliance team needs litigation hold, Plan 2 is the minimum.

One thing admins often miss: when you convert a user mailbox to a shared mailbox, you can remove the user’s license and the mailbox stays active as long as it stays under 50 GB. If the mailbox was on a plan with a larger storage allocation, the limit drops to 50 GB after the license is removed, so check the current size before removing the license.

How do you fix a shared mailbox that is not showing up or sending correctly?

Most shared mailbox problems fall into a handful of categories. Work through this list before escalating.

If the mailbox is not appearing in Outlook:

  1. Restart Outlook and wait up to one hour for automapping to propagate
  2. Confirm Full Access was granted directly to the user account, not via a security group
  3. Add the mailbox manually using the client-specific steps in the section above
  4. In Classic Outlook, close Outlook, delete the local .ost cache file, and reopen
  5. In the Exchange admin center, verify the mailbox exists and the user is listed as a member under Recipients > Shared

If automapping is not working:

  • Check that the permission was set with -AutoMapping $true (the default) and not explicitly disabled
  • Security group membership does not trigger automapping; only direct user assignments do
  • Remove and re-add the permission via PowerShell to force a refresh: Remove-MailboxPermission then Add-MailboxPermission

If you get a “You do not have permission to send the message” error:

  • Full Access alone does not grant send rights; verify Send As or Send on Behalf is also assigned
  • In the Exchange admin center, go to Recipients > Shared > select the mailbox > Manage mailbox delegation and confirm the send permission is listed
  • Allow up to 60 minutes for permission changes to propagate before testing again
  • Via PowerShell, check current permissions: Get-RecipientPermission -Identity "support@contoso.com"

Admin-level checks:

  • Verify the shared mailbox is not hidden from the address list (this can prevent it from being found during manual add)
  • Confirm the mailbox is not over its storage quota, which can block sending
  • Check the Exchange admin center’s message trace if a specific message is not delivering

What are the real limitations of shared mailboxes and how do you manage them well?

A shared mailbox is a coordination tool, not a collaboration platform. That distinction matters operationally.

Security non-negotiables:

  • Always keep the shared mailbox account blocked from direct sign-in, per Microsoft’s explicit guidance. Direct sign-in breaks the audit trail because actions are no longer attributed to individual users.
  • Never create a password for the shared mailbox account or convert it to a licensed user just to bypass delegation. That approach destroys auditability and creates a shared credential security risk.
  • Manage access entirely through delegation (Full Access, Send As) so every action in the mailbox is logged under the individual user’s account.

Scalability limits:

Microsoft recommends shared mailboxes for teams with a modest number of concurrent users. As team size grows and message volume increases, the absence of native assignment, collision detection, and SLA tracking becomes a real operational problem. When two agents reply to the same email without knowing the other is doing so, or when messages sit unread because everyone assumes someone else handled it, the shared mailbox has hit its ceiling.

Operational best practices that actually work:

  • Use color categories to signal ownership: assign a category (e.g., “In Progress - Sarah”) when you pick up a message, and remove it when resolved
  • Create server-side rules in OWA to auto-route specific senders or subjects to subfolders, reducing inbox noise
  • Appoint a daily owner or on-call agent responsible for the inbox during their shift, so there is always one person accountable for triage
  • Set the Sent Items copy setting (MessageCopyForSentAsEnabled) so all sent replies are visible to the whole team
  • Never move messages from the shared mailbox to a personal folder; keep everything in the shared mailbox so the team has full context

Do-not-do list:

  • Do not grant access via security groups if you want automapping to work
  • Do not rely on personal Sent Items for shared mailbox replies
  • Do not use the shared mailbox as a personal archive by moving unrelated messages into it

Pro Tip: Audit shared mailbox membership quarterly. People change roles, leave teams, or leave the company, and stale Full Access permissions are a security gap. In the Exchange admin center, pull the membership list under Recipients > Shared and cross-reference it with your current team roster.

Key Takeaways

A shared mailbox in Microsoft 365 gives teams a free, delegation-based shared address up to 50 GB, but it requires deliberate permission setup, client-specific configuration, and operational discipline to avoid missed replies and security gaps.

Point Details
Admin creates, members access Only an admin can create the mailbox; grant Full Access + Send As directly to each user, not via security groups.
50 GB free, license when needed The mailbox is free up to 50 GB; assign Exchange Online Plan 1 for archive or when storage exceeds that limit.
Block sign-in always Keep the shared mailbox account blocked from direct login to preserve audit trails and security.
Operational discipline required Use categories, server-side rules, and a daily owner to prevent missed or duplicate replies.
Deskhero for teams that need more When assignment, collision detection, SLAs, or analytics become necessary, Deskhero connects your Microsoft 365 mailbox to a full helpdesk workflow.

The shared mailbox works until it does not

Here is the honest take on shared mailboxes after watching teams run them at various scales: the tool is genuinely good for what it was designed to do. A small team, a manageable volume, a clear set of categories and rules — that setup runs cleanly. The problems start when teams treat a shared mailbox as a substitute for a real support workflow.

The biggest operational failure is not a technical one. It is the assumption that visibility equals accountability. Everyone can see the inbox, so everyone assumes someone else is handling the email that just came in. That assumption is how messages sit for two days in a shared mailbox that three people check every hour. The fix is not a better tool — it is a daily owner, a category system, and a clear rule that uncategorized messages are unowned messages.

The second thing most guides miss: the Sent Items problem is not just a convenience issue. When replies land in personal Sent Items instead of the shared mailbox, you lose the team’s institutional memory. A new agent has no idea what was promised to a customer last week. Enabling MessageCopyForSentAsEnabled via PowerShell is a five-minute fix that prevents weeks of confusion.

On the question of when to move to a helpdesk: the signal is not message volume. It is when your team starts having conversations about who owns what. The moment you are spending more time coordinating the inbox than working it, the shared mailbox has done its job and it is time for something with assignment and collision detection built in.

When your team outgrows the native shared mailbox

At some point, categories and daily owners are not enough. When your support team needs to know who owns each conversation, when two agents are typing replies to the same email at the same time, or when your manager asks for first-response time data you cannot produce, the native shared mailbox has hit its limit.

Deskhero

Deskhero connects directly to your existing Microsoft 365 mailbox and turns it into a ticketed shared inbox without a new email address or a migration. Every incoming email becomes a ticket. Agents see who is working on what in real time, so duplicate replies stop happening. You get assignment rules, SLA tracking, AI-drafted replies drawn only from your approved knowledge base, and a ticket insights map that shows where your backlog actually lives. The two-way email sync means customers still get replies from your own company address, and nothing sends automatically unless you opt in.

For teams ready to make that move, the Deskhero helpdesk for sales-driven support is a strong starting point. The 30-day free trial requires no credit card, and setup takes minutes, not days.

Useful sources

Official Microsoft documentation is the authoritative reference for setup, permissions, and licensing. These pages are maintained by Microsoft and reflect current product behavior:

Follow the official Microsoft Learn and Microsoft Support pages for licensing and compliance updates, as limits and feature availability change with each Exchange Online service update.

FAQ

What is a shared mailbox in Outlook?

A shared mailbox is a delegation-based mailbox in Microsoft 365 that multiple users can access using their own credentials to send and receive email from a common address like support@ or info@. It does not require a separate license for the mailbox itself (up to 50 GB), and the associated account should remain blocked from direct sign-in.

What are the main disadvantages of using a shared mailbox?

Shared mailboxes lack native ticket assignment, collision detection, and SLA tracking, which means teams must rely on manual conventions like categories and daily owners to avoid duplicate or missed replies. They also have feature gaps in newer Outlook clients, including limited shared contacts support in New Outlook and inconsistent add-in behavior.

How is a shared mailbox different from a Microsoft 365 group inbox?

A shared mailbox uses delegation (Full Access, Send As) and appears as a standard mailbox in Outlook, while a Microsoft 365 group has its own membership model, a group inbox, a shared calendar, and a SharePoint site. Groups are better suited for team collaboration and large audiences; shared mailboxes are better for a team address that needs to send and receive as a single identity.

How do I access my shared mailbox in Outlook?

If your admin granted you Full Access directly (not via a security group), the shared mailbox should appear automatically in Outlook desktop within about an hour via automapping. If it does not, go to File > Account Settings > Account Settings in Classic Outlook, or View > View settings > Accounts in New Outlook, and add the shared mailbox manually using its email address.

When should a team switch from a shared mailbox to a helpdesk tool?

The clearest signal is when your team starts spending time coordinating who owns which email rather than actually answering them. If you need assignment, collision detection, first-response time reporting, or SLA enforcement, a helpdesk platform like Deskhero connects to your existing Microsoft 365 mailbox and adds those capabilities without requiring a new email address or migration.