BIMI Support in Outlook & Microsoft 365

Is BIMI Working in Outlook and Microsoft 365 in 2026?

You send a brand-verified email with a BIMI logo—clean, consistent, professional. But when you check the inbox on Outlook for Windows, the logo doesn’t show up. You check the mobile app. Still nothing. You’re not alone.

As of 2026, BIMI support in Microsoft 365 remains patchy. It works—but only under strict conditions, and not reliably across all clients. If your logo is missing from Outlook, it’s not necessarily your fault.

BIMI is designed to help brands stand out in crowded inboxes by displaying a verified logo next to messages. But in Microsoft’s ecosystem, it’s still more promise than performance. Your DMARC alignment, public CDNs, and even the device type all influence whether the logo appears at all.

Key takeaways

BIMI logos in Outlook only appear when DMARC is enforced and the logo is hosted on a public, HTTPS-accessible CDN.
Outlook for Windows and web typically display BIMI only when all authentication checks pass, but mobile apps often suppress or delay logo rendering.
As of 2026, BIMI remains inconsistently implemented across Microsoft 365 clients, with no guarantee of visual fidelity regardless of proper setup.

How Does BIMI Work in Microsoft's Ecosystem?

Outlook and Microsoft 365 only show BIMI logos if your domain has a DMARC policy with p=none or p=quarantine and includes i=*. Once verified, Microsoft checks your domain’s BIMI DNS record (a TXT record with the BIMI tag). If the record is valid, the logo is at least 140x140px, and served over HTTPS, it may appear next to your sender name in the inbox. Without these prerequisites, BIMI won’t render.

Step-by-step: BIMI Activation in Microsoft 365

Set up a DMARC policy with i=* Microsoft 365 requires your DMARC record to be either p=none or p=quarantine, and include the i=* tag to allow BIMI enforcement. Without it, your BIMI record is ignored—even if it’s technically correct. This is a hard requirement for visibility in Outlook. RFC 7483 defines BIMI’s integration with DMARC.
Host your BIMI record in DNS Once authenticated, Outlook queries a TXT record at default._bimi.[yourdomain]. The record must start with BIMI1: followed by the logo’s HTTPS URL. The domain must be accessible, and DNS propagation can take up to 48 hours. Use a real domain with valid TLS certs—self-signed certs will block rendering.
Verify logo dimensions and HTTPS delivery Outcomes depend on correctness. The logo must be a minimum 140x140px PNG or SVG, compressed without transparency, and delivered over HTTPS. Many domains fail here due to incorrect formatting or unsecured hosting. Even with a correct BIMI record, these issues prevent display.
Test inbox placement with real mail clients Your BIMI policy is only validated when an email is received in a real Outlook inbox. Use tools that simulate real-world delivery to confirm the logo appears. MailTester’s inbox placement tester helps you verify how your messages render across providers, including Microsoft 365.

Why this matters for your deliverability

BIMI isn’t just about branding—it signals trust. Microsoft only displays BIMI for senders that meet authentication thresholds. If your domain lacks a valid DMARC policy with i=*, BIMI remains inactive. This isn’t a bug. It’s security enforcement.

While BIMI can increase click-through rates in theory, its visibility depends entirely on your domain’s authentication stack. You can’t force it with just a logo file. If your emails are blocked by greylisting, rejected for poor sender reputation, or marked as spam, BIMI won’t appear—even on a valid record.

Want to check if a single address will receive your BIMI-enabled email? Use MailTester’s email checker to verify deliverability and inbox placement before sending to large lists.

What’s Missing in Outlook’s BIMI Implementation?

Outlook’s BIMI support is limited: it only applies to messages sent from Microsoft 365 domains with proper BIMI DNS records, and doesn’t work for third-party gateways or external domains. Even when BIMI is configured, users receive no feedback if the logo fails to load—no visual cue, no error indication. Admins can’t opt out or disable BIMI, even for privacy or branding control. This means BIMI’s value is inconsistent and unpredictable across the ecosystem.

