Skip to content

How to Set Up Email Forwarding in Microsoft 365

Set up email forwarding in Microsoft 365 the right way: mailbox forwarding, inbox rules, deliver-and-forward, internal vs external, and why external forwarding may be blocked.

MGMCSA Guru Team August 23, 2026 7 min read
Diagram-style cover showing a Microsoft 365 mailbox forwarding mail to an internal recipient and an external address that is blocked

Email forwarding in Microsoft 365 is one of those tasks that’s simple until it isn’t. Forwarding to a colleague down the hall works on the first try. Forwarding to a personal Gmail address silently fails, and you spend twenty minutes convinced you set it up wrong — when actually Microsoft is blocking it on purpose. The trick is knowing which forwarding method to use and understanding why external forwarding behaves differently from internal.

This guide covers the two ways to forward (admin-set mailbox forwarding and user inbox rules), how to keep a copy in the original mailbox, the difference between internal and external destinations, and the security setting that blocks external forwarding by default.

Two ways to forward, and when to use each

There are two distinct places forwarding can be configured, and they behave differently.

Mailbox forwarding vs inbox rule

Set by Mailbox forwarding: admin / Inbox rule: the user
Scope Mailbox forwarding: all incoming mail / Inbox rule: messages matching the rule
Reliability Mailbox forwarding: applies server-side always / Inbox rule: runs during rule processing
Best for Mailbox forwarding: permanent/role routing / Inbox rule: user-controlled, conditional

Mailbox forwarding is set on the mailbox object by an admin and applies to every message that arrives, no matter what. It’s the right choice for a departed employee whose mail should go to their manager, or a role address that should land with a specific person.

Inbox rules are created by the user in Outlook or OWA and can forward conditionally — only mail from a certain sender, or containing a keyword. They give the user control but depend on rule processing and can be changed or deleted by the user at any time.

Setting mailbox forwarding in the admin center

This is the most common admin task. To forward all of a user’s incoming mail:

  1. Go to the Microsoft 365 admin centerUsers → Active users.
  2. Select the user, open the Mail tab.
  3. Under Email forwarding, choose Manage email forwarding.
  4. Turn on Forward all emails sent to this mailbox and enter the forwarding address.
  5. Decide whether to tick Keep a copy of forwarded messages (this is deliver-and-forward).
  6. Save.

You can do the same in the Exchange admin center under the mailbox’s Mailbox delegation / Others settings, which exposes the same forwarding address and deliver-and-forward options.

Deliver and forward: keep a local copy

By default, forwarding moves the message on without keeping it. If you want the original mailbox to retain a copy and forward — useful when someone is covering for a colleague but the original mailbox still needs the record — enable deliver and forward.

Doing it in PowerShell

For scripting or bulk changes, Exchange Online PowerShell is faster than clicking through each mailbox.

Connect-ExchangeOnline

# Forward to an internal recipient and keep a copy in the original mailbox
Set-Mailbox -Identity "[email protected]" `
  -ForwardingAddress "[email protected]" `
  -DeliverToMailboxAndForward $true

# Forward to an EXTERNAL address (uses ForwardingSmtpAddress)
Set-Mailbox -Identity "[email protected]" `
  -ForwardingSmtpAddress "[email protected]" `
  -DeliverToMailboxAndForward $false

Note the two different parameters: ForwardingAddress takes an internal recipient object, while ForwardingSmtpAddress takes a raw SMTP address and is what you use for external destinations. To check what’s already set across your tenant:

# Find every mailbox with forwarding configured
Get-Mailbox -ResultSize Unlimited |
  Where-Object { $_.ForwardingAddress -or $_.ForwardingSmtpAddress } |
  Select-Object DisplayName, ForwardingAddress, ForwardingSmtpAddress, DeliverToMailboxAndForward

That audit query is worth running periodically on its own — unexpected ForwardingSmtpAddress values pointing to outside addresses are a classic sign of a compromised account quietly exfiltrating mail.

User-side: forwarding with an inbox rule

When the user wants to control forwarding themselves, an inbox rule is the way. In Outlook on the web:

  1. Settings → Mail → Rules → Add new rule.
  2. Name it, set a condition (or “Apply to all messages”).
  3. Add the action Forward to (or Redirect to) and enter the address.
  4. Save.

There’s a meaningful difference between Forward and Redirect: forwarding sends a new message from the user with the original attached/inlined, while redirect passes the message along keeping the original sender, so replies go back to the original sender rather than the forwarding user. Choose redirect when you want the recipient to reply to whoever sent it originally.

Internal vs external: the part that catches everyone

