You can add a shared mailbox in Outlook by getting Full Access permission from your Microsoft 365 admin, then letting Outlook auto-map it into your folder pane, usually within 30 minutes to a few hours. If it doesn't appear, you add it manually via File > Account Settings > Account Settings > Change > More Settings > Advanced > Add. Shared mailboxes under 50 GB don't need a paid license, but mailboxes over 50 GB require one.
The steps differ by client. Classic Outlook for Windows and Mac auto-map and support manual adds. New Outlook for Windows and Outlook on the web show shared mailboxes automatically once permission is granted, and new Outlook also supports adding any mailbox you have Full Access to. Mobile apps have the narrowest path, and there the shared mailbox must be added as a second account on iOS or Android. Permission propagation and cache behavior cause most "it's not showing up" complaints, so the guide below covers the fix for each failure point.
What Full Access permission actually grants and what it leaves out
Full Access gives a delegate the ability to open a shared mailbox and read, send, and delete mail inside it, with permissions checked when the mailbox is opened. What it does not grant is Send As or Send on Behalf, which are separate permissions that control how outgoing mail is labeled. A user with Full Access only can open the mailbox and read everything in it, but the From field won't offer the shared address until a send permission is added.
The distinction matters because many admins grant Full Access in the Microsoft 365 admin center or Exchange admin center and assume the job is done. According to Microsoft's documentation on shared mailboxes in Exchange Online, Full Access lets a delegate sign in to the mailbox and act on its contents, while Send As lets the delegate send messages that appear to come from the shared address. Create the shared mailbox, add Full Access for each member, then add Send As or Send on Behalf for anyone who replies to customers under that address.
Automatic mapping is the default behavior of Full Access. Outlook for Windows detects the permission at profile load and adds the shared mailbox to the folder pane without user action. Admins can disable this by running the PowerShell cmdlet that sets the automapping parameter to false on the mailbox permission, which is a common source of confusion when users report the mailbox "never appears." If auto-mapping is off, every user has to add the mailbox manually.
Microsoft also states that shared mailboxes aren't meant for direct sign-in. User accounts shouldn't have passwords for the shared mailbox, and delegates access it only through their own credentials. On mobile, that rule bends, because iOS and Android can't display a shared mailbox as a folder collection the way desktop Outlook does. Treat the mobile setup as a separate case, covered later.
Check the license requirement before you touch any settings
Microsoft's licensing rule, documented in the Microsoft 365 admin center guidance for shared mailboxes, is that a shared mailbox doesn't need a paid license as long as it stays at or under 50 GB and no delegate needs archiving or an online archive. A shared mailbox can hold up to 50 GB of storage with no assigned license, and receiving mail larger than 25 MB is blocked regardless of mailbox size.
Shared mailboxes are capped at 50 GB for unlicensed use, and the guidance has long been that a license is required once the mailbox grows past that threshold. Once it exceeds 50 GB, the mailbox stops receiving mail until you assign a license or archive and delete content. Estimate the trigger before rollout: a support inbox receiving 8 GB of mail per year crosses the 50 GB line in roughly six years, which is slow enough that most teams never hit it. A shared inbox that receives large attachments daily can cross it in under two years, and those are the ones to watch.
A second licensing trap: any delegate who works in the shared mailbox on a device also needs their own licensed account, because the delegate's sign-in is the only sign-in. Per Microsoft's guidance, shared mailboxes can only be accessed by users who have been granted permissions and are signed in with a licensed account. A tenant with unlicensed kiosk accounts can't let those accounts open a shared mailbox. Provision a licensed account first.
Sign-in restrictions vary by tenant. If your organization enforces security defaults or Conditional Access policies, a shared mailbox permission still resolves through the delegate's own account. Nothing about the shared mailbox bypasses the delegate's sign-in requirements. Confirm that at the tenant level before rollout, rather than debugging it user by user.
How to add a shared mailbox in Outlook: the auto-mapping path first
Before adding anything manually, confirm the permission is actually live. Auto-mapping takes effect when Outlook next loads the profile, and the mailbox usually appears in the folder pane on its own. Steps:
1: Restart Outlook completely, closing all windows, not just the message window. 2: Open the folder pane and scroll to the bottom of the folder list. 3: Look for the shared mailbox name, collapsed beneath your own mailbox. 4: If it's there, click the chevron to expand it, then open Inbox and confirm mail is arriving. 5: If it's missing, wait 30 minutes to several hours for permission replication, then restart Outlook again. 6: If it's still missing after a day, an admin should confirm the permission in the Exchange admin center, then verify the automapping parameter on the mailbox.
Auto-mapping is the path Microsoft engineers for Shared Mailboxes as Standard Mailboxes, and it requires no PowerShell from the user side. It's also the design most likely to fail quietly: a permission granted with automapping disabled produces no error, no bounce, and no visible mailbox in the folder pane, so the admin needs to confirm the setting rather than the user.
If the mailbox appears but the mail inside looks stale, that's the cache problem described later. If it appears in one Outlook profile and not another, compare the automapping setting across the two accounts. In tenants where one delegate was added before an admin changed the automapping parameter, the two users can behave differently with identical permissions, which is one of those edge cases a help-desk script won't catch.
Manual add in classic Outlook for Windows, step by step
When auto-mapping is off or the mailbox won't appear, add it by hand. Microsoft's support documentation for Outlook for Windows lists the manual add path through account settings. Steps:
1: Open Outlook and click File > Account Settings > Account Settings. 2: On the Email tab, select your Microsoft 365 account and click Change. 3: Click More Settings. 4: Open the Advanced tab and click Add. 5: Type the shared mailbox's full email address exactly as provisioned, such as [email protected]. 6: Click OK, then Apply, then close the dialogs and restart Outlook. 7: The mailbox appears in the folder pane below your own, expanding to show Inbox, Sent Items, and other folders.
The email address must match the shared mailbox's primary SMTP address. If the mailbox has an alias and the permission was granted under a different address, the manual add fails with "The name cannot be matched to a name in the address list." That error means the address or permission is wrong, not that Outlook is broken, and the fix lives in the admin center. For the "The name cannot be matched" path, run a quick check of the address the user typed.
A second failure has nothing to do with the user: Outlook caches the address book, and a newly created shared mailbox can take up to 24 hours to appear in that cache. If the manual add fails for a brand-new mailbox, retry after a day. Send/receive sync (F9 is the classic manual trigger) refreshes mail, not address-book entries, so pressing it repeatedly doesn't speed this up.
There's a debt on each Windows device: the shared mailbox's folder data is cached locally, and if the profile already holds the maximum number of cached mailboxes Outlook will sync, adding the shared mailbox pushes it into "Mail to keep offline" settings territory. Classic Outlook's slider caps cached mail, and profiles with several accounts can push the shared mailbox past the cache limit. If the mailbox appears but mail only loads online, check the sync slider. On shared computers, cached data also means mail from the shared mailbox sits in the profile's OST file, so a user who wants no local copy should use Outlook on the web for it instead.
Mac, new Outlook for Windows, and Outlook on the web behave differently
Outlook for Mac adds shared mailboxes through a different path, and Microsoft's Mac support documentation describes the process separately. Steps:
1: Open Outlook and click Tools > Accounts. 2: Select the Microsoft 365 account and click Advanced. 3: Open the Delegates tab and click the plus under "People I am a delegate for." 4: Type the shared mailbox address and select it from the search results. 5: Click Add and confirm, then close and restart Outlook. 6: Expand the shared mailbox in the folder pane.
Mac auto-mapping has been limited historically compared with Windows, so the manual add is the reliable path on Mac. If the delegate tab shows an empty list after an admin grants permission, sign out of the account in the app and sign back in to refresh the local permission state.
Outlook on the web (outlook.office.com) displays a shared mailbox automatically once Full Access is active. Microsoft's guidance is that the mailbox appears in the folder pane after the delegate has been granted permission, with no add step. New Outlook for Windows behaves closer to the web client and supports adding a shared mailbox under Settings > Accounts > Shared mailboxes. If the legacy-mapped mailbox is missing in new Outlook, the add from settings is the workaround. Outlook on the web also carries no local cache, which makes it the fastest diagnostic: if the shared mailbox shows in the browser but not in desktop Outlook, the permission is fine and the desktop client is the problem.
Mobile apps need the shared mailbox as a second account
Outlook for iOS and Android don't render a shared mailbox as a delegate folder collection. Microsoft's mobile guidance is to add the shared mailbox as an additional account in the app. Steps:
1: Open Outlook on the phone and tap the account icon or Settings. 2: Tap Add Account and choose the Microsoft 365 option. 3: Enter the shared mailbox's address, not your own. 4: When prompted for a password, the app typically requires the delegate to sign in with their own credentials, but shared mailboxes have no password of their own. The workable path depends on tenant policy: some tenants permit adding the address under the delegate's identity, and some don't permit the second-account model at all. 5: Confirm the account added, then switch between inboxes using the account list.
The mobile add path has an authentication boundary that trips most people. A shared mailbox isn't a licensed account, so it doesn't have credentials, and the app can't authenticate as it directly. Check the tenant's policy and the app version before promising a phone setup, because behavior varies by app version and by tenant. Microsoft's documentation on shared mailboxes notes that the mailbox can be added on mobile per the platform guidance. If the mobile add fails at sign-in, that's a tenant policy or app-version problem, not a permissions gap.
An alternative that avoids the second-account model: use Outlook on the web on the phone's browser. It auto-displays shared mailboxes once permission is live and accepts the delegate's own sign-in. For a quick reply from a personal phone, that's faster than debugging the app.
Diagnosing a shared mailbox that won't appear or sync
Work through the failures in the order they occur, because each symptom points to a different culprit.
| Symptom | Most likely cause | Fix |
|---|---|---|
| Mailbox absent from every client | Permission not replicated or not granted | Confirm Full Access in Exchange admin center |
| Absent only in desktop Outlook | Automapping disabled | Manual add via Account Settings > More Settings > Advanced |
| Manual add fails with "name cannot be matched" | Address typed wrong or permission under a different alias | Confirm primary SMTP address |
| Appears on web, absent on desktop | Desktop profile or cache issue | Recreate the profile or check the sync slider |
| Mailbox present but empty | Local cache still building | Wait for sync, check "Mail to keep offline" |
Attribution: the automapping behavior and the manual-add path come from Microsoft's Outlook and Exchange Online documentation, the "name cannot be matched" error is documented in Microsoft's support content for Outlook, and the cache behavior is documented in Outlook's account-settings guidance.
If the mailbox appears in the browser and in new Outlook but not in classic Outlook for Windows, rebuild the Outlook profile. That's a heavier fix than it sounds, because rebuilding re-downloads all cached mail for the profile. For a user with a large primary mailbox plus the shared mailbox, budget an hour or more for re-sync. The browser check is always the first diagnostic step and costs nothing.
One failure the admin center can't fix: delegates in different tenants. Cross-tenant shared mailbox delegation in Exchange Online isn't supported in the way most people expect, and the delegate would need to be a user in the same tenant. If a contractor at another company needs access, that's a guest-account question, not a shared-mailbox question, and the answer comes from Microsoft's external collaboration guidance rather than the mailbox setup screens.
Fix the cache and folder-count limits after setup
Classic Outlook stores each mailbox's folders locally, and the "Mail to keep offline" slider determines how much is cached. A new shared mailbox can appear without its mail if the profile's cache budget is full. Steps:
1: Open File > Account Settings > Account Settings and double-click the account. 2: Drag the "Mail to keep offline" slider to a longer period, or to All for the full cache. 3: Click Next and finish, then restart Outlook and let sync complete. 4: To check local size, find the OST file via File > Account Settings > Data Files.
Microsoft documents that cached mode syncs a set volume of mail per profile, and the slider is the only user-side control. In profiles with two or more accounts, increasing the slider raises local disk use by the same proportion, so on a 100 GB disk with a large primary mailbox, choosing All can fill it. A practical rule: keep the slider at one year for primary mailboxes and accept that older shared mail items stay server-side until searched.
On folder-count limits, keep well clear of the boundaries. Microsoft's published limits for Exchange Online mailboxes include a maximum of 500 folders per mailbox and a maximum of 5,000 folders including subfolders when the folder hierarchy is deep. A shared intake mailbox that routes mail into dozens of subfolders per category can approach that ceiling in a busy sales organization. If the shared mailbox hits the limit, moves into subfolders fail and the mailbox needs restructuring or a separate mailbox.
New Outlook and Outlook on the web sidestep the cache-discussion entirely because nothing is cached locally. On shared or borrowed computers, add the shared mailbox in the browser instead of the desktop app. That's the configuration that keeps the mailbox's contents off the local disk, and it's the one to use with contractors on temporary machines.
Who should get Full Access, Send As, or Send on Behalf
Match permissions to job, and don't grant the maximum by default. Microsoft's shared-mailbox documentation treats Full Access, Send As, and Send on Behalf as distinct permissions that are granted separately. The combinations map to roles as follows.
Grant a sales coordinator Full Access plus Send As on the shared sales address if they answer inbound leads as the team. Grant a receptionist Full Access and Send on Behalf on the front-desk address if they must be identifiable, because Send on Behalf labels the message with the sender's name. Keep a manager with Full Access but no send rights on an inbox they should read but not answer. Give a contractor full access to a project mailbox for the contract term, then remove the permission when it ends, because departed delegates retain access until the permission is removed.
Permissions are not self-expiring. Microsoft's admin guidance covers the grant and revoke flows; nothing expires automatically, so an offboarding checklist that removes the user's license but not the shared-mail mailbox permission leaves the account unable to sign in but still on the access list. If that account is restored to undo an offboarding mistake, the mailbox delegation comes back with it.
One last combination to avoid: granting Send As to a distribution list. Sending as a group address from a shared mailbox is handled differently, and an email sent "on behalf of" a group can fail SPF or DMARC checks at the recipient's end. If the shared address must be the visible sender, use Send As, not Send on Behalf. The visible-from headers are different, and Microsoft's permission documentation spells out the practical difference.
FAQ
Does a shared mailbox need a license?
No, as long as it stays at or under 50 GB and no delegate needs archiving or an online archive. Microsoft's admin center guidance confirms the 50 GB unlicensed ceiling. Once the mailbox grows past it, mail stops flowing until a license is assigned or content is archived. Budget the trigger, not the moment it happens.
Why is my shared mailbox not showing up in Outlook?
The most common cause is that Full Access permission hasn't replicated yet, which can take 30 minutes to several hours and up to 24 hours after the mailbox is created. After that, the second cause is automapping being disabled on the mailbox permission. Confirm both before rebuilding a profile, because profile rebuilds re-download the whole local cache.
Can I add a shared mailbox as my primary account?
No, and trying to sign in directly to a shared mailbox is the most common misconception. Shared mailboxes have no password of their own and are meant to be opened through a delegate's licensed account, per Microsoft's shared-mailbox guidance. On phones, the app may require a second-account add, but the shared address still isn't a standalone sign-in.
What's the difference between Full Access and Send As in a shared mailbox?
Full Access lets the delegate open and act inside the mailbox. Send As lets outgoing mail show the shared address in the From field. Microsoft documents them as separate grants, and Full Access alone leaves the From field offering only the delegate's own address. Grant the send permission explicitly when replies must come under the shared address.
Which Outlook versions support adding a shared mailbox manually?
Classic Outlook for Windows and Outlook for Mac support the manual add through account settings or delegates. New Outlook for Windows has a Shared mailboxes section under Settings > Accounts, and Outlook on the web displays shared mailboxes automatically once permission is granted. If the manual path is missing, the app version or tenant policy is the variable to check.
How long does shared mailbox permission take to sync?
Microsoft advises allowing propagation time after granting Full Access, and the practical window is a few minutes to several hours. Restarting Outlook after the permission is granted is the user-side action that triggers the auto-map check. If nothing appears after a day, the issue is the grant or automapping setting, not propagation.
What happens if a shared mailbox gets too much mail?
It stops receiving at the 50 GB unlicensed limit until a license is assigned or archive and delete are used. Individual messages larger than 25 MB are blocked before they touch storage. A high-volume intake box that receives daily attachments can fill the quota in under two years at typical volumes, so size the license plan against the mailbox's observed mail volume.
Can I open a shared mailbox while offline?
Classic Outlook can show cached shared-mailbox mail offline, provided the mailbox is within the "Mail to keep offline" range. Fresh mail, calendar updates, and any uncached items are unavailable until the connection returns. Outlook on the web and new Outlook require a connection, so the offline-safe configuration is the classic desktop profile with the cache slider set long enough.