Why BIMI Often Fails for External Senders

Outlook ignores BIMI for emails sent via third-party email services like SendGrid, Mailchimp, or Amazon SES unless the sender is part of a direct Microsoft integration.
Even if the BIMI DNS record is valid, the logo won’t display unless Microsoft’s systems confirm alignment with the sender’s verified domain and authenticated email.
Domain administrators have no way to check why BIMI isn’t rendering—there’s no diagnostic indicator, error code, or status message in the email client.

No Visibility, No Control

You can’t tell if the BIMI logo isn’t showing due to a misconfigured DNS record, an expired or invalid SVG file, or Microsoft’s rejection of the BIMI policy.
There’s no user or admin toggle to disable BIMI, even if you want to prevent logo rendering for privacy, compliance, or brand consistency.
Microsoft has not disclosed public documentation on BIMI fallback behavior or status codes, leaving organizations blind to failure modes. See the IETF BIMI spec for reference on expected behavior.
Without clear feedback, teams are forced to guess whether BIMI issues are technical, policy-based, or client-side—making troubleshooting nearly impossible.

Let’s be clear: true BIMI success depends on end-to-end support. Outlook’s selective, silent approach means you can’t reliably track or measure BIMI performance. If you're setting up authentication or testing inbox appearance, verifying your domain’s deliverability and DNS health upfront is essential. Use a trusted tool to test whether your email setup meets recipient expectations—check inbox placement across major providers to see how your messages appear in practice.

Why BIMI Support in Outlook Isn’t Fully Reliable

BIMI support in Outlook and Microsoft 365 is inconsistent because it relies on DKIM alignment with the 'd=' domain, which Microsoft only verifies for that specific domain—not the full sending domain. If DKIM is misconfigured, weak, or not aligned, Outlook suppresses the BIMI logo entirely. Plus, delays in rendering and inconsistent mobile support mean the logo might appear hours later—or not at all—undermining brand trust.

Dkim Alignment Limits BIMI Reliability

Outlook checks BIMI only when the DKIM signature aligns with the 'd=' domain in the email header. If your sending domain uses a different domain for DKIM (like a subdomain or third-party provider), BIMI fails. This strict alignment requirement means even a minor misconfiguration blocks the logo from showing, regardless of how well your brand reputation looks.

Because of this, BIMI is effectively unreliable unless you control the full DKIM setup and ensure consistent domain alignment. Many brands using third-party email platforms or SPF/DKIM policies that don't match the 'd=' domain find BIMI consistently suppressed. You can check for alignment issues using tools like MxToolbox or RFC 6376’s guidelines on DKIM signing practices.

Rendering Delays and Mobile Gaps Break Consistency

Even when BIMI passes checks, Outlook’s caching mechanisms can delay logo rendering by hours or even days. An email arrives with no logo, but it shows later—often without explanation. This inconsistency breaks user trust, especially when customers expect immediate visual verification of brand authenticity.

Mobile Outlook apps, particularly on iOS, frequently fail to render BIMI logos altogether. While desktop Outlook may show the logo after a delay, mobile versions often ignore BIMI completely, even when the same email passes on the desktop. This creates a fragmented user experience across devices, undermining the goal of brand consistency.

Let’s be clear: BIMI isn’t a fail-safe for trust. It’s conditional. If your email’s technical setup isn’t rock solid, or if the user’s device doesn’t support it, the logo won’t appear. For the best results, ensure your DKIM setup is robust and consistently aligned with the 'd=' domain.

How to Verify BIMI Readiness in Microsoft 365

You can verify BIMI readiness in Microsoft 365 by confirming your domain’s BIMI TXT record is correctly published in DNS, testing message rendering across Outlook clients and devices using a deliverability tool, and ensuring consistent icon display in Windows, web, iOS, and Android. Real-world testing is essential—BIMI only works if both the DNS setup and client support align.

