Here’s the short version: shared mailbox security means nobody signs in as the mailbox. Block sign-in on that account, let named people open it from their own login, and do not assume a conversion erased the old password.
info@, billing@, and the old office manager’s address are how a small firm actually works. They are also accounts with a password, a user object, and often a forward rule nobody has opened since 2022. This page is the control for that mailbox. It is not a reason to skip multi-factor authentication on the people who open it.
What shared mailbox security actually means
Microsoft’s shared mailbox article is blunt. A shared mailbox is not intended for direct sign-in with its user account. Block sign-in for that account and keep it blocked. The account still exists. It has a system-generated password that is not meant to be known or used. People who need the mail get permission on the mailbox and open it from their own licensed mailbox.
That split is the whole security model. The human has a name, MFA, and a password you can reset. The mailbox is a place, not a person. When five people know “the info@ password,” you have one account that cannot be tied to a leaver, and you cannot turn one of them off without turning all of them off.
A copier or a website form is not an excuse to leave sign-in open. If a device must send mail, that is a separate sending setup, with legacy authentication treated as a hole rather than a convenience. It is not a reason to put the shared mailbox password on a sticky note.
Block sign-in, including after a conversion
New shared mailboxes start in the right state. Microsoft’s create article says every new shared mailbox has sign-in blocked by default. The mailbox you made on purpose is usually fine. The mailbox you inherited is not.
A converted mailbox keeps the old password
Convert a user mailbox to a shared mailbox keeps the mail and the calendar, which is why firms do it when someone leaves. The same page has the line people skip: if you do not reset the password, the original username and password continue to work after the conversion. It also says not to delete the user account, because the account anchors the mailbox. And it points you at the extra steps for a leaver so they cannot sign in anymore.
So the conversion is not the offboarding. Microsoft’s former-employee article is the rest of that job, and our offboarding checklist is the local version of the same list. Block sign-in. Reset the password even though nobody should use it, because Microsoft says the old one still works until you do. Remove the leaver from Full Access and Send As. Do not delete the account the same afternoon and expect the mailbox to survive on its own.
Conditional Access still covers the humans. It is a weak story for a shared account that should not sign in at all. Blocked sign-in beats a clever exception.

Full Access is not permission to send
Microsoft documents three permissions, and they are not interchangeable. The create article defines them this way:
- Full Access opens the mailbox. The person can read, delete, and change mail, and can work in the calendar. They still cannot send as that address.
- Send As makes the message look like the shared mailbox sent it. The recipient does not see the delegate.
- Send on Behalf sends for the mailbox and shows that a named person did it.
Send As and Send on Behalf are different letters
Use Send on Behalf when the recipient should know which human wrote it. Use Send As for addresses that are supposed to look like the company, such as billing@, and keep that list short. Granting both to every member of the mailbox is how a temporary helper sends a wire instruction that looks official.
Business email compromise loves a shared address. The customer already trusts billing@. A delegate’s stolen mailbox, plus Send As, is enough. MFA on the delegate still matters. A shared password on billing@ skips that MFA entirely, which is another reason sign-in stays blocked.
You also cannot grant these permissions to a user in another organization. Microsoft’s mailbox permissions article says permissions are only inside the current organization. A bookkeeper at another firm does not get Full Access on your billing mailbox. If an outside person needs a conversation, that is a different tool, not a password you text them.
The 50 GB line, and the license people remove too early
A shared mailbox can store up to 50 GB with no license of its own. The person opening it still needs a licensed Exchange Online mailbox. Microsoft’s about article says that if you go past the storage limit, the mailbox can keep receiving for a while and then stop, and senders get a non-delivery report. “We will clean it up later” becomes bounced invoices.
These cases need a license, from the same Microsoft pages:
| Situation | What Microsoft requires |
|---|---|
| Under 50 GB, no archive, no hold | No license on the shared mailbox. Delegates still need their own mailbox. |
| Over 50 GB | Exchange Online Plan 2. Plan 1 on that mailbox is not the compliant fix. |
| Archive, including auto-expanding archive | Plan 2, or Plan 1 plus an Exchange Online Archiving add-on. |
| Litigation hold or in-place hold | Plan 2, or Plan 1 plus archiving. |
A hold is not included in the free 50 GB
The conversion article states the hold line directly: to put a litigation hold on a shared mailbox, assign Plan 2 or Plan 1 plus archiving. That matches the litigation hold guide. Removing the user’s license after a conversion is allowed when the mailbox is under 50 GB and you do not need the archive or the hold. Removing it because the invoice looked high, while counsel still wants the mailbox preserved, is how the hold button disappears.
Microsoft also posts a service advisory for shared mailboxes over 50 GB without the right license. If that advisory is in the admin center, the mailbox is already past the free line. Shrink it or license it. Do not wait for mail to stop.
Rules survive the person who left
Inbox rules are preserved when you convert the mailbox. A rule that forwards invoices to a personal address, or that files “wire” messages into RSS Feeds, does not die in the conversion. Open the rules on every shared mailbox you did not create yourself. If the address receives money mail, treat a new forward as an incident, not as a setting.
The From line is not an audit log
The From line will not save you when the permission is Send As. The recipient sees the shared address. The record of which delegate sent it is in auditing, not in the message they reply to. Turn mailbox auditing on before you need it, and review sends from billing@ and payroll@ when the dollar amount matters. A dark log is not proof the right person sent the note.

Outsiders do not get the mailbox password
Microsoft’s about article says that if people outside the business need access, consider a Microsoft 365 group instead of the shared mailbox. That is the right instinct. A vendor, a client, or a spouse who “helps with the books” should not know a password that opens company mail. They also cannot be granted mailbox permissions from another tenant.
If the front desk must read info@, give those employees Full Access on their own accounts and block sign-in on info@. When one of them leaves, remove that one permission. You do not change a password six people have memorized.
Do not put an admin role on the shared mailbox account. It is a mailbox. Global Admin belongs on named, rarely used admin accounts, not on reception@.
What we change, and what we leave as mail
On a tenant we manage, shared mailbox work looks like this.
- List every shared mailbox. Note which ones have sign-in allowed. Block those, unless a documented device flow is being replaced the same week.
- For any mailbox converted from a person, reset the password and block sign-in even if you think the conversion did it. Microsoft says the old password keeps working if you skip the reset.
- Write down who has Full Access, Send As, and Send on Behalf. Remove anyone who left. Prefer Send on Behalf when a human should be visible.
- Open inbox rules. Remove forwards you cannot explain.
- Check size. Under 50 GB with no archive and no hold can stay unlicensed. Over that line, or on hold, gets the license the article names.
- Do not delete the user object that anchors the mailbox.
We will not share one password for billing@ and call it collaboration. We will not remove a license a hold still needs. We will not treat a conversion as offboarding. If the shared addresses, the leavers, and the forward rules should be cleaned up as one pass, start with cybersecurity and contact Secure Techies. The mailbox can stay. The sign-in should not.
