Outlook Shared Mailbox vs Microsoft 365 Group vs Distribution List, Decided Properly

The quickest way to tell the three apart is to ask where the mail actually lives. Send to a distribution list and Microsoft copies the message into every member’s personal inbox, five members, five copies, and no master copy anywhere at all. Send to a shared mailbox and the mail lands in one mailbox that several people can open, one copy, one place. Send to a Microsoft 365 group and it lands in the group’s own mailbox, a sort of side room with its own furniture, files, a calendar, a Teams tie-in, where members can drop in to read it or subscribe to have copies sent out to them as well.

Three addresses that look identical from the outside, three completely different rooms behind the door. And the reason this page needs writing is that almost nobody picked theirs. Whichever one the IT person set up first, back whenever support at your domain first needed to exist, is the one you are still running, on account of it working just well enough that changing it never made anybody’s list. Fair is fair, it did work, at the size you were then.

We sell the thing that sits one step past all three, so you know our angle from the start. Most of this page is Microsoft’s furniture and not ours, and two of the three verdicts below amount to stay where you are.

The support address that has been a distribution list since 2019

Here is the shape of the ordinary trouble, and you can check your own sent items afterwards to see whether it is yours.

Support at your domain is a distribution list. A customer writes in on a Tuesday morning, and the mail arrives five times, once each in five personal inboxes. Two of the five answer it, within the very same hour, politely contradicting each other on the refund window. One customer, two answers. Neither of the two people did a thing wrong, since neither had any way of seeing the other reaching for the keyboard. The other three, mind you, each assumed somebody else had it, and on a worse Tuesday all five assume that, and the man gets no answer at all from anybody.

The replies went out from personal addresses too, which is its own slow leak. What the customer writes back to is now one person’s inbox, so the thread has left the list entirely and lives wherever that person’s mail lives, and when she leaves in the autumn the whole correspondence goes and leaves with her. The new hire who starts in March opens a fresh inbox with nothing in it, on account of a distribution list keeping no history of its self anywhere. There is nothing to hand over, on account of the correspondence never having lived in one place that a handover could point at.

None of that is the list misbehaving. A distribution list is a broadcast tool, one address that fans a message out to many people, and for announcements, all-staff notices, the newsletter, a vendor’s alerts, it is exactly the right thing and we have a whole separate piece on it. It only breaks when it gets asked to hold a conversation, because holding things is precisely what it was built not to do.

The 365 group, which is a very good room for the wrong meeting

The Microsoft 365 group is the one people reach for second, usually after the distribution-list Tuesday described above, and it is a genuine improvement in the one way that matters least for support.

A group keeps the conversation. There is a group mailbox, the history sits in it, a new member can scroll back through the whole of it, and around the mailbox stands the furniture, shared files, a shared calendar, the Teams channel, the works. No complaints on that front. For a project team, a committee, a department talking to its self around its own documents, it is honestly the best thing Microsoft makes in this corner, and nothing below is an argument against using it for that.

Support mail goes quiet in there, though, and it goes quiet for a reason that takes a minute to see. The group’s mailbox is a place members visit, or subscribe to copies from, and a customer’s question does not chase anybody. It sits in the side room waiting for somebody to walk in, and on a busy week nobody walks in, since everybody’s actual work arrives in their actual inbox. The furniture makes it worse rather than better, truth be told, on account of the room being arranged for the team’s own conversation, threads about the team’s own things, and a stranger’s question about an invoice sits oddly among them, unowned, unstated, with no clock running on it and nobody sure whose turn it is. The group answers the question where does our stuff live. It was never trying to answer who is looking after this customer.

The shared mailbox, which is the right shape and still not finished

The shared mailbox is the one that was actually designed for the job you have. One mailbox, one copy of each mail, several people inside it at once, and replies can go out as the address its self, support at your domain, rather than under anybody’s personal name. The history stays put when people leave. The new hire opens it in March and the whole record is sitting there waiting for her. That is no small thing. And as licensing stands, a shared mailbox under fifty gigabytes needs no licence of its own, it rides on the licences your people already have, though check your own plan before quoting that at anybody, since Microsoft moves these lines about from time to time.

For two or three people at modest volume, that is genuinely enough, and if that is you, our advice is to go and set one up this afternoon and stop reading vendor pages, ours included. The move from a distribution list takes an hour or two, keep the old list for the announcements it was good at, point the customer-facing address at the mailbox, and the Tuesday problem is mostly over.

