How to Forward Just One Sender’s Emails from a Shared Mailbox in Microsoft 365

A team member wants emails from one specific outside sender to come straight to their personal inbox, but those emails arrive in a shared mailbox. Mailbox forwarding is the wrong tool. A targeted mail flow rule is the right one. Here is the safe way to set it up in Microsoft 365.

Published 2026-06-08 by TechNet New England

A common Microsoft 365 request goes like this. Your team has a shared mailbox where all customer or partner emails land. One outside sender (a vendor, a chamber, a newsletter, a regulator) writes regularly, and one specific team member is the right person to act on those messages. You want their emails to land in that team member's personal inbox automatically. You do not want every other email in the shared mailbox to be forwarded.

The instinct is to open the shared mailbox in the admin center and turn on Email forwarding. That is the wrong tool for this job.

Why mailbox forwarding is the wrong choice

Mailbox forwarding is a blunt instrument. When you enable it on a mailbox, every email that arrives in that mailbox is forwarded to the destination address. There is no sender filter, no subject filter, no recipient filter. If you turn on forwarding for the shared mailbox to send to one team member, that team member will receive a copy of every customer email, every internal notification, every vendor message, every newsletter, every spam-marginal message that lands in the shared mailbox.

Mailbox forwarding also conflicts with how shared mailboxes are designed. A shared mailbox is meant to be a team workspace, not a relay. Microsoft documents the configuration for mailbox-level email forwarding in Configure email forwarding for a mailbox, but the right tool for conditional forwarding is a mail flow rule, not mailbox forwarding.

The right tool: an Exchange Online mail flow rule

Exchange Online mail flow rules (also called transport rules) let you describe a condition ("if a message is from sender X to recipient Y") and pair it with an action ("then add a recipient, redirect, or BCC"). The rule fires only when the condition matches. Every other message hitting the shared mailbox is unaffected. Microsoft's documentation for mail flow rules and how their conditions and actions work is at Mail flow rules (transport rules) in Exchange Online and Conditions and exceptions for mail flow rules.

This is the pattern you want. Sender filter plus recipient filter plus a delivery action.

Step-by-step setup in Exchange Admin Center

Use this approach if you prefer a graphical setup. Replace the example addresses with your real ones.

  1. Sign in to the Exchange Admin Center.
  2. In the left navigation, go to Mail flow, then Rules.
  3. Select Add a rule, then Create a new rule.
  4. Name the rule something clear, for example: Forward Vendor X emails from shared inbox to team member.
  5. Under Apply this rule if, set two conditions:
    • The sender > is this person and pick or type vendor@example.com (the specific outside sender).
    • The recipient > address includes any of these words and enter shared@yourcompany.com (the shared mailbox the email is arriving at).
  6. Under Do the following, choose one of these delivery actions:
    • Add recipients > to the Bcc box and enter the team member's address. This is the cleanest option in most cases. The outside sender does not see the team member added. The shared mailbox still gets the message. The team member also gets a copy.
    • Add recipients > to the To box if you want the team member visibly added as a recipient. The outside sender will see them on future replies.
    • Redirect the message to the team member only, if you want the shared mailbox to stop receiving these specific messages entirely. Use this with caution because once the rule fires, the shared mailbox no longer has the message.
  7. Set the Severity and Mode of the rule. Leave Severity on Not specified unless you have policy reasons to set it. Set Mode to Enforce when you are ready for the rule to take effect. Use Test with policy tips or Test without policy tips if you want to verify the rule fires correctly before enabling enforcement.
  8. Save the rule.

The rule takes effect within a few minutes. Test it by sending a message from the outside address to the shared mailbox.

PowerShell version

If you manage Microsoft 365 by script or want a repeatable deployment for multiple tenants or rules, do it in PowerShell.

Connect-ExchangeOnline

New-TransportRule `
  -Name "Forward Vendor X emails from shared inbox to team member" `
  -From "vendor@example.com" `
  -SentTo "shared@yourcompany.com" `
  -BlindCopyTo "teammember@yourcompany.com"

