Choose for the workflow
An alias adds an address to an existing mailbox. A shared mailbox provides a separate workspace. Send As is a sending permission, not a mailbox or alias. An alias may suit one person using two brands. A team handling support@example.com should usually use a shared mailbox with named delegates.
Start with three questions: who receives replies, who needs to see sent messages, and who takes over during an absence? An address that works today can become a continuity problem if it belongs to an employee’s personal mailbox.
Aliases do not create separate workspaces
Messages to aliases arrive in the same mailbox. Aliases have no independent folders, quotas, or permissions. An alias cannot give someone access only to billing messages without exposing the rest of the mailbox.
Add and verify domains in Microsoft 365 before assigning their addresses. Each address must be available. billing@example.com and billing@example.net can share a local part, but decide whether they should share history. The Exchange Alias parameter is not the SMTP address collection.
Outlook clients: test the exact scenario
Microsoft documents sending from aliases in Outlook on the web after SendFromAliasEnabled is enabled. New Outlook also has sending-address settings; an unexpected SendAddressDefault can select a secondary address.
Do not promise identical behavior across clients. Alias documentation distinguishes web replies from Outlook desktop replies. Record version, build, channel, and platform for classic Outlook, Mac, iOS, and Android, then test new messages, replies, and forwarding. Shared mailbox support does not prove support for sending from its aliases. Use the web as the documented reference for the alias pilot.
Shared mailbox permissions and licensing
Full Access allows reading and managing content but does not grant sending permission. Send As presents the mailbox as sender; Send on Behalf identifies the delegate acting for it. Grant only what the workflow requires.
A shared mailbox can hold 50 GB without its own license; delegates need licensed Exchange Online mailboxes. Larger storage, archiving, Litigation Hold, and some compliance or security capabilities require specific licensing checks. Keep direct sign-in blocked on the associated account; each person uses their own identity.
Fictional example: Lea and Sam handle support@example.com with Full Access and Send As, without administrative roles. Their manager reviews membership quarterly and at departures. A shared mailbox is not a ticketing system: define how to avoid duplicate replies.
Read-only PowerShell inventory
Use an MFA-authenticated Exchange Online PowerShell session with RBAC rights for the required reads. Global Administrator is not the default requirement. Addresses below are fictional. Access denied does not mean configuration is absent.
Record the initial SendFromAliasEnabled value, addresses, and delegations before changes. Group-based permissions also require checking group membership. This block does not change the tenant.
# Read-only, after Connect-ExchangeOnline
Get-OrganizationConfig | Select-Object SendFromAliasEnabled
Get-Mailbox 'support@example.com' | Select-Object PrimarySmtpAddress,EmailAddresses,GrantSendOnBehalfTo,MessageCopyForSentAsEnabled,MessageCopyForSendOnBehalfEnabled
Get-MailboxPermission 'support@example.com'
Get-RecipientPermission 'support@example.com'
Get-MailboxMessageConfiguration 'lea@example.com' | Select-Object SendAddressDefaultChanges: scope and rollback
Enabling SendFromAliasEnabled affects the organization, not just a pilot user. Approve that scope through your internal change process, communicate it, and check existing dependencies. Then configure selectable addresses in Outlook on the web and send test messages.
For a shared mailbox, configure sent-item copies for the sending mode used. The following settings are separate changes. Do not apply them to every mailbox without inventory. Rollback means restoring recorded original values; disabling the tenant feature can affect existing alias users. Do not delete an address to undo a sending preference.
# CHANGES: record original values before running individually.
Set-OrganizationConfig -SendFromAliasEnabled $true
# Shared mailbox copies; choose the modes actually used.
Set-Mailbox 'support@example.com' -MessageCopyForSentAsEnabled $true
Set-Mailbox 'support@example.com' -MessageCopyForSendOnBehalfEnabled $trueReplies, attribution, and multiple domains
Send to a controlled external recipient and reply from that recipient. Inspect From, Reply-To, the actual received address, and the mailbox receiving the response. Repeat per domain and client. Signatures and automatic replies should match the intended brand.
Shared sent items help coordination but do not replace audit logs. Send As hides the delegate in the normal recipient presentation. Investigations should correlate available audit evidence, timestamps, mailbox, and message identifiers. Evidence availability depends on configuration, licenses, and retention.
Validate SPF, DKIM, and DMARC for each sending domain and legitimate source. Choosing an alias or shared mailbox does not itself fix domain authentication or deliverability.
Validate before expanding
Test initial sending, replies, forwarding, sent-item copies, substitute access, denial for an unauthorized user, and behavior after delegate removal. Keep results without unnecessarily retaining message contents.
If Full Access works but sending fails, check Send As or Send on Behalf. If copies are missing, inspect mailbox settings. If an unexpected address appears, inspect SendAddressDefault and the client. Propagation delay is possible; avoid repeated changes while diagnosing.
For teams, a shared mailbox is generally easier to hand over. For an additional identity owned by one person, an alias stays lightweight. Microsoft 365 consulting can validate permissions, domains, and retention; this guide does not replace a complete assessment.