Does a shared mailbox in Microsoft 365 need its own license?

Usually not on its own, though this depends on your plan and the mailbox's storage size. Larger shared mailboxes or ones that need archiving may require a license. Check your current Microsoft 365 plan details to confirm.

Can I set up an Outlook shared inbox without an admin?

No. Creating a shared mailbox requires Microsoft 365 administrator permissions in the admin center. A regular user can be granted access to an existing shared mailbox, but only an admin can create one and assign permissions.

How many people can access one shared mailbox?

Microsoft supports many members on a single shared mailbox, well beyond what a small team needs. The practical limit is coordination, not the member count. The more people share one mailbox, the more you feel the lack of built-in assignment and status.

What is the difference between Send as and Send on behalf of?

Send as makes a reply look like it came directly from the shared address, with no individual name attached. Send on behalf of shows both the sender and the shared address, so recipients can see who actually wrote the message. Choose based on whether you want replies attributed or anonymous.

Does alfred_ give me a shared inbox?

No. alfred_ is a personal AI assistant for your own mailbox, not a shared team inbox. It connects to your individual Outlook, Microsoft 365, or Gmail account to triage, draft, and track your email. If you need several people working one address, use a Microsoft 365 shared mailbox for that and consider alfred_ for each person's own inbox.

How to Set Up a Shared Inbox in Outlook

Setting up an Outlook shared inbox is the standard way to let a team read and reply from one address like support@ or team@ without sharing a single password. If you run a support queue, a billing address, or a general contact box, a shared mailbox in Outlook and Microsoft 365 gives everyone a common view of what came in and what still needs a reply. This guide walks through how to set one up at a high level, explains who can access it, and covers the limits so you know when a shared inbox is the right tool and when it is not.

Before we start, one note on terminology, because Microsoft uses two words that people mix up constantly.

Shared mailbox vs shared inbox in Outlook

In everyday conversation, “shared inbox” is what people call any single email address that a group of people works out of together. Inside Microsoft 365, the actual feature that powers this is called a shared mailbox.

A Microsoft 365 shared mailbox is a mailbox that does not have its own login. It usually does not consume a paid license on its own (subject to your plan and storage limits), and members access it through their own accounts. When someone replies, the message can appear to come from the shared address rather than from that person’s personal name.

So when this article says “Outlook shared inbox,” it means a Microsoft 365 shared mailbox that your team opens inside Outlook. Same thing, two names.

How to set up an Outlook shared inbox

The setup happens in the Microsoft 365 admin center, not in the Outlook client itself. You need administrator permissions to do this. Microsoft updates its admin interface fairly often, so treat the steps below as the accurate high-level process and confirm the current button labels in Microsoft’s official admin documentation as you go.

Sign in to the Microsoft 365 admin center. Use an account with admin rights. Shared mailbox creation lives under the Teams and groups or Shared mailboxes area of the admin center.
Create a new shared mailbox. Give it a display name (for example, Support Team) and an email address (for example, support@yourcompany.com). Microsoft provisions the mailbox behind the scenes. It can take a little time before it is ready to receive mail.
Add members. Choose the people who should be able to read and send from the mailbox. Every member you add gets access through their own Outlook account, so no shared password is needed.
Grant the right permissions. There are two that matter:
- Send as lets a member send email that looks like it came directly from the shared address.
- Send on behalf of shows both the person and the shared address, so recipients see who actually wrote the reply. Pick one based on whether you want replies to look fully anonymous (Send as) or attributed (Send on behalf of).
Access it in Outlook. Once permissions propagate, the shared mailbox usually appears automatically in each member’s Outlook folder list, often within a few hours. If it does not show up, members can add it manually through their account settings. In Outlook on the web and the desktop app, it sits as a separate mailbox below their personal one.

That is the whole process. Everyone on the team can now see incoming mail to the shared address and reply from it. For a deeper comparison of tools built specifically around this workflow, see our guide to the best shared inbox software.

The limits of an Outlook shared inbox

A shared mailbox solves one problem well: giving several people a common view of one address. It was not designed to help those people actually get through the mail. A few limits show up quickly.

No drafting help. A shared mailbox is a container, not an assistant. It does not read threads, summarize what a customer is asking, or write a reply for you. Every response is still typed from scratch by whoever grabs the message.

Permissions overhead. Send as, Send on behalf of, membership, and license rules all have to be managed by an admin. When someone joins or leaves, an administrator has to update access. For a small team this is minor. As you grow, it becomes a recurring task.

It gets messy at volume. The native shared mailbox has no built-in concept of assignment or ownership. Two people can open the same message and both reply. Nobody can tell at a glance which emails are handled and which are waiting. There is no status, no “assigned to,” and no easy way to see who is on the hook for what. At low volume you can coordinate by talking. At high volume, things fall through.

These are not bugs. They are just the edges of what a shared mailbox was built to do. If your real problem is a team that needs to divide and track a support queue, purpose-built tooling handles the assignment and status layer that Outlook does not. If your real problem is your own inbox drowning you, that is a different tool entirely.

When a personal AI assistant fits better

Here is the distinction that trips people up. A shared inbox answers the question “how do several people work one address together.” It does not answer “how do I stop dropping the balls in my own inbox.”

If you are reaching for a shared mailbox because your personal email is out of control, the shared inbox is the wrong fix. It adds coordination overhead without reducing the actual work of reading and replying. What helps there is a personal assistant that works your inbox with you.

That is what alfred_ does. It is a personal AI executive assistant, not a shared queue. It connects to your own Outlook, Microsoft 365, or Gmail account and:

Triages your inbox so the messages that matter surface first and the noise stays out of the way.
Drafts replies in your voice that you approve before anything sends. Nothing goes out without you.
Remembers your follow-ups so the thread you meant to answer three days ago does not quietly disappear.
Sends you a proactive brief and SMS nudges so you act on the right things without living in your inbox.

The difference is dropped follow-ups versus team assignment. A shared inbox exists to divide work across people. A personal AI assistant exists to keep one person’s commitments from slipping. Some teams need both: a shared mailbox for the support queue and a personal assistant for each individual’s own load. They solve different problems, and it is worth being honest about which one you actually have. For a fuller breakdown, read shared team inbox vs personal AI assistant.

Set up the shared mailbox, then fix the real bottleneck

A Microsoft 365 shared mailbox is the right call when a team genuinely needs to work one address together, and the setup above will get you there. Just be honest about the problem you are solving. If the pain is really your own inbox, no amount of shared-mailbox configuration will fix it.

alfred_ handles that side: a personal assistant that triages, drafts in your voice, and remembers your follow-ups, all with your approval before anything sends. There is a free trial, so you can see whether it lightens the load before committing. Try alfred_ on your inbox and keep the shared mailbox for what it is actually good at.