Microsoft's email stack is built for one organization at a time. Inside a single company it's powerful, but the moment you're running two or three businesses through it, you start fighting the grain. Adding a second account, sending as a shared mailbox, keeping signatures and identities straight across tenants: each is solvable, and none of it feels designed for the person doing all of it at once.
This is a practical guide to configuring Outlook and Microsoft 365 cleanly across multiple businesses, where the built-in tools take you, and where you'll want something on top to keep the businesses genuinely separate.
Most people running several businesses on Microsoft end up in one of these arrangements.
Multiple Microsoft 365 tenants. Each business has its own organization, its own domain, its own billing. This is the cleanest separation at the account level and usually the right structure. The cost is that you're now signing into multiple tenants and switching between them constantly.
One tenant, multiple domains and shared mailboxes. You run several brands under a single Microsoft 365 organization, using added domains and shared mailboxes like info@brandtwo.com. Cheaper and fewer logins, but the businesses are now entangled inside one tenant, and separation becomes a matter of discipline rather than structure.
A mix. In practice most founders have a primary tenant plus a couple of other accounts bolted on, which is exactly where Outlook's account handling starts to feel like a compromise.
Outlook supports multiple accounts, so add each business's mailbox rather than forwarding everything into one. Forwarding gets mail to you but leaves you to fix the From address on every reply, which is where the wrong-sender mistakes come from. Adding the accounts keeps each identity real.
For shared mailboxes within a tenant, Microsoft 365 lets an admin grant Send As permission, so you can send as info@brandtwo.com rather than from your personal account with that brand bolted on. Configure this deliberately for any address that needs to send but doesn't warrant its own full account. Get the permission right and the recipient sees the correct brand; get it wrong and your personal name leaks onto the brand's mail.
Outlook ties signatures to accounts, so set a distinct signature for each business and confirm the correct one attaches when you switch. This is a small thing that quietly signals carelessness to a client when it's wrong, the right brand's reply carrying another brand's footer.
If you want to connect these mailboxes to other tools, check each tenant's IMAP and authentication settings, since Microsoft's modern authentication and admin policies affect what external clients can connect and how. Some tenants restrict basic IMAP, so you may need app-level access configured by the admin.
Configured well, Microsoft handles the accounts. What it doesn't do is treat each business as its own focused context. Outlook's model is a list of accounts and folders in a sidebar, and the work of staying in one business at a time falls to you.
The result is the familiar set of frictions. You're switching accounts manually all day. A reply occasionally goes out from the wrong account because the right one wasn't selected. Every business's mail shares the same visual space, so focusing on one means ignoring the others by willpower rather than by design. None of these are Microsoft failing at its job; they're Microsoft doing a different job than the one a multi-business operator needs.
What closes the gap is a dashboard that sits on top of your Microsoft accounts and organizes by business rather than by account. Each business becomes its own context, with its own view of incoming and sent mail and a sending identity locked to that context, so a reply in one business cannot go out as another.
This is what Cereal does. It connects to your Microsoft 365 and Outlook mailboxes over standard protocols, alongside any other providers you use, and gives each business its own bowl. Mail routes into the right bowl by the address it was sent to, so sorting is automatic. You see every business at a glance on one screen without the accounts blending, and your reply identity comes from the bowl you're in rather than an account dropdown. If you also run businesses on Google, our guide to Google Workspace across multiple companies covers that side, and Cereal handles both in one place.
Microsoft gives you the accounts and the permissions. The piece it leaves out is keeping each business in its own lane without constant manual switching, and that's the piece worth adding.