Dialogue emails and the Outlook Focused Inbox

Allow-listing, SPF, DKIM and DMARC control whether a message is treated as spam they determine whether mail reaches the inbox rather than the Junk folder or quarantine.

Focused Inbox is an entirely separate mechanism. It only acts on mail that has already passed filtering and landed in the inbox. It then sorts that mail into "Focused" or "Other" using a machine-learning model based on how each individual recipient engages with a sender. An invitation from a sender your people have not corresponded with before fits the profile of automated bulk mail - exactly what the model places in "Other", at least until it has learned otherwise.

💡 Allow-listing is still worth doing - it solves a different problem. The mail flow rule below is what addresses tab placement. Both should be applied.

⚠️ Why WorkBuzz cannot apply this rule on your behalf - Exchange Online's "header firewall" automatically strips X-MS-Exchange-Organization-* headers from inbound messages arriving from outside your tenant. If WorkBuzz stamped the bypass header on our side, it would be removed at your perimeter before Outlook ever saw it. The rule must be created inside your own tenant by your IT team.

Run the following as an account holding the Organization Management or Transport Rules role:

⚠️ Case sensitivity - both the header name and the value true are case sensitive. Entering True instead of true produces a rule that saves and enables normally but has no effect. This is the most common reason the rule appears not to work.

Step 1. Go to Mail flow > Rules > Add a rule > Create a new rule

Step 2. Name the rule: Dialogue emails to Focused Inbox

Step 3. Set the condition: The sender > domain is > enter dialogue.workbuzz.com

Step 4. Set the action: Modify the message properties > set a message header

Step 5. Set the header name: X-MS-Exchange-Organization-BypassFocusedInbox

Step 6. Set the header value: true

⚠️ Case sensitivity - both the header name and the value true must be entered exactly as shown. True or TRUE will not work.

Step 7. Set the rule mode to Enforce and save.

💡 Subdomain coverage - SenderDomainIs automatically matches subdomains as well as the domain entered. Scoping to dialogue.workbuzz.com also covers the SendGrid bounce subdomains WorkBuzz uses (e.g. em52.dialogue.workbuzz.com). No wildcards or regular expressions are needed.

💡 Why not match workbuzz.com? - The apex domain covers other WorkBuzz senders including marketing, support and notification tools. Scoping to dialogue.workbuzz.com keeps the rule focused on Dialogue product mail only.

1. Case sensitivity - The header name and the value true are both case sensitive, as stated explicitly in Microsoft's documentation. A single wrong capital letter produces a rule that appears healthy but does nothing.

2. The rule is not retroactive - It only acts on messages arriving after it is enabled. Emails already sitting in "Other" will remain there. Always test with a newly received Dialogue email, not an existing one.

3. A third-party security gateway does not interfere - If your inbound mail routes through a filtering gateway (such as Symantec/MessageLabs) before reaching Exchange Online, the rule still works. Exchange Online mail flow rules run after the gateway hands the message off.

If the header is present, the bypass is active and the rule is working. If it is absent, the rule is not matching - in almost every case this is the capitalisation issue described above.

💡 Users may need to close and reopen Outlook before the change is reflected in their tab sorting.

Once the rule is live, all Dialogue emails arriving in your organisation will bypass the Focused/Other sort and land in the Focused tab. Individual users do not need to configure anything themselves. You may also wish to add dialogue.workbuzz.com to your organisation's allow-list using the sending details below - the two steps solve different problems and work well together. If the header does not appear after applying the rule, check the capitalisation of both the header name and the value true first, then confirm the rule is set to Enforce mode and that no higher-priority rule is overriding it.

Use these details if you are also adding WorkBuzz Dialogue to your allow-list.

Our sender authentication on dialogue.workbuzz.com is fully configured and can be verified independently from public DNS. We publish SPF with a hard fail (-all), sign with DKIM on 2048-bit keys, and publish DMARC at p=reject - the strictest enforcement policy available. None of this affects Focused Inbox tab placement, but it confirms that Dialogue mail is genuine and correctly authenticated at every receiving server.

Focused Inbox is a Microsoft feature, so the rule above only applies to Exchange Online. If your organisation uses Google Workspace, Gmail's Primary and Promotions tabs work differently and there is no equivalent administrative rule. Please get in touch and we will go through the options with you.

Why did our allow-list not fix the "Other" tab problem?
Allow-listing and sender authentication (SPF, DKIM, DMARC) control whether a message is treated as spam. Focused Inbox is a completely separate mechanism that only acts on mail already in the inbox, sorting it based on per-recipient engagement patterns. The two systems are independent, so a fully allow-listed sender with perfect authentication can still land in "Other". The mail flow rule in this article is what addresses tab placement.

The rule is applied and enabled, but emails are still going to "Other". What should I check?
In almost every case this is capitalisation. Check that the header name is entered as X-MS-Exchange-Organization-BypassFocusedInbox and the value as true - both are case sensitive and True will not work. Also confirm the rule is set