Content reviewed: 12 October 2026
You have two brands and want to handle email in Microsoft 365. Decide what should be shared: inbox, people’s access, replies and archive. The domain in an address is only one part of the design. An alias can route several addresses into one mailbox; separate mailboxes keep workstreams apart.
A domain is not another work account
Microsoft supports multiple domains in one tenant, typically up to 5,000. Adding a domain does not create a user account or its licences, nor migrate historical mail. Decide whether the brand should share the organisation’s administration and security environment or needs a separate architecture.
| Requirement | Model | Result |
|---|---|---|
| Shared inbox and same people | Alias on an existing mailbox | Another address without separate history |
| Separate team workstream and replies | Shared mailbox | Dedicated folders and delegated access |
| Personal account and user services | Licensed user | Separate identity and required entitlements |
| Automated application sending | Supported application model | Assess protocol, authentication and service separately |
Aliases deliver to the same mailbox
Exchange Online proxy addresses let one mailbox receive mail at multiple addresses. An alias does not create separate folders, an independent archive or different delegates. If another team should see only its workstream, a different domain name is insufficient.
A hypothetical owner manages two brands alone. If shared history is acceptable, both addresses could be aliases on the owner’s mailbox. Handing just one brand to a colleague later creates a problem with common content and access. Future handover can justify separate mailboxes at the start.
Receiving at an alias does not prove the sender identity
Exchange Online has an organisation setting called SendFromAliasEnabled. When enabled, aliases are not rewritten to the primary SMTP address, and compatible clients support sending and replying from aliases. It can affect message behaviour even in clients without newer support. It is not an isolated switch for one brand.
Test both a new message and a reply in the actual clients. Check the address visible to an external recipient, signature and automatic reply. Do not extend a web Outlook test result to mobile, desktop or accounting software without verification. Sending from an alias still does not create a separate workstream.
Shared mailboxes use delegation
A shared mailbox can hold up to 50 GB without its own Exchange licence in the basic scenario. Every accessing employee needs their own licensed Exchange Online mailbox and delegated access. Keep direct sign-in to the shared mailbox account blocked. Larger primary storage, archive, hold and advanced features have separate licensing rules.
| Permission | Allows | Does not imply |
|---|---|---|
| Full Access | Open the mailbox and work with its content | Sending rights |
| Send As | Send as the shared mailbox | Read access to mailbox contents |
| Send on Behalf | Send with the delegate shown on behalf of the mailbox | The same sender display as Send As |
Microsoft explains these distinctions when creating a mailbox. Decide whether brand-support replies should appear from the brand or from a person on its behalf. Test the actual client and mailbox visibility in the directory too.
Configure shared reply history
The configuration guide says messages sent from a shared mailbox are saved by default in the sending person’s Sent Items. Configure the shared mailbox’s Sent items options for the team history you need. Send as a delegate, then verify another team member can find the message.
These are separate tests: the recipient sees the correct branded reply, and the team retains its history. Passing the first does not prove the second. Repeat both for each mailbox and sending method.
An application is not another employee
Invoice software has different requirements from a person reading an inbox. Do not automatically create shared credentials or assume human delegation solves unattended sending. Establish the vendor’s supported authentication and service, and access to the required mailbox and protocol. Confirm licensing and security for that actual model.
Prepare recipients before changing mail DNS
The domain setup guide requires recipients and mailboxes before MX cutover. Domain ownership verification and mail routing are different steps. Changing MX does not move old messages or create missing recipients. When moving between tenants, check domain dependencies and the coexistence plan too.
- 01
Inventory all addresses
Users, aliases, team mailboxes, groups, applications and historical mail
- 02
Choose models and prepare recipients
Permissions, licences, signatures, rules and shared Sent Items
- 03
Verify the domain and senders
DNS ownership; SPF, DKIM and DMARC for the domain and services in use
- 04
Switch MX under the plan
Confirmed readiness, timing and recovery procedure
- 05
Test the complete workflow
External delivery and replies, clients, delegates, team history and applications
Use one applicable SPF TXT record for the domain. Microsoft recommends adding new values to existing SPF rather than creating a second independent record. Inventory CRM, invoicing and other senders that will continue after migration.
For conversion after an employee leaves and retaining the mailbox account, see A leaver’s mailbox. Choosing brand addresses does not replace that offboarding procedure.
Frequently asked questions
Does every extra domain need a licence?
Adding the domain alone does not. Licensing follows accounts, mailboxes and features used.
Can aliases separate people’s access to brands?
No. An alias is another address on the same mailbox. Separate content and delegation need a different model.
Is Full Access enough to send as the brand?
No. Check Send As or Send on Behalf according to the required sender display.
Will the team automatically see every sent reply?
Not necessarily. Configure shared-mailbox Sent Items and verify the actual sending method.