What the shared mailbox still does not have is everything above the mail: no owner on a message, so two people can still collide inside the one mailbox, just less often than five did. No state, so read and dealt-with look identical, and the gap between those two is the gap customers fall into. No clock, no escalation path, no rules doing the sorting, and an audit trail that thins out fast once you ask who actually handled a thing in June. The mailbox holds the record beautifully and holds nobody responsible for any of it, and that is not Microsoft failing, it is simply the edge of what a mailbox is.

The table, since nobody on this comparison ever ships one

Print it, argue with it, check it against your own tenant. The rows are the questions worth asking, whatever answers your setup gives.

The move its self, for the Friday you decide to do it

The order matters less than people fear. Set up the shared mailbox first and give the two or three actual answerers access to it. Test it quietly. Send a mail in, answer it as the address, watch where the reply lands. That is ten minutes of a Friday.

Then move the address. Point support at your domain at the mailbox rather than the list, and keep the old list alive under a new name for the announcements it was always good at, which costs nothing and spares you inventing a second habit for the all-staff mail. Nothing gets deleted. The old copies stay sitting in everybody’s personal inboxes, where they always were.

The old threads will not follow you over, mind you. History starts on the day of the move, on account of the record having lived five separate lives up to then, and there is no honest way of stitching five inboxes back into the one. Accept the clean start. Most desks find the first fortnight strange and the second one better, and by the third nobody would go back for money.

Agree two habits while you are at it. Replies go out as the address, never as your own self. And a mail that is dealt with gets marked or moved, the very same way, by one and all, so that read and done stop wearing the same face. Two habits, no invoice, and the mailbox is now doing the most of what a mailbox will ever honestly do for a support team, which is to say holding everything and chasing nobody.

The day the shared mailbox stops being enough

There is a day the shared mailbox stops being enough, and it has less to do with volume than people expect. It is the day conversations start needing to pass between hands without dropping, or needing a state somebody can check without asking about the place, or needing evidence of who said what for a dispute that came back in November. We have a full piece on that threshold and the four triggers that fire it, when a shared inbox becomes a ticketing system, and it deserves its own reading rather than a paragraph here. The short version is that a mailbox stores mail and a ticketing system fastens a record onto it, owner, state, clock, history, and the mail its self never changes, only what your company keeps.

If your operation runs on Google’s side of the fence instead, the very same argument exists over there and we have written it separately as the Google Collaborative Inbox piece, five stops and all. And if the actual question in your building is whether to leave the big providers entirely, that is a different decision again, written up under Gmail alternative, and it is a bigger move than anything on this page requires. You do not need to change providers to fix a support address. You need the mail to live in one place with names on things.

Where we come into it, briefly

Maxdesk sits on top of whichever address you already have. You forward support at your domain into the workspace, from the distribution list, the shared mailbox, the group, Microsoft or Google alike. What arrives then has a name on it, a state, and a clock running, which is precisely the layer the shared mailbox section above found missing. The shared inbox view keeps the one-place-one-copy virtue, helpdesk automation rules take the morning sorting off somebody’s hands, and the free plan takes unlimited people, on account of us billing the workspace rather than the seat. Your mail stays with Microsoft. We are not an email management software replacement for the mailbox, we are the record fastened on top of it.

The three verdicts, and the two that cost nothing

Keep the distribution list, for the job it was built for. Announcements, the all-staff mail, the alerts. Costs nothing. Works forever. And stop asking it to hold conversations.

Move the customer-facing address to a shared mailbox if it is on a list or in a group today, and do it this week, since the move is an afternoon and the improvement is immediate. The steps are up the page. For a small desk that may be the whole of the fix for a good long while, and we mean that plainly, no purchase attached.

And when the mailbox starts dropping handovers, that is the day to look one step further up, at us or at anybody in our trade. Not before, funnily enough. Buying a help desk for a two-person desk that a shared mailbox would have served is the same mistake as running support on a distribution list, in the opposite direction, and this page was written to save you from the both of them.

Fifteen minutes in your own sent items

Here is the check, and it wants no tool of any kind. Go through the team’s sent mail for the last fortnight, one and all, and count the replies to customer questions that went out under personal addresses rather than as the support address. Then count the questions where two people answered the very same mail, and the ones where nobody did.

Three counts on a bit of paper. If they are all near zero, your setup is fine, whichever of the three it is, and you can close this tab with our blessing. If they are not, the counts tell you which failure you are living with, scattered replies mean the list, silence means the group, collisions mean an unowned mailbox, and the fix for each is written above, and two of the three fixes are free.