Validate your BIMI TXT record in DNS
Use a DNS lookup tool or your registrar’s console to confirm your domain has a valid BIMI TXT record. It must follow the format: v=BIMI1; l=https://yourdomain.com/bimi.png; h=sha256;. The h=sha256 value must match the hash of your BIMI logo file. Check via DNSChecker.org or MXToolbox to verify the record's visibility across global DNS servers.
Test delivery and BIMI rendering via email
Send a test email from your Microsoft 365 address to a known inbox (e.g., Gmail, Yahoo, or Outlook.com). Use a deliverability testing platform like MailTester’s inbox placement tool to simulate delivery across multiple clients. This reveals whether BIMI is rendered, ignored, or blocked due to policy or format mismatches.
Check cross-device rendering
Open the test message on Windows desktop Outlook, Outlook on the web, iOS Outlook, and Android Outlook. BIMI should display consistently across all. Devices may vary in support—e.g., older Outlook clients may not render BIMI at all. Microsoft’s documentation notes BIMI support is rolling out, but not yet universal.

What BIMI Support Looks Like in Practice

BIMI is not a guaranteed feature in Outlook or Microsoft 365. Even with correct DNS, you may see no icon. This happens if the domain isn’t in Microsoft’s BIMI whitelist, or if email clients enforce strict policies. The IETF BIMI working group specifies that BIMI icons must be public, small (100x100 pixels max), and hash-verified—violations block rendering regardless of DNS.

Common Pitfalls and Fixes

Incorrect hash – Rehash your logo using SHA-256. Even a minor change breaks the match.
Missing or wrong DNS record – Ensure the record uses v=BIMI1 and doesn’t conflict with SPF or DKIM. DNS can’t have multiple conflicting BIMI records.
Hosted logo not accessible – The URL must be publicly reachable via HTTPS, with no redirects or authentication.

BIMI readiness isn’t just technical—it’s dependent on client policies and Microsoft’s rollout. The only way to confirm it works in real-world use is through actual testing. Start with a single verified sender domain, test across platforms, and iterate until consistent results appear.

What Should You Expect from BIMI in Outlook in 2026?

You should expect limited BIMI support in Outlook and Microsoft 365 in 2026. Even with correct DMARC, valid BIMI records, and properly hosted logos, BIMI will only appear in a small percentage of cases, mostly due to Microsoft’s restrictive rollout, mobile client limitations, and inconsistent enforcement. Don't treat BIMI as a reliable inbox signal yet—validate your setup, but don’t count on it.

Item	Details
Incorrect hash	Rehash your logo using SHA-256. Even a minor change breaks the match.
Missing or wrong DNS record	Ensure the record uses v=BIMI1 and doesn’t conflict with SPF or DKIM. DNS can’t have multiple conflicting BIMI records.
Hosted logo not accessible	The URL must be publicly reachable via HTTPS, with no redirects or authentication.

The 3 items listed under “Common Pitfalls and Fixes”, side by side.

What’s Required for BIMI to Appear in Outlook?

You must have a DMARC policy set to p=none or p=quarantine—p=reject will block BIMI display.
Your BIMI record must be publicly accessible via DNS, using a valid and properly formatted BIMI TXT record.
The BIMI logo URL must use HTTPS, not HTTP, and be reachable from public networks—firewalled or restricted URLs will fail silently.
If the logo returns a 404, 403, or other error, Outlook will not display it, regardless of DNS setup.
Even with flawless configuration, BIMI may not render in mobile Outlook apps—a known limitation in Microsoft’s current implementation.

Why BIMI Still Isn’t Reliable in Microsoft 365

Microsoft has not enabled BIMI enforcement consistently across all clients. While the technology is standardized (see RFC 8463), deployment remains experimental. BIMI shows up only in specific enterprise environments or through rare opt-ins—most customers never see brand logos in Outlook.

Testing BIMI status isn't trivial. You can’t assume visibility just because your DNS is correct. Use tools like MailTester’s inbox placement test to verify how your messages appear in real Outlook environments, including mobile and web clients.

