Does Outlook Support BIMI?

Short answer: no, not for standard inbound mail, as of 2026. If a meaningful share of your recipients read mail through Outlook.com, Hotmail, or a corporate Microsoft 365 mailbox, a BIMI logo you've set up will not appear for them, no matter how correctly your VMC, DMARC, and DNS record are configured.

That answer surprises people who've already done the BIMI work elsewhere and assumed it would carry over. It's worth unpacking why Microsoft is the exception, what it's doing instead, and what that means for whether a VMC is still worth it if Outlook makes up a large slice of your audience.

Why Outlook doesn't show your BIMI logo

BIMI is an open standard, published through the AuthIndicators Working Group, and adopted independently by each mailbox provider that chooses to support it. Gmail, Apple Mail, Yahoo, AOL, and Fastmail have all implemented it, in each case reading the same DNS record and the same certificate. Microsoft has not adopted it for its mainstream inbound mail flow: Outlook.com, Hotmail, Exchange Online, and Microsoft 365 mailboxes generally.

This isn't a bug or a partial rollout you're waiting on. Microsoft has been public about pursuing its own approach to branded sender identity rather than adopting BIMI as published. So a valid BIMI record, a correctly issued VMC, and DMARC at full enforcement will do everything they're supposed to at Gmail or Apple Mail, and produce nothing visible at an Outlook mailbox.

Remember that BIMI display depends on the recipient's mailbox provider, not the mail client they happen to open it in. Someone reading a Gmail account through the Outlook desktop app still gets Gmail's BIMI behavior for that message, because the mailbox is Gmail's. Someone reading a Microsoft 365 mailbox through any client, including Apple Mail on an iPhone, gets Microsoft's behavior, which today means no BIMI logo. It's the mailbox that decides, not the window it's viewed through.

What Microsoft does instead

Microsoft has explored and piloted its own sender-verification and branding mechanisms at various points, generally under its own naming and its own rules, separate from the BIMI standard and not interchangeable with a VMC or CMC. As of 2026 there is no general, publicly available equivalent to BIMI's logo-in-the-inbox behavior across ordinary Outlook.com and Microsoft 365 mail.

If you're specifically chasing brand display in Outlook, there currently isn't a reliable purchasable path to it the way there is with a VMC and Gmail, or a VMC and Apple Mail. That's worth knowing before you spend time hunting for an Outlook equivalent of the BIMI setup you've already done elsewhere; as of this writing, there isn't one to find.

Does that mean a VMC is wasted on an Outlook-heavy list?

No, and this is the part worth getting right before you write off the whole project. A VMC and a working BIMI record are not Outlook-specific investments that fail if Outlook doesn't cooperate. They're standards-based, and every other BIMI-supporting provider reads the same certificate and the same record. If your list has a mix of Gmail, Apple Mail, Yahoo, and Microsoft addresses, the certificate does real work for the non-Microsoft portion regardless of what Microsoft does.

What changes is your expectation of total reach, not whether the project is worth doing. If your list is 70% Microsoft 365 and 30% Gmail, a VMC is still fully functional, it just delivers visible value to that 30%, not the whole list. That's a very different calculation from "BIMI doesn't work," and it's the distinction that should actually drive the decision.

How to work out how much this matters to you

The honest first step, before committing to a VMC, is understanding your own audience mix. A few ways to get a real number instead of a guess:

• Check your ESP's engagement data. Most email service providers report opens by client or by provider, which gives you a rough split between Gmail, Outlook, Apple Mail, and others.
• Look at your recipient domains. If you have visibility into the domains your list sends to, a rough manual sample of common domains (gmail.com, outlook.com, hotmail.com, corporate domains that route through Microsoft 365) will approximate the split even without dedicated tooling.
• Weigh B2B versus B2C. As a rule of thumb, B2C and consumer lists skew toward Gmail and Apple Mail, both of which support BIMI. B2B lists, especially ones talking to larger enterprises, skew toward corporate Microsoft 365, which currently does not.

None of this needs to be precise to be useful. Even a rough split tells you whether you're looking at a program that reaches most of your list or a smaller slice of it, and that should shape how much you invest and how you talk about the payoff internally.

The comparison

If Outlook is a large share of your list and you'd still like some visible brand presence there, note that this is a different problem from BIMI, and there isn't currently a direct purchasable equivalent. It's worth watching for Microsoft to move on this, since large mailbox providers have shifted their authentication requirements before (their own enforcement of SPF and DKIM alignment for bulk senders is a recent example), but there's nothing to configure toward it today.

What we would tell you to do

Don't let "Outlook doesn't support BIMI" talk you out of a VMC if a real share of your recipients are on Gmail or Apple Mail. It talks you into being precise about who benefits, not into skipping the project. Work out your actual provider mix first, size the realistic upside against that mix rather than your full list count, and then decide.

If your list turns out to be overwhelmingly Microsoft 365 with only a small Gmail or Apple Mail presence, that's useful to know early, since it changes the calculus and might mean waiting or deprioritizing rather than moving ahead immediately. Either way, that's a decision worth making with real numbers rather than an assumption in either direction.

Signume checks your domain and talks through your realistic audience mix before you commit to anything, so you know what a VMC will and won't do for your specific list before spending on it.

Frequently asked questions

Does Outlook show BIMI logos? No, not for standard inbound mail as of 2026. Outlook.com, Hotmail, Exchange Online, and Microsoft 365 mailboxes do not render BIMI logos. Microsoft has pursued its own approach instead of adopting the BIMI standard.

Is there a Microsoft equivalent to a VMC? Not one that's generally available for standard inbound mail as of 2026. Microsoft has explored proprietary branding and verification approaches, but there is no current purchasable path to logo display in ordinary Outlook mail comparable to a VMC.

If I use Outlook desktop app to read my Gmail, will I see the logo? Yes. BIMI display depends on the mailbox provider, not the client. A Gmail mailbox read through the Outlook app still shows Gmail's BIMI behavior for that message.

Is a VMC worth it if most of my recipients use Microsoft 365? It depends on what share of your list is on non-Microsoft providers. The certificate still works fully for any Gmail, Apple Mail, Yahoo, or Fastmail recipients you have; it simply won't show anything to Microsoft 365 recipients. Check your actual provider mix before deciding.

Will Microsoft add BIMI support eventually? There's no public commitment either way as of 2026. Large providers have changed authentication requirements before, so it's worth monitoring, but there's nothing to configure toward it today.