Does Microsoft 365 Support BIMI?

Direct Answer

As of the last verified update (mid-2026), Microsoft 365 (Outlook.com and Exchange Online) does not support the BIMI standard for displaying sender logos in the way that Gmail does. Microsoft uses its own logo verification mechanism — Brand Indicators — which operates independently of the BIMI DNS record and VMC/CMC certificate infrastructure. A correctly configured BIMI record with a VMC has no display effect in Microsoft 365 inboxes under this system. Microsoft’s support model should be verified against current official documentation before making implementation decisions.

What Microsoft 365 Uses Instead

Microsoft’s Outlook.com and Exchange Online environments have implemented their own logo display system, sometimes referred to as Brand Indicators or BIMI-adjacent. As of mid-2026, this system operates independently of the BIMI DNS record and VMC/CMC certificate infrastructure that governs display in Gmail and other BIMI-participating providers.

Microsoft’s logo display has historically been tied to their own verification process and requirements, which differ from the CA-issued certificate model used by BIMI. Organizations that have set up BIMI correctly for Gmail should not assume that configuration also activates logo display in Outlook.

Do not assume that a passing BIMI record check or an active VMC will cause logo display in Microsoft 365. The two systems are independent. Treat them as separate implementation tracks with separate requirements.

Support Status by Provider Context (June 2026)

Provider / ContextBIMI Support (as of June 2026)Notes
Gmail (Google Workspace)SupportedRequires VMC and DMARC enforcement. Blue checkmark displayed for VMC holders.
Outlook.com / Exchange OnlineNot supportedUses separate Microsoft logo display system. BIMI record has no display effect here.
Yahoo Mail / AOLSupportedEarly adopters of BIMI. VMC or CMC may be required depending on current policy.
Apple Mail (iCloud)Partial / VariableSupport has been reported in some contexts. Behavior may vary by client version and account type.
FastmailSupportedBIMI support announced and implemented as of 2024–2025.

What This Means for Implementation Planning

A BIMI setup — DNS record, VMC certificate by a trusted CA, DMARC at enforcement — delivers logo display to Gmail and other participating providers. It does not deliver logo display to Microsoft 365 inboxes under the current separation of systems. If a significant portion of your target recipients use Outlook.com or Exchange Online, separate research into Microsoft’s current logo program requirements is needed.

BIMI is still worth implementing for Gmail reach. Gmail and Yahoo Mail together represent a substantial share of consumer and business email. The absence of Microsoft 365 support limits reach but does not make BIMI implementation pointless. See Why Isn’t My BIMI Logo Showing? if logo display issues exist in Gmail specifically.

Frequently Asked Questions

Will Microsoft 365 ever support BIMI?

As of the last verified update (mid-2026), Microsoft has not made a public commitment to implementing the BIMI standard. Their logo display roadmap is controlled independently. Monitor bimigroup.org and Microsoft's Exchange blog for announcements — provider support for BIMI has expanded over time, but whether and when Microsoft may adopt the standard is not known.

Does a VMC help with Microsoft 365 logo display?

Not directly, as of mid-2026. A VMC is a CA-issued certificate tied to the BIMI infrastructure. Microsoft's logo display system operates separately and does not consume VMC or BIMI DNS records for display decisions. Check Microsoft's current documentation for their specific logo verification requirements.

My logo shows in Gmail but not Outlook. Is something broken?

No — this is expected behavior given the current state of support. Gmail reads your BIMI record and VMC; Outlook does not use that infrastructure for logo display. The two systems are separate. If your BIMI setup passes validation and displays in Gmail, nothing is broken on the BIMI side. Outlook requires a separate approach.