Let’s be clear: BIMI is not a deliverability fix. It’s a brand visibility tool. If your sending domain has poor reputation, low engagement, or high spam complaints, BIMI won’t help—Microsoft may still hide it.

Until Microsoft standardizes BIMI across all platforms, don’t rely on it for trust signals. Focus first on proper authentication: SPF, DKIM, DMARC. Then, validate your entire email delivery chain using real inbox testing—not just DNS checks.

For a full audit of your sending setup, use MailTester’s bulk verification to clean your list and ensure only valid, deliverable addresses proceed.

Can MailTester Help Verify BIMI and Deliverability?

Yes — MailTester’s inbox-placement testing confirms whether your messages land in inboxes across real Outlook environments, including Windows and web clients. It validates that your sender policies (SPF, DKIM, DMARC) are correctly configured and aligned, which are required for BIMI to activate. While MailTester doesn’t render BIMI logos directly, it checks if your emails pass DMARC, which is the foundational requirement for BIMI to work.

Testing BIMI’s Foundation: DMARC and Sender Alignment

Before a BIMI logo appears in Outlook, your domain must pass DMARC authentication and maintain alignment between SPF and DKIM. MailTester checks these in real-world conditions by sending test emails through multiple client environments. It flags misconfigurations like broken SPF records, failed DKIM signatures, or policy mismatches that would block BIMI activation.

Outlook applies strict DMARC enforcement — messages failing authentication are treated as untrusted, even if the content is valid. A recent DMARC.org overview notes that enterprise email systems increasingly rely on DMARC as a gatekeeper for brand authentication, making it essential for features like BIMI.

Does BIMI Render in Outlook? The Reality Check

Outlook on Windows does support BIMI, but only if your domain has a valid BIMI record and passes DMARC with a ‘p=quarantine’ or ‘p=reject’ policy. However, the client doesn’t display the logo during verification — it’s rendered only in client inboxes when all conditions are met.

MailTester doesn't display BIMI logos, but it verifies the necessary conditions: that the BIMI DNS record is published, that it resolves correctly, and that messages consistently land in the inbox (not spam or blocked). This is a critical step — BIMI is useless if delivery fails.

Use MailTester’s inbox-placement tester to run a real delivery check across Outlook and other inboxes. It’s the closest you get to testing how recipients will see your message — including whether BIMI could eventually appear.

What Other Deliverability Factors Matter More Than BIMI?

BIMI is a visual signal—not a deliverability gate. Even with perfect BIMI, your emails won't land in the inbox if your sender reputation is poor, authentication is inconsistent, or your sending behavior looks suspicious. The truth is, inbox placement isn’t about logos; it’s about trust. You can’t brand your way out of a spam reputation.

Sending Behavior and Volume Are Silent Gatekeepers

Consistent sending volume matters. Sudden spikes in emails per day—especially without prior engagement—are red flags to filtering systems.
High abandonment rates (e.g., users opening but not engaging) signal low relevance, which harms your long-term deliverability, regardless of BIMI.
Monitor and stabilize your send volume over time. A steady, predictable flow is more trusted than bursts, even from a technically compliant domain.

Authentication Is the Foundation—BIMI Is the Finishing Touch

SPF, DKIM, and DMARC aren't optional—they’re required for most email providers to even consider your message legitimate.
Inconsistent or missing authentication leads to higher spam filter rejection rates, especially on Microsoft 365 and Outlook.
You can have BIMI enabled but still be blocked if any of these protocols fail. Fix the core—then add branding.

Sender Reputation Is the Ultimate Decider

Even perfectly authenticated emails get rejected if your domain or IP has a history of spam complaints, high bounce rates, or blacklisting—check Spamhaus or MXToolbox to verify.
Microsoft uses reputation data extensively—your past delivery behavior weighs more than any visual branding you apply.
Every email you send shapes your reputation. A single spam complaint can lower your score, just as consistently good engagement raises it.

