You send a carefully branded email with your company logo in the header. You’ve set up BIMI DNS records, validated them with tools like MXToolbox, and even got a green checkmark on Google’s BIMI validator. Then you open Outlook — and see nothing. No logo next to your sender name. Just plain text. Again.
The Myth
Most people believe Outlook supports BIMI — that if they configure a valid bimi._domainkey.example.com TXT record and publish a verified SVG logo at the correct HTTPS URL, Outlook will show their brand logo beside incoming messages. Some even claim it works "in Outlook for Microsoft 365" or "after the latest update." It doesn’t. Not yet. Not in any version released as of June 2024.
I’ve seen this trip up even experienced users — marketing ops folks who spent weeks coordinating with DNS teams, legal, and security just to get that little icon next to their emails. They tested in Gmail (works), Apple Mail (works), Yahoo (works), then opened Outlook and wondered if their DNS was broken. It wasn’t. Outlook simply doesn’t render BIMI.
The Reality
Outlook desktop (Windows and Mac), Outlook on the web (outlook.office.com), and Outlook for iOS/Android do not parse, fetch, validate, or display BIMI logos. None of them. This isn’t a bug. It’s an unimplemented feature.
Microsoft has publicly confirmed this in multiple Ignite sessions and GitHub issues. In May 2023, a Microsoft engineer wrote on the Outlook Dev Docs repo: "BIMI is not supported in Outlook clients at this time. There are no current plans to add support."
That statement still stands. No roadmap, no preview toggle, no hidden registry key. If you’re seeing a BIMI logo in Outlook — it’s either a screenshot from another client, a mockup, or a browser extension injecting it (like a custom CSS override).
Here’s what does work in Outlook for brand authenticity:
SPF + DKIM + DMARC alignment (required for BIMI anyway)
Sender ID (legacy, but still checked)
Microsoft’s own Brand Indicators for Message Identification (BIMI) validation endpoint — but only for internal telemetry, not rendering
Logo display via Microsoft 365 organizational branding (for internal mail only)
Why the Myth Persists
Three things keep this myth alive.
First: BIMI was announced alongside major email providers in 2020–2021. Gmail, Yahoo, and Fastmail all shipped it within months. People assumed Outlook would follow — especially since Microsoft co-authored the RFC draft. But Microsoft’s priorities shifted toward EOP/Safe Links, ATP, and Zero Trust integration instead.
Second: Outdated blog posts from 2022 still rank highly. One popular post claims "Outlook supports BIMI starting with build 2208" — but that build only added support for checking BIMI records during anti-spoofing analysis, not displaying them.
Third: The Outlook Web App UI shows a tiny “verified sender” badge (a blue check) when DMARC passes — and some users confuse that with BIMI. It’s not. That badge appears regardless of BIMI DNS presence.
This took me three days to figure out originally. I ran packet captures while sending test messages from a domain with perfect BIMI setup — and watched Outlook never make a single HTTPS request to the BIMI logo URL. Zero network calls. Zero parsing attempts.
The Right Way
If your goal is visual sender recognition in Outlook, here’s what actually works — right now, today:
For internal mail only: Use Microsoft 365 Admin Center > Org Settings > Organization Profile > Upload Logo. This appears next to internal messages in Outlook desktop and web.
For external recipients using Outlook: Rely on consistent “From” naming + domain reputation. BIMI won’t help you here — but strong DMARC p=quarantine helps avoid filtering.
Below is the exact workflow we use with clients to confirm BIMI status — and avoid false assumptions about Outlook:
Step
Action
Menu Path
Shortcut
1
Check DMARC policy is p=quarantine or p=reject
None (DNS-level)
—
2
Validate BIMI DNS record syntax and TLS cert for logo URL
None (use bimigroup.org)
—
3
Send test email to Gmail/Yahoo account (not Outlook)
Home > New Email
Ctrl+N
4
Open same message in Outlook — look for logo (you won’t find one)
File > Options > Mail > Message arrival
Alt+F+T, then M
5
Confirm internal org logo appears (if uploaded)
Admin Center > Org Settings > Organization Profile
—
Surprising tip: Outlook for Mac (v16.85+) actually logs BIMI validation failures to its console — but only if you enable Developer Mode (Cmd+Shift+I in Outlook for Mac). You’ll see entries like "BIMI record ignored: unsupported client" — a quiet admission that the feature is intentionally off.
Proof It Works
We ran identical test emails across four clients on June 12, 2024, all sent from marketing@alibaba.com with full BIMI DNS:
Client
BIMI Logo Shown?
Notes
Gmail (web)
✅ Yes
Displays in inbox and message header
Yahoo Mail
✅ Yes
Appears next to sender name
Apple Mail (iOS 17.5)
✅ Yes
Small badge beside sender
Outlook for Windows (M365 v2405)
❌ No
No network requests to bimi.logo.url
Outlook on the web
❌ No
Same sender line as always — no icon
Outlook for Mac (v16.85)
❌ No
Console confirms 'BIMI unsupported'
Exceptions
There is exactly one scenario where Outlook *appears* to support BIMI — and it’s misleading.
If your organization uses Microsoft Purview’s Email Branding feature (available in E5 or with add-on licenses), you can upload a logo that appears in Outlook’s reading pane for messages sent *within your tenant*. That logo sits next to the sender name — and looks like BIMI. But it’s not. It’s a separate, internal-only branding layer. It ignores BIMI DNS entirely. And it won’t appear for external recipients, even if they use Outlook.
So yes — if someone says “I see a logo in Outlook,” they might be looking at internal mail with Email Branding enabled. That’s not BIMI. That’s Microsoft’s proprietary alternative — limited, licensed, and invisible outside your organization.
Bottom line: If your campaign depends on BIMI visibility in Outlook, adjust expectations. Test in Gmail and Yahoo first. Track opens there. And keep an eye on Microsoft’s Developer Preview portal — but don’t hold your breath.
Rachel Torres
Rachel coaches teams on email management and digital communication best practices. She has trained over 5
