Somebody in IT tells you the access is done. You restart Outlook, look at the folder pane, and support@ is not there. Or the opposite version: it is there, you answer four customers from it before lunch, and a colleague opens the mailbox in the afternoon to find the Sent Items folder empty. All four replies are sitting in yours, where nobody else can see them.
Both of those are documented behavior. The awkward part is that the answer depends on which Outlook you are looking at, and there are five of them now: classic Outlook for Windows, new Outlook for Windows, Outlook on the web, Outlook for Mac, and the mobile apps. Microsoft covers the two Windows clients and the web in one article, then puts Mac, mobile, sent items, automapping and the offline caching behavior in five more, spread across two sites. This page collects the click paths and then explains the defaults that send people looking for help. If the term itself is new to you, what a shared inbox is and when a team outgrows the built-in options is the wider picture.
One thing this article does not cover: creating the mailbox and granting the permissions. That happens in the admin center, somebody with an admin role does it, and how the mailbox gets created and who gets access is written up separately. Everything below assumes that part is done and you are the person who has just been given access.
The short version
- Which Outlook you use decides the click path, and the five paths do not resemble each other.
- If access was granted normally, the mailbox usually appears by itself after a restart. If it was granted through a security group, it never appears by itself, and that is documented.
- Replies you send from the shared address land in your own Sent Items by default. The proper fix is a change on the mailbox, and your admin makes it.
- Adding the mailbox as an additional account is the only route that gives you event reminders from its calendar.
- Every shared folder you can see gets downloaded to your machine by default, which is why the person with access to five mailboxes has the slowest Outlook in the office.
Which Outlook are you actually in?
Worth settling before you click anything, because half the advice you will find applies to a version you are not running.
Classic Outlook for Windows is the desktop application with the ribbon across the top and a File menu that opens a full-page Account Settings screen. If there is a "Try the new Outlook" toggle in the top right corner, you are in the classic one.
New Outlook for Windows is the replacement, and it is a different product underneath. Microsoft publishes separate instructions for it, and as you will see below, a shared mailbox behaves differently there depending on whether you add it as a folder or promote it to an account.
Outlook on the web is whatever you get at your organization's webmail address. Outlook for Mac is its own application again, with its own limits. Outlook mobile is the iOS and Android app, which has a prerequisite that catches people out.
If you are not sure which Windows version you have, the toggle is the fastest tell. The rest of this article is organized by client, so read your own section and skip the others. Two sections near the end apply to everybody: sending from the address, and where your replies get filed.
Add a shared mailbox in new Outlook for Windows
Start by doing nothing at all. Microsoft's instruction is that after your admin adds you, you "close and then restart new Outlook. The shared mailbox should automatically display in your Folder pane." A good proportion of the time that is the whole procedure, and the shared calendar is added to your Calendars list along with it.
If it does not turn up, add it by hand. In Microsoft's guide to opening a shared mailbox in Outlook, the path is: in the Folder pane, right-click your account name, and select Add shared folder or mailbox, then type the address, for example info@contoso.com. It appears as a subfolder under Shared with me.
That gets you the mail. What it does not get you is the mailbox's own settings, and this is the part worth knowing about new Outlook: a shared folder and a shared account are two different levels of access to the same mailbox. Microsoft's page on managing shared mailbox settings in new Outlook documents the upgrade path. Go to Settings > Accounts > Shared with me, select the mailbox, and choose Convert to add it as a full account. A mailbox that was never automapped gets added there with + Add instead. You need Full Access permission from your admin either way.
Once it is an account, the mailbox shows up in the account selector for Categories, Notifications, Rules, and Automatic Replies. That last one matters. On the shared-mailbox guide linked above, Microsoft states flatly that "Only your Microsoft 365 admin has permissions to set up the ability to send automatic replies from a shared mailbox", and that page is describing classic Outlook and the web. Converting the mailbox in new Outlook is the documented way to reach that setting yourself.
Microsoft also publishes what is still missing, and it is a real list: calendar event search (email search works fine), People, contact sharing, Notes, Tasks, the Archive folder and add-ins are all documented as not yet available for a converted shared account. Several are marked as coming. If you rely on any of them, stay on the shared-folder version for now. Going back is a two-click reversal: select More on the mailbox, then Use as shared folder.
Add a shared mailbox in classic Outlook for Windows
Classic Outlook has three ways to hold a shared mailbox, and almost nobody knows about the third. Microsoft's documentation on adding a shared mailbox as an additional account states it plainly: "You can include a shared mailbox in your Microsoft Outlook profile as an automapped mailbox, an additional mailbox, or an additional account."
They are not interchangeable.
| Route | Who does it | How it gets there | What it costs you |
|---|---|---|---|
| Automapped mailbox | Your admin, by granting Full Access | Appears in the folder pane on its own after a restart | No event reminders. You cannot switch it off yourself |
| Additional mailbox | You | File > Account Settings > Account Settings > Email tab > Change > More Settings > Advanced > Add, then type the address | No event reminders |
| Additional account | You, after your admin disables automapping | File > Add Account | A round trip through your admin, and a wait |
The deciding column is the last one, and the reason is a single sentence in that same document: "Outlook doesn't show event reminders for a mailbox that is automapped or added as an additional mailbox. Outlook supports event reminders for a shared or regular mailbox only if you add the mailbox to your Outlook profile as an additional account."
So picture a shared mailbox whose calendar carries real appointments (customer calls, an on-call rota, a room booking) and a reader who has been quietly missing every reminder for it. Nothing is misconfigured. The two common routes do not produce reminders at all.
The additional-account route has one counter-intuitive step in it. Go to File > Add Account, enter the address of the shared mailbox, and select Connect. When you get the sign-in prompt, enter your own email address, not the shared one. Shared mailboxes have no password to sign in with. If the prompt will not let you change the address, select Sign in with another account to open a fresh one. Restart Outlook afterward.
Before any of that works cleanly, the mailbox has to stop being automapped, and this is the part you cannot do yourself. The same Microsoft page is direct about it: "Only an Exchange admin can disable automapping." Your admin runs a pair of PowerShell commands (Remove-MailboxPermission, then Add-MailboxPermission with -AutoMapping $false), and afterward, in Microsoft's words, "you might have to wait up to one hour for Microsoft Exchange to remove the automapped mailbox from your Outlook profile." That hour is about the removal. It is not a general rule for how long a new mailbox takes to appear.
Add a shared mailbox in Outlook on the web
The web version is the quickest of the five. Right-click Folders in the left navigation pane, choose Add shared folder or mailbox, and enter the address.
There is one behavior here to plan around. New-mail notifications for a shared mailbox added this way do not work. On the same Microsoft page linked above, the instruction is that "you must open the shared mailbox in a separate browser window" to get them. Practically, that means whoever is on inbox duty today should open the mailbox in its own tab and treat that tab as the shared inbox, instead of watching for it inside their own.
Add a shared mailbox in Outlook for Mac
Mac has its own application and its own rules. In Microsoft's page for opening a shared folder in Outlook for Mac, current Outlook for Mac uses File > Open > Shared Mailbox. There is a second route through Tools > Accounts, selecting your account, then Delegation and Sharing > Shared With Me and the plus sign. Legacy Outlook for Mac uses File > Open > Other User's Folder instead, where you pick the folder type and search for the person.
Two limits are stated outright on that page, and both explain support tickets.
Outlook for Mac "does not support Auto-mapping of shared mailboxes". A Mac user will never see the mailbox turn up by itself the way a Windows colleague does, no matter how the permission was granted. It always has to be added by hand. If your team is mixed and only the Mac users are complaining, that is the whole explanation.
Outlook for Mac also "currently supports only Full Access permissions for shared mailboxes". If a colleague was granted the ability to send from the address but not Full Access, they can add the mailbox on the web and on their phone, and the Mac app will refuse. The symptom looks like a broken app and is a permission mismatch.
To remove a shared mailbox later, hold Control, select the folder, and choose Remove Shared Account.
Add a shared mailbox to Outlook on iPhone and Android
Sign in to your own account in Outlook for iOS or Android first. Then, per Microsoft's mobile instructions, tap the Add Account button in the left navigation pane, then tap Add a Shared Mailbox. If you have several accounts in the app, pick the one that actually holds the permission.
Check the prerequisite before you spend twenty minutes on this. Microsoft supports shared mailboxes in the mobile apps "when your mailbox and shared mailbox are located in Exchange Online and using the native Microsoft sync technology". If either mailbox sits somewhere else, the option is not going to behave. Removal is Settings > Accounts, tap the shared mailbox, Delete Account.
Sending from the shared address
This part is the same in every client, which is why it sits outside the sections above. When you compose or reply, select From in the message and change it to the shared address. If From is not showing, it is a display option in the compose window, not a missing permission.
What the recipient sees depends on which permission you were granted, and the two are granted separately. Send As makes the message go out as the mailbox itself, so the customer sees support@ and nothing else. Send on Behalf shows both names, which suits an assistant writing for a named person and is usually wrong for a team address. If replies from your support address are arriving with an individual employee's name attached, that is the permission to check, and the grant side of this covers how it gets set.
Where your replies actually go
This is the single most common surprise, and it is a default rather than a fault. When you send from a shared address, the message is saved in your Sent Items, not the mailbox's. Microsoft's explanation of why sent mail is not saved to the shared mailbox is worth reading once: in Microsoft 365, shared mailboxes "don't require a license and can't be added to Outlook as independent mailboxes. You can't sign in to a shared mailbox. Instead, you sign in to your own mailbox, and then you open the shared mailbox." Outlook sends from the account that is signed in, so the copy goes where that account keeps its copies.
For a team this is worse than untidy. It means nobody can see what a colleague already told the customer, which is exactly the thing a shared address is supposed to prevent.
There are two documented fixes and they operate at different levels. The first is set on the mailbox by your admin, using set-mailbox with -MessageCopyForSentAsEnabled $True (and the matching -MessageCopyForSendOnBehalfEnabled for send-on-behalf). The second is a registry value called DelegateSentItemsStyle, set on one Windows machine, and it only works if that Outlook runs in Cached Exchange mode.
They interact, and Microsoft publishes the combinations:
| DelegateSentItemsStyle on the client | MessageCopyForSentAsEnabled on the mailbox | What you end up with |
|---|---|---|
| 0 | True | A copy in both your mailbox and the shared one |
| 1 | True | Two copies in the shared mailbox, none in yours |
| 0 | False | A copy in yours only. This is the default everyone complains about |
| 1 | False | A copy in the shared mailbox only |
Row two is why doing both looks like a good idea and is not. Ask for the mailbox-side setting and leave the registry alone: it applies to everyone on the address at once, it survives new laptops and new staff, and nobody has to edit a registry on five machines. There is also a hard reason to prefer it. Microsoft notes that "If you're using new Outlook, only Method 1 will apply", so the client-side trick is a dead end for anyone who has already moved.
When the mailbox does not show up
Work through it in this order.
Restart the client first, and give it a little time. Automapping happens through Autodiscover, and it is not instant. Restarting before you start debugging saves most of these.
Then ask how the permission was granted. This is the cause nobody guesses, and it is documented in Microsoft's own troubleshooting article on mailboxes that are not automapped. If full access was assigned through a security group, "the members of the assigned group don't see the mailbox get automapped to their Outlook profile. However, the mailbox can be accessed if the mailbox is manually added to the Outlook profile or by using Outlook on the Web." The reason is that the group's membership list "isn't expanded during the autodiscover process".
That symptom pattern is very specific and worth memorizing: it works on the web, it works if you add it manually, it never appears on its own. That combination points at a group-based grant. Microsoft's own resolution is that permission has to be assigned to each person directly for automapping to work.
Add it manually in the meantime. Whatever the cause, the manual routes above are unaffected by any of this, so you are not blocked while somebody sorts the permissions out.
On a Mac, stop looking. It was never going to appear by itself. See the Mac section.
In new Outlook, there is one more gate. Shared mailbox access there is switched on by a tenant-level policy, and Microsoft documents the setting as an Outlook on the web mailbox policy with OneWinNativeOutlookEnabled turned on. In Microsoft's words, "With this newly applied OWAMailboxPolicy, users can access and add shared mailboxes using new Outlook." If the add reliably fails in new Outlook while the web version works, ask whether that policy is set before anyone reinstalls anything.
What having it open costs you
Shared mailboxes are not free to keep in your profile, and the bill arrives as a slow Outlook.
By default, in Cached Exchange mode, "If you add another user's shared mailbox or shared folder to your profile, then all the folders in the shared mailbox to which you have access are downloaded to your local cache by default." Microsoft's page on download settings for shared mail folders spells out the consequence: those contents live in your local offline data file, and "If the shared folders contain many items or large attachments, the size of your .ost file size might grow significantly." Where an administrator has capped the size of that file by policy, caching shared folders "might result in the .ost file size limit being reached".
This is the mechanism behind an office pattern you have probably seen. The person who supports four or five addresses has an Outlook that takes a long time to start and periodically stops responding, and it is not their hardware. They are syncing four or five entire mailboxes onto one laptop.
Two things soften it. Since Outlook 2016, the Download email for the past setting applies to shared mailboxes as well as your own, which Microsoft says "helps to prevent the .ost file from becoming too large", though an administrator can revert that behavior. And the caching of shared folders can be switched off entirely, which is a setting your administrator controls through policy. The trade is that those shared folders then stop being available when you are offline.
The practical version: if you are in more than two or three shared mailboxes and Outlook is painful, remove the ones you do not open daily. In classic Outlook that is the same Account Settings screen you added them on.
What a shared mailbox in Outlook will not do for a team
Everything above is a per-person setting on a per-person machine, and that is the honest limit of the whole exercise. You can get the mailbox into five clients, fix the Sent Items, and still not know who is dealing with a given message right now.
Outlook has no concept of an owner. There is no field that says this one is mine, no way to see that a colleague opened a message four minutes ago and is halfway through a reply, no clock on how long a customer has been waiting. Most teams cover the gap with conventions that everyone half-remembers, and that holds up until two people are busy at the same time. The rules a team needs around a shared address is the practical version of those conventions, and it is worth writing them down before you spend money.
Past a certain volume the conventions stop being enough. A shared inbox tool such as TriageFlow puts an owner on each incoming message before anyone opens it, so the question of who has this one gets answered on screen instead of in a chat thread. If you would rather have status, priorities and a reference number on every conversation, what changes when a message becomes a ticket covers that direction. Neither is urgent at three people, and both get hard to avoid at ten: if you are somewhere in between and guessing, the support team size calculator puts a number on it.
Frequently asked questions
Why is my shared mailbox not showing in Outlook?
Restart the client first, since automapping runs through Autodiscover and takes a moment. If it still does not appear but you can reach the mailbox on the web or by adding it manually, the permission was almost certainly granted through a security group, which Microsoft documents as never automapping. On a Mac it will never appear by itself under any circumstances.
Why are my sent messages not saved in the shared mailbox?
Because Outlook sends as the account you signed in with, and files the copy in that account's Sent Items. Ask your admin to set MessageCopyForSentAsEnabled on the mailbox. That fixes it for everyone on the address at once, and it is the only method that works in new Outlook.
Can I set an automatic reply on a shared mailbox myself?
In classic Outlook and on the web, no: Microsoft states that only your Microsoft 365 admin can set that up. New Outlook has a route, which is to convert the mailbox to an account under Settings > Accounts > Shared with me. Automatic Replies then appears in the account selector alongside Categories, Notifications and Rules.
How do I get calendar reminders from a shared mailbox?
Add the mailbox to your profile as an additional account, using File > Add Account and signing in with your own address. That is the only route that produces event reminders. Automapped mailboxes and additional mailboxes do not.
How do I send an email from a shared mailbox in Outlook?
Compose as normal, then select From and switch it to the shared address. Whether the recipient sees only that address or sees your name alongside it depends on whether you were granted Send As or Send on Behalf, which are two separate permissions.
Does a shared mailbox need its own license?
No. Microsoft's documentation says shared mailboxes "don't require a license", which is also the reason you cannot sign in to one directly and why your replies get filed under your own account. The storage ceilings and the licensing exceptions sit on the admin side of this, covered in the shared mailbox and distribution list comparison.
Can I give a shared mailbox its own signature?
There is no first-party client-side setting for a per-mailbox signature. The only documented way to reach mailbox-level settings is the account route above: adding it as an additional account in classic Outlook, or converting it in new Outlook.
How do I remove a shared mailbox from Outlook?
In classic Outlook, go back to Account Settings, open More Settings > Advanced, select the mailbox under the list of additional mailboxes and remove it. On mobile it is Settings > Accounts > Delete Account, and on a Mac it is Control-click the folder and Remove Shared Account. If it reappears after a restart, it is automapped, and only your admin can stop that.
Bottom line
Find your client, use its path, and then deal with the two things the path does not cover. Get the Sent Items setting applied on the mailbox so the team can see its own replies, and if the mailbox has a calendar anyone depends on, ask your admin to disable automapping so you can add it as an account and actually get reminders. Both take one conversation with whoever administers your tenant, and both are easier to ask for now than after somebody misses something.