Overview

This article walks through creating an Exchange mail-flow rule that redirects mail sent to your support address (e.g. support@yourcompany.com) to a Scrambl inbox. The rule runs in your tenant and applies to all inbound messages matching the recipient.

You need Exchange Administrator (or higher) permissions.

Who can do this

  • Required access: an access level that includes Tickets - Full Access.
  • Default access levels that include it: System Administrator.
  • Owners and admins: always allowed. Workspace owners and admins are not limited by access levels.
  • You also need admin access to the Microsoft 365 or Exchange admin center.
  • Personal accounts: Not available. This is a work feature, so it is hidden in personal (family) spaces.

Owners and admins review and change access levels in Settings → Administration → Members → Access levels.

Before you start

Step-by-step

  1. Sign in to the Microsoft 365 Admin Center.
  2. Open the Exchange admin center → Mail flow → Rules.
  3. Click + Add a rule → Redirect messages… and name it Support emails to Scrambl.
  4. Set Apply this rule if… to The recipient address includes… and add your address (e.g. support@yourcompany.com).
  5. Set Do the following… to Redirect the message to… and paste the Scrambl inbox address.
  6. (Optional) Add an exception such as "Except if the sender is internal" to prevent loops if internal teammates accidentally email the support address.
  7. Set the rule mode to Enforce, click Save.
  8. Send a test email to your support address and confirm a ticket appears in Scrambl.

Choosing redirect vs. forward

Use Redirect (not Forward or BCC). Redirect keeps the original sender as the From address, which is how Scrambl correctly identifies the requester. Forward and BCC rewrite the sender or duplicate delivery, which breaks the requester record.

Troubleshooting

SymptomLikely cause
Test email doesn't create a ticket.The recipient condition doesn't match — check casing and that the rule is enforced, not in test mode.
Ticket shows your own Exchange tenant as the requester.You configured Forward instead of Redirect. Recreate the rule using Redirect the message to….
Replies from Scrambl get filtered by your tenant.Add the Scrambl outbound domain to your accepted-senders or anti-spam allow list.