Let’s be clear: BIMI is a nice-to-have, not a must-have. If you're still figuring out SPF alignment, checking for high bounces, or seeing spam complaints, BIMI won’t fix it. Focus first on cleaning your list, verifying addresses, and sending only to engaged users. Use real email verification to catch invalid, catch-all, and risky addresses before they harm your sender reputation.

How Do Major Tools Compare on BIMI Support?

BIMI support in Outlook and Microsoft 365 remains limited and inconsistent, unlike Gmail, which displays BIMI logos reliably across devices and email clients. Microsoft hasn’t published detailed documentation on BIMI behavior in Outlook, and even their admin guides offer minimal guidance. As a result, BIMI visibility in Outlook is unpredictable, often dependent on outdated or undocumented policies — making verification efforts unreliable without direct testing.

Outlook’s BIMI Behavior Is Unpredictable and Under-Documented

You can’t rely on Outlook to render BIMI logos consistently, even when your domain has valid BIMI records. Unlike Gmail, where BIMI display is stable and well-documented, Outlook’s handling varies by version, user settings, and organizational policies. Microsoft doesn’t specify how or when BIMI logos are rendered in their documentation, which makes troubleshooting nearly impossible for senders.

For example, BIMI might appear in some Outlook clients but not others—even within the same organization. Some users see logos; others see no indicator at all. This lack of consistency undermines the visual trust signal BIMI was designed to provide.

Third-Party Tools Don’t Test BIMI Delivery

Most email verification tools—including NeverBounce, Bouncer, and MailTester—focus on validity, syntax, and policy compliance. None claim to verify whether a BIMI logo actually displays in Outlook or other clients. You can check if your BIMI record is formatted correctly, but you can’t confirm if it appears in the user’s inbox.

MailTester, for instance, validates the technical setup: whether your DNS records are correctly set (BIMI policy, TXT record, logo URL) and whether the logo serves a valid, accessible image. But it doesn’t simulate how the logo renders in Outlook. The only definitive way to test actual BIMI delivery is to send test emails to real recipients across multiple Outlook versions and check the result manually.

For insight into how email clients interpret BIMI, refer to the IETF’s BIMI specification, which outlines expected behavior but acknowledges implementation varies. Real-world performance, especially in enterprise environments, often diverges from the standard.

Key Takeaways on BIMI in Outlook and Microsoft 365

BIMI in Outlook and Microsoft 365 is functional but limited: it requires flawless DMARC, DKIM, and BIMI record alignment in public DNS. Even then, mobile clients often skip BIMI, and caching delays or suppression can block visual display. Focus first on sending fundamentals—authentication, sender reputation, and list hygiene—before investing in BIMI branding.

What’s Actually Needed for BIMI to Work in Outlook

You must have a DMARC record with p=quarantine or p=reject and rua set to a valid email address to receive reports.
Digital signatures via DKIM must be properly aligned with the From domain and published in DNS.
The BIMI record must be published at selector._bimi.domain.com and link to an SVG logo hosted on a secure, publicly accessible URL.
Outlook checks BIMI only on domains that pass both DMARC and DKIM validation—and only if the BIMI record is correctly formatted.
For more context on DMARC policy enforcement, see the IETF’s DMARC specification (RFC 7483).

Why BIMI Often Fails Despite Correct Setup

Mobile Outlook apps (iOS and Android) often ignore BIMI, even when DNS records are correct.
Some versions of Outlook delay BIMI rendering for up to 24–72 hours due to client-side caching.
Outlook may suppress BIMI if the sending domain has weak reputation signals or poor engagement history.
Even with proper setup, BIMI may not appear in shared inboxes, group emails, or non-English language messages.
Testing BIMI in practice is difficult—you need live email sends and real inbox monitoring to confirm results.

Let’s be clear: BIMI is a branding feature, not a deliverability fix. If your emails are bouncing, blocked, or landing in spam, BIMI won’t help—no matter how crisp your logo.

