Microsoft Preview crawler bot is Microsoft’s metadata fetcher (user agent typically “MicrosoftPreview/1.0”) that retrieves Open Graph, Twitter Card, oEmbed and favicon assets to render link previews across Microsoft apps such as Teams, Outlook, OneDrive/SharePoint and Copilot. When a URL is typed, pasted, or received, the service performs server-side HEAD/GET requests from Microsoft IP ranges, follows redirects, downloads representative images, and does not execute client-side scripts. For defenders and fraud teams, its traffic can appear as automated “first clicks,” skewing analytics, firing webhooks, consuming one-time links, or tripping bot/geo policies. Use cases: allowlist/identify it to avoid false positives, block it on sensitive endpoints, design idempotent GETs, avoid side effects on preview fetches, and provide explicit preview metadata for safer, consistent rendering.
(Bing) MicrosoftPreview
What is (Bing) MicrosoftPreview?
Threat research insights on (Bing) MicrosoftPreview
All data in this section are produced by DataDome's Galileo Threat Research team from our proprietary detection network and reviewed by human analysts.
Traffic origins
Top 15 countries by bot traffic
Most used autonomous system (AS)
Top 5 by traffic share
On average, occupy <0.1% of the traffic from bots in the directory
Businesses decide to authorize this bot 100% of the time
Why is (Bing) MicrosoftPreview crawling my site?
It’s typically triggered when someone in a Microsoft ecosystem (e.g., mail, chat, browser) shares or opens your URLs, prompting automated fetching for safety checks and preview generation. Potential downsides: increased crawl traffic and bandwidth costs; skewed analytics (inflated pageviews, unusual referrers, misattributed campaigns); false positives in bot/fraud detectors and WAFs; premature activation of single-use links (password reset, magic links, unsubscribe, download tokens, payment or promo URLs); accidental invocation of webhooks or workflows; session or geo/AB-test leakage that alters user experience or pricing logic; rate-limit exhaustion impacting real users; noisy logs that hinder incident triage; and compliance/privacy concerns if sensitive, unguessable URLs are probed from private contexts. Ensure sensitive routes require proper authorization and that tokens/links are resilient to non-human prefetching without relying on client-side behavior.
How to detect and authenticate (Bing) MicrosoftPreview?
1. Robots.txt File: Disallow Microsoft’s preview crawler (BingPreview) so compliant bots won’t fetch pages. Place in your site root.
User-agent: BingPreview
Disallow: /
User-agent: MicrosoftPreview
Disallow: /
2. .htaccess (Apache): Block by user-agent at the web server layer using mod_rewrite.
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (BingPreview|MicrosoftPreview) [NC]
RewriteRule .* – [F,L]
3. Nginx Config: Return 403 for requests whose user-agent matches Microsoft’s preview identifiers.
if ($http_user_agent ~* (BingPreview|MicrosoftPreview)) {
return 403;
}
4. Server-Side Scripting: Deny at the application layer by inspecting the user-agent (example in PHP).
if (isset($_SERVER[‘HTTP_USER_AGENT’]) &&
preg_match(‘/BingPreview|MicrosoftPreview/i’, $_SERVER[‘HTTP_USER_AGENT’])) {
header(‘HTTP/1.1 403 Forbidden’);
exit;
}
See which bots and AI agents bypass your defenses
Create your account to start analyzing and mitigating malicious bots and AI-driven threats in real-time