Collaboration & Communication Ecommerce

How an online retailer turned paid inboxes into free shared mailboxes

A small ecommerce team turned its shared team addresses into proper free shared mailboxes. They gained full visibility on every reply, and saw a saving on the very next bill.

An online retailer
Ecommerce
8 users
Same day
At a glance

MStack360 turned an online retailer's info, sales, and support addresses into proper free shared mailboxes. The work was done inside the Microsoft 365 plan they already paid for. Each of the eight team members then got their own access in Outlook. The shared password was gone, and every reply became visible to the whole team. Removing the paid licenses showed up as a saving on the very next bill.

  • Three team addresses converted to free shared mailboxes. The business stopped paying licenses on inboxes that never needed one
  • Per person access in place of one shared password. Each member signs in as themselves, and access is removed in seconds when someone leaves
  • Every message in and out sits in one place, so replies are never missed or doubled up
What this story covers
  1. The hidden cost
  2. How we fixed it
  3. One address, whole team
  4. What we set up
  5. The payoff
The Challenge

Paying for inboxes that should have been free

This online retailer ran the business from a handful of team addresses. Customers wrote to info@, leads landed in sales@, and order questions went to support@. The trouble was how those addresses had been built. Each one was set up as a normal user account with a paid license, and the whole team logged in with one shared password.

That created two quiet problems at once. Nobody could see who had answered what, so replies got missed or doubled up. The shared password was a security risk every time someone joined or left. On top of that, the business was paying for licenses on addresses that never needed one.

A shared mailbox in Microsoft 365 is free when it is set up properly. They were paying full price for three.

What They Needed

One inbox each that the whole team could see

  • One address each for info@, sales@, and support@ that the whole team could read and answer
  • Every reply visible to the team, with nothing trapped in one person's inbox
  • An end to the shared password, with access controlled per person
  • A way to stop paying for inboxes that should be free
Our Approach

Scoped on a call, then fixed live while they watched

Free intro call

We listened to how the team used each address, then offered to fix it right there while they watched. No paperwork, no waiting. We checked which addresses were licensed today, how many people needed each one, whether anyone sent externally, and how much mail history had to be preserved.

Converted to proper shared mailboxes

We turned each paid account into a free shared mailbox inside their existing Microsoft 365 plan. Send as and send on behalf were set up so replies go out from the right address. The full mail history stayed with the mailbox, so nothing was lost in the switch.

Granted access per person

Each team member got the mailbox in their own Outlook, signed in as themselves. No more shared password, and access can be removed in seconds when someone leaves.

Quick walkthrough

A short tour so everyone knew where the mailbox appears in Outlook and on their phones. We also showed how a reply now leaves from the shared address rather than a personal one.

One address, the whole team

How a shared mailbox routes to everyone at once

A shared mailbox is a single address that several people open from inside their own Outlook. There is no separate login and no shared password. Everyone reads and replies from the same place, and every message in and out sits in that one mailbox. Send as makes sure replies leave from the shared address, not a personal one. Here is how info@ fans out to the team.

In plain terms

It is one email address that several people open from their own Outlook. There is no separate sign in and no license to buy. It suits team addresses like info@, sales@, and support@. Everyone sees the same mail, and replies are shared across the team.

We do this kind of quick win inside the plan you already own as part of our Microsoft Office 365 Support. Often it is the small free fix that starts a longer relationship.

Quick reference

Shared mailbox vs the other Microsoft 365 options

A bonus aside, not specific to this client. Tap a tab to compare four common Microsoft 365 ways to handle a team or extra address.

Shared mailbox

What it is
A mailbox several people open from their own Outlook. Sign in is disabled by default.
Best for
A team that answers one address together, like info@, sales@, or support@.
Who can reply / send
Members get Full Access plus Send As or Send on Behalf. Sent items are shared.
Cost & licensing
No license needed up to 50GB. A license is only needed for larger storage, archive, or legal hold.
Choose this when a team shares an inbox and you want shared history at no extra cost.

Distribution list