Forwarding to another mailbox inside your tenant is straightforward and works immediately. Forwarding to an address outside your organization — a personal account, a partner, a different company — is where things stop “just working.”

Microsoft 365 blocks automatic external forwarding by default. This isn’t a bug. Attackers who compromise an account frequently set up silent external forwarding to siphon off a copy of everything the victim receives. To shut that down, the default outbound anti-spam policy stops automatic external forwarding for everyone unless an admin explicitly allows it.

To permit external forwarding when it’s genuinely needed, adjust the outbound spam filter policy in the Defender portal (Email & collaboration → Policies & rules → Threat policies → Anti-spam → Outbound), where the Automatic forwarding setting controls whether forwards are blocked (default/automatic) or allowed. You can scope a separate outbound policy to only the users who should be allowed to forward externally.

Troubleshooting external forwarding that won't flow

  • Confirm the forwarding address itself is correct (typo check)
  • Check the outbound anti-spam policy's automatic forwarding setting
  • Verify the affected user isn't caught by a default block policy
  • Run a message trace to see whether mail is held or rejected
  • Confirm the destination domain isn't rejecting the forwarded mail (SPF/DMARC)

A note on forwarding and security

Because external forwarding is such a reliable exfiltration trick, the safe default is to leave it blocked and only open it where there’s a real business need. If you’re tightening this up after finding rogue forwards — or just hardening a tenant — our guide on stopping auto-forwarding of emails in Microsoft 365 walks through locking it down and catching the inbox rules attackers hide.

When a forward involves SPF, DKIM, or DMARC on the receiving end, the destination domain may reject mail that appears to come from your domain via the forward. That’s a deliverability issue on the other side, separate from whether Microsoft 365 lets the forward out.

Wrapping up

Pick mailbox forwarding for permanent, admin-controlled routing and inbox rules for flexible, user-driven forwarding. Turn on deliver-and-forward when the original mailbox still needs the message. Internal forwarding works out of the box; external forwarding is blocked by default as an anti-exfiltration measure, so expect to allow it deliberately through the outbound spam policy when there’s a real need. And audit your tenant’s forwarding settings now and then — unexpected external forwards are often the first sign of a compromised account.

If forwarding is part of routing mail for a shared role or a departed user, you may also want to look at tracing a message in Exchange Online to confirm where forwarded mail actually ends up.

Frequently asked questions

What is the difference between mailbox forwarding and an inbox rule?

Mailbox forwarding is set by an admin on the mailbox itself and applies to all incoming mail regardless of which client the user opens. An inbox rule is set by the user in Outlook or OWA and only runs while the mailbox is processing rules. Mailbox forwarding is more reliable for permanent setups; inbox rules are flexible and user-controlled.

How do I keep a copy of forwarded email in the original mailbox?

Use the deliver-and-forward option. When you set mailbox forwarding in the admin center, tick the box to keep a copy of forwarded messages, or in PowerShell set DeliverToMailboxAndForward to $true. Without it, forwarded mail leaves the mailbox and isn't retained locally.

Why is my external email forwarding not working?

By default, Microsoft 365 blocks automatic external forwarding through the anti-spam outbound policy to prevent data exfiltration from compromised accounts. The forward is configured correctly but the mail is held. An admin has to allow external forwarding in the outbound spam policy for it to flow.

Can I forward email to multiple addresses in Microsoft 365?

Mailbox forwarding sends to a single forwarding address. To send to several recipients, point the forward at a distribution group or mail-enabled security group that contains those addresses, or use inbox rules and transport rules for more complex routing.

Does forwarding work for a mailbox that has no license?

A user mailbox needs a license to function. Shared mailboxes can forward without a license as long as they stay under the size limit, which makes them a common way to route mail for a departed user or a role-based address to an active person.

Sources & further reading

Official vendor documentation referenced while writing this guide.

MG

MCSA Guru Team

IT & Systems Administration

We are working IT pros and system administrators who spend our days in Windows Server, Microsoft 365, and the wider Microsoft stack. MCSA Guru is where we write down the fixes and walkthroughs we wish we had found the first time.

MCSA Guru provides independent, educational IT guidance. Microsoft, Windows, Windows Server, Microsoft 365, Exchange, and Microsoft Teams are trademarks of Microsoft Corporation; Docker is a trademark of Docker, Inc. MCSA Guru is not affiliated with or endorsed by Microsoft or Docker. Always test changes in a safe environment before applying them in production.

Related guides

Fixing something right now?

Jump straight into the guide library or search for the exact error or task you are dealing with.