Before you publish a BIMI record, verify your email infrastructure. Use MailTester’s bulk verification to clean your list, then validate sender reputation and DNS setup. True inbox placement depends on consistent sending behavior, engagement, and alignment with email standards.

For real-time testing of inbox delivery, try MailTester’s Inbox Placement tool. It checks how your message lands across major providers—including Outlook—with accurate feedback on rendering, spam flags, and deliverability signals.

Ready to Test Your Deliverability and Avoid BIMI Failure?

BIMI support in Outlook and Microsoft 365 is now live, but it’s only effective if your messages pass all authentication checks and land in inboxes reliably.

Use MailTester’s inbox-placement test to validate deliverability across Outlook and other major email clients. It checks SPF, DKIM, DMARC, and bounce behavior — including catch-all and greylisting traps — so you know exactly where your messages stand.

Run bulk list verification to remove invalid, role-based, and disposable emails that degrade sender reputation and trigger filtering. Clean lists lead to better engagement and stronger BIMI adoption.

98.9% verification accuracy
100 free verifications to start — no expiry
AI-assisted insights for ongoing deliverability improvement

Sources

Since May 5, 2025, Microsoft Outlook requires SPF, DKIM, and DMARC from domains sending 5,000+ emails per day, rejecting non-compliant mail outright at the SMTP level with error 550 5.7.515. — Microsoft Outlook requirements (via MailOver bulk-sender requirements guide) (2025)
The number of top domains at DMARC enforcement grew from 233,249 in 2023 to 411,935 in 2026 — a 77% increase driven largely by mailbox-provider sender mandates. — EasyDMARC 2026 DMARC Adoption & Enforcement Report (2026)

Keep reading

Ready to put this into practice? MailTester verifies emails with 98.9% accuracy — start with 100 free verifications.

Frequently asked questions

Does Outlook support BIMI in 2026?

Outlook supports BIMI in 2026 only partially—messages must pass DMARC, have correct BIMI DNS, and be sent from compliant domains. Mobile and some web clients often don't render the logo.

Why isn’t my BIMI logo showing in Outlook?

Your BIMI record may be misconfigured, the logo URL may not be accessible over HTTPS, or your DMARC policy may not permit BIMI. Check DNS, hosting, and authentication alignment.

Can BIMI work without DMARC?

No. BIMI depends entirely on DMARC alignment. Without a valid DMARC policy with a 'v=BIMI1' tag, BIMI will not be recognized by Outlook or any client.

Is BIMI supported on Outlook for iOS?

BIMI is not reliably supported on Outlook for iOS as of 2026. Even with correct setup, logos are often not rendered.

How do I test if BIMI will work in Microsoft 365?

Send a test message through your Microsoft 365 domain to a verified email address. Use MailTester’s inbox-placement test to simulate delivery across Outlook clients and check authentication results.

Do BIMI logos improve inbox placement?

No. BIMI does not directly improve inbox placement. It only enhances brand recognition when messages are already delivered. Authenticity and sender reputation matter more.

Can MailTester check BIMI logo visibility?

MailTester does not render BIMI logos. It checks whether your domain’s SPF, DKIM, and DMARC policies are valid and aligned, which are required for BIMI to work.

What’s the best way to improve Outlook deliverability?

Ensure proper authentication, maintain a clean email list, avoid spam triggers, and test delivery with tools like MailTester before sending campaigns.

Does BIMI work in Outlook web and desktop?

Yes, but only under ideal conditions. The logo appears only if DNS, DMARC, and delivery conditions are fully met. Rendering varies by client and device.

Can BIMI be used for transactional emails in Microsoft 365?

Yes, if the domain has valid DMARC and BIMI records. But the low success rate on mobile clients limits its usefulness for transactional branding.

What happens if my BIMI record is invalid?

Outlook will ignore the BIMI tag. No logo will appear. The message may still deliver—but without visual brand trust signals.

How often should I check my BIMI setup?

Check BIMI configurations whenever you update DNS records, change a send domain, or experience sudden delivery spikes or drops.