What it is
A list that forwards an incoming message to a group of people. Each gets a copy in their own inbox.
Best for
One way announcements or broadcasts to a group. No shared storage, no central history.
Who can reply / send
It is one way. Each person replies from their own inbox, not from a shared place.
Cost & licensing
No license needed. There is no mailbox to store mail, only a list of recipients.
Choose this when you want to email many people at once and each should get their own copy.

Microsoft 365 Group

What it is
A membership object that gives a shared inbox plus a shared calendar, a SharePoint site, Planner, and an optional Team.
Best for
A project or team that needs collaboration beyond email. There are more moving parts.
Who can reply / send
Members share the inbox and can reply from it, alongside the shared files and calendar.
Cost & licensing
Comes with Microsoft 365. Members use their existing plans.
Choose this when a team needs shared files, calendar, and Teams, not just a shared inbox.

Alias (proxy address)

What it is
Just an extra email address added to an existing mailbox. Mail to the alias lands in that one mailbox.
Best for
One existing mailbox that also needs to receive mail at another address.
Who can reply / send
No separate inbox and no separate permissions. Sending as the alias needs extra setup.
Cost & licensing
No extra license. It rides on the mailbox it is added to.
Choose this when one existing mailbox just needs to also receive mail at another address.
What We Ran Into

The snags behind shared team addresses, all handled

One shared password across the whole team

Everyone logged into each address with the same credentials, a real risk at every join and leave.We moved to per person access so each member signs in as themselves, and access is removed in seconds when someone leaves.

Replies missed or doubled up

Nobody could see who had answered what, so messages slipped or got two replies.We converted the accounts to shared mailboxes where every message in and out sits in one place the whole team can see.

Risk of losing mail history on conversion

The team worried that converting the accounts would drop years of email.We preserved the full history with the mailbox, so nothing was lost in the switch.

Replies going out from the wrong address

Without send as set up, responses could leave from a personal address.We configured send as and send on behalf, so every reply goes out from the correct shared address.

What We Delivered

Three free shared mailboxes the whole team could see

Three free shared mailboxes

info@, sales@, and support@ now run on shared mailboxes at no extra license cost, inside the Microsoft 365 plan they already pay for.

Send as and send on behalf

The team replies from the correct address every time, with the mailbox keeping a full history of every message.

Team wide visibility

Every message in and out sits in one place the whole team can see, so nothing slips and nobody doubles up.

Clean, removable access

Access is granted per person in Microsoft Entra ID and removed in seconds, with no shared password left in play.

Results

The payoff for the team

Zero
Shared passwords across the three team addresses, with access now granted per person
8 users
With full reply visibility, so nothing slips through and nothing is answered twice
Same day
Delivery, much of it completed live on the free intro call, with a saving on the next bill

"We had no idea we were paying for inboxes that could be free, and now the whole team can finally see what is going on. You solved it while we watched."

Operations lead, an ecommerce company

The solution behind this story

Microsoft Office 365 Support

We get the most out of the plan you already pay for, from team mailboxes done right to the bigger work that follows. It is the small free win that often starts a longer relationship. No new license, and no new vendor.

Use what you already pay for Free shared mailboxes Per person access
Common Questions

What people ask about shared mailboxes

Is a shared mailbox really free?

Yes. In Microsoft 365 a shared mailbox does not need its own paid license when it is set up properly. If a paid license was sitting on one of these addresses, removing it shows up as a saving on your next bill.

Will the team lose any old emails when you convert the address?

No. The history stays with the mailbox. Everyone keeps using their own Outlook, and the shared mailbox simply appears alongside their personal one.

What happens when someone leaves the team?

Access is granted per person, not through a shared password. We remove that person's access in seconds. The address keeps working for everyone else, with nothing exposed.

Google review

"Very good service. Easily migrated our shared inboxes and email to Microsoft 365. Easy and smooth."

Mohammed IrshadGoogle review

Read more on Google

Paying for inboxes that could be free?

Let us take a quick look at your team addresses and your plan. Often the fix is free, and we can do it on the first call. That call is on us.

Book a call