The full parameter reference is in New-TransportRule (ExchangePowerShell).

If you want the team member visibly copied rather than BCCed, swap -BlindCopyTo for -CopyTo. If you want the message redirected to the team member only and removed from the shared mailbox path, use -RedirectMessageTo instead.

New-TransportRule `
  -Name "Forward Vendor X emails from shared inbox to team member" `
  -From "vendor@example.com" `
  -SentTo "shared@yourcompany.com" `
  -CopyTo "teammember@yourcompany.com"

To connect to Exchange Online PowerShell in the first place, follow Microsoft's setup steps in Connect to Exchange Online PowerShell.

Copy, BCC, or Redirect: which to use when

The three delivery actions look similar but behave differently. Choose based on what you want the shared mailbox and the outside sender to see.

Action Shared mailbox still gets message Outside sender sees team member added Best for
Add to To (CopyTo) Yes Yes When you want the team member visible and the outside sender to reply to all going forward
Add to Bcc (BlindCopyTo) Yes No Most cases. Quietly route a copy to the team member without changing how the conversation looks to the outside sender.
Redirect No Not applicable When the shared mailbox should not see these messages at all. Use carefully. Once redirected, the shared mailbox has no record.

If unsure, default to BCC. It is the least intrusive and preserves the shared mailbox as the system of record.

Common mistakes to avoid

Mistake 1: Enabling mailbox forwarding on the shared mailbox.
Forwards every email. The team member's inbox fills with noise and the shared mailbox loses its team-workspace function.

Mistake 2: Forgetting the recipient condition.
A rule that filters only by sender will fire on any message from that sender no matter where it lands in the tenant. Always include the recipient condition to scope the rule to the shared mailbox.

Mistake 3: Using the team member's user mailbox forwarding instead.
Setting forwarding on the team member's mailbox does not help here. The message arrives at the shared mailbox, and the team member's mailbox is not involved unless you copy them into the delivery.

Mistake 4: Skipping the test mode.
Mail flow rules can have unintended interactions with other rules in the tenant. Set the new rule to test mode first if you are running other rules. Microsoft describes test mode in Mail flow rule procedures in Exchange Online.

Mistake 5: Not documenting the rule purpose.
Use the rule name and the optional Comments field to explain why the rule exists, when it was created, and who owns the request. Six months from now, someone will need to know.

Validation

After saving the rule:

  1. Send a test message from the outside sender's address (or a quick mock that resembles it) to the shared mailbox.
  2. Check the shared mailbox: the message should arrive normally.
  3. Check the team member's inbox: a copy should appear (or, if you used Redirect, the message should appear only here).
  4. Open the message in the team member's mailbox and inspect the headers. Look for the X-MS-Exchange-Organization-TransportRuleHit or similar header indicating which rule fired. Microsoft documents message header fields and tracing in Message trace in the modern Exchange admin center.

If the rule did not fire, check that:

Bottom line

For "forward emails from this one sender to that one person," do not use mailbox forwarding. Build a mail flow rule with two conditions (sender and recipient) and a delivery action (BCC is the safest default). The rule fires only on matching messages, the shared mailbox keeps working normally, and the team member gets the right emails without the noise.

References

  1. Mail flow rules (transport rules) in Exchange Online (Microsoft Learn)
  2. Conditions and exceptions for mail flow rules in Exchange Online (Microsoft Learn)
  3. Actions for mail flow rules in Exchange Online (Microsoft Learn)
  4. Manage mail flow rules in Exchange Online (Microsoft Learn)
  5. New-TransportRule (ExchangePowerShell) (Microsoft Learn)
  6. Connect to Exchange Online PowerShell (Microsoft Learn)
  7. Configure email forwarding for a mailbox (Microsoft Learn)
  8. Message trace in the modern Exchange admin center (Microsoft Learn)
  9. Create a shared mailbox (Microsoft Learn)

If you need help building or auditing mail flow rules across your Microsoft 365 tenant, contact TechNet New England at info@technetnewengland.com or (413) 459-9663.