Shared mialboxes in MS 365
Posted by IcyOutlandishness268@reddit | sysadmin | View on Reddit | 19 comments
I hope I chose the right group; if not, I apologize. I’m not very technical, but I run a small business. I switched our email provider to Microsoft because of Office for employees. Before that, we used a different provider and based our work on a few shared addresses like logistics@, sales@, etc. It worked somehow, and it also helped me cut costs a bit because we didn’t have many addresses.
Now we’re growing a little, and every employee has their own private mailbox, but the shared addresses still remain, and I wouldn’t want to change that. I thought that using shared mailboxes would make this work nicely, as the Microsoft representative promised, but it doesn’t quite work that way. We have a lot of problems with this, from simple ones like when someone chooses “Reply all” and the shared mailbox address is automatically included, or the lack of automatically selecting the shared mailbox as the default sender address, to more annoying issues, like when one person reads a message and everyone else sees it as read, or the need to change the signature every time because it can’t be set automatically for a shared mailbox.
This shouldn’t be the case, and I’m convinced you have this better worked out here. Could you share your ways of handling such shared mailboxes? I’ll bring this up in the company and make some changes, because I think my business needs to modernize a lot in this area.
printoninja@reddit
Understandable headaches at the start. For shared mailboxes in M365 with no extra cost: assign no license to the mailbox itself.. just the users who need access get the license, and you grant them access (Full Access, Send As) to the shared box via the Exchange admin center. The mailbox can hold 50GB with no per-mailbox license cost.
Two common gotchas:
Set-Mailboxshared@yourdomain.com-MessageCopyForSentAsEnabled $trueFor broader M365 admin work - assigning licenses, managing distribution lists, onboarding/offboarding - I built a tool called UserDesk that consolidates that into a clean delegation UI instead of bouncing between Exchange admin / Entra / Teams admin. Might be relevant if you're doing this often. getuserdesk.com if you want to check it out. If not, the above gets you the shared mailbox piece.
Let me know if you run into any other areas where you have questions in the environment
sakatan@reddit
If you're using Outlook Classic to work with these shared mailboxes: Disable Automapping for these mailboxes (for all users) so that they fall out of Outlook. Then add them manually via "Add account" rather than "open these additional mailboxes". This gets rid of so much bullshit; it's actually unreal that MS never bothered to correct this mechanism.
The rest is user training. Especially the read/unread status. For now, use categories when an employee has "reserved" a mail so that everyone else knows.
IcyOutlandishness268@reddit (OP)
What's funny, i did try, but always had error message about wrong password. Now i've tried again, but when prompt about password showed then i've chosen "use different account" and it added without issues. Big step for the beggining. Thank you
Disastrous_Recipe424@reddit
You shouldn't be adding the account via username & password. Add them as shared mailboxes in 365 admin console, assign the users to the shared mailbox & get them each to restart Outlook. The mailboxes will appear down the left-hand side under the users' own mailbox.
IcyOutlandishness268@reddit (OP)
yes, I know this, but like user mentioned, this way make many obstacles to users
NerdyNThick@reddit
If users are unwilling to learn the tools and equipment that they need to use for their job, that is a great big red flag.
Chico0008@reddit
Their is different ways of using shared mailbox with Outlook
1 - you can add the shared mailbox in your personnal flox (left list)
you can access mail and answer
but, when you answer, default reply address is your, you have to manually change to the shared mail address.
Your personnal profil setting are priori to shared mailbox.
+ when you reploy, sent mail w'ont go in the sent recipient of shared mailbox (there is a powershell command to fix this)
2 - you can open the shared mailbox in it's own space (new tab)
when you reply, the shared mail address is set by default.
for the fact than when someone read a mail, it is marked as read for everyone, it's normal, every change made to the shared is sync with other users connected to it.
NerdyNThick@reddit
Sorry, but... "flox" ??
Ihaveasmallwang@reddit
Put together some training for your users on the proper way to use the shared mailbox.
But from what you are describing as one person reading the message and it showing as read for everyone else who has delegation to that mailbox, it seems like what you are actually wanting isn’t shared mailboxes at all, but distribution groups which have a common email address just like shared mailboxes, but forward the message to everyone in the group.
IcyOutlandishness268@reddit (OP)
Yes, i know this distibution groups, but i like having whole mails history in one place, and shared mails allow me to have it.
shiftywalruseyes@reddit
Could do a distribution list, add all your users + add a shared mailbox as a recipient, then only delegate who you want to have access to the history of that specific mailbox. That way each user gets their own copy but you have a historical record.
Ihaveasmallwang@reddit
Then you’ll need to stick with the training. You’re not going to get rid of a read message showing as read in the mailbox.
sakatan@reddit
Nah; you want a real mailbox so that colleagues can look into what another colleague (on holiday) may have sent the customer. This centralization is crucial.
A distribution list is for one-way information flow, not customer engagement.
Agreeable-Buy-999@reddit
Before making changes, figure out what you actually need: do people need to collaborate inside the same inbox, or do they just need to receive and reply from the same address? Those are two different problems with very different solutions. That distinction will save you a lot of trial and error.
IcyOutlandishness268@reddit (OP)
company is rather small, employers can set who takes which clients inside, so for us it's more important receive and reply from the same address. but I want have all mails within one mailbox for the future. now the biggest problem is related with that the mails are read by somebody else and it's easy to confuse or miss some messeges
gptbuilder_marc@reddit
The Reply All loop from a shared mailbox is a known M365 configuration issue - it happens when employees reply directly to the mailbox email address instead of sending from it as a delegate. The fix is in how each user is set up to send from the shared address, not in the mailbox settings themselves. Make sure everyone is configured to send 'as' or 'on behalf of' the shared address rather than replying to the inbox email. Short term that stops the loop. The Microsoft rep oversold the 'just works' part on this one.
Curious201@reddit
Shared mailboxes are fine for a small team, but they need rules or they turn into chaos fast. We usually tell users: don’t mark messages unread to “assign” work, use categories or move it to a folder like In progress / Done, and if it’s going to a customer, reply from the shared mailbox only when the customer should see the shared address. If every person needs their own signature and identity, that’s a sign some of these should maybe be distribution groups or individual mailboxes, not one shared mailbox doing every job.
hight0w3r@reddit
I worked at a firm who used shared mailboxes and discovered certainly challenges due to their limitations, they rolled out the following to overcome them: Front - maybe worth a look? Not sure on costs.
BeginningCitron467@reddit
If you are in US feel free to Dm me. I offer consulting services along with MSSP services and am quite reasonable. Happy to help.