Azure AI Search
Operated by Microsoft
Quick Facts
- User-Agent:
- AzureAI-SearchBot
- Category:
- AI & LLM Bots
- Operator:
- Microsoft
- Safety:
- Safe
- Blocking Impact:
- Low - No SEO ranking impact
- SEO Impact Score:
- 2/10
- Official docs:
- None published by Microsoft
Reported, not operator documented
Microsoft has not published a crawler page that names AzureAI-SearchBot. It is listed here on our own evidence. Verified by AI Crawler Check: 26 of the 5,583 valid robots.txt files in the Tranco top 10,000 carry a rule for AzureAI-SearchBot, so site owners treat it as a real crawler name (how we measure this). That proves the spelling is in use, not who sends it. Reported Azure AI Search crawler token. Microsoft publishes no page for it.
What that means for you: the AzureAI-SearchBot rule on this page is the best available spelling, but Microsoft has made no statement of purpose, crawl rate or robots.txt compliance. Treat a AzureAI-SearchBot request in your logs as a clue, not proof of who sent it, and add a firewall rule if that traffic matters to you. If the operator publishes documentation, this profile moves to Official docs.
What is Azure AI Search?
Azure AI Search is an AI search-index crawler operated by Microsoft. It collects and indexes web content so it can be surfaced as citations or answers inside Microsoft's AI search experience. Allowing Azure AI Search can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Azure AI Search is an AI search-index crawler operated by Microsoft. It collects and indexes web content so it can be surfaced as citations or answers inside Microsoft's AI search experience. Allowing Azure AI Search can increase your visibility in AI-powered search results, which is why most sites choose to permit it.
Azure AI Search uses the user-agent token AzureAI-SearchBot. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.
What happens if you block Azure AI Search?
User-agent / Disallow: / without any SEO penalty.AzureAI-SearchBot compared with documented Microsoft crawlers
| Token | Documented by Microsoft? | What it is linked to | Effect of blocking |
|---|---|---|---|
| AzureAI-SearchBot | No (Reported) | Reported with Azure AI search services | Unknown; may stop an Azure-based indexer |
| bingbot | Yes | Bing Search and Copilot grounding | Removes you from Bing and Copilot answers |
| BingPreview | Yes | Page previews in Bing | Previews missing |
| OAI-SearchBot | Yes (OpenAI) | ChatGPT search, often confused with Microsoft | Drop out of ChatGPT search |
Microsoft's crawl-to-refer ratio was 40.7 pages per visitor in Cloudflare, 29 August 2025 data, far better than most AI-first operators, which is why Bingbot should almost never be blocked.
AzureAI-SearchBot use cases
| If you are... | Recommended setting and why |
|---|---|
| You want Copilot visibility | Keep Bingbot allowed. That is the documented route into Copilot. |
| You see AzureAI-SearchBot in logs | Treat it as an Azure-hosted indexer of unknown owner. Check reverse DNS; an Azure IP proves the host, not the operator. |
| You block unverified bots | A named Disallow group is safe; it has no documented search effect. |
User-agent: AzureAI-SearchBot
Disallow: /
User-agent: bingbot
Allow: /Run a crawler check to see Bingbot and AzureAI-SearchBot separately, and read Bingbot and Copilot for the documented path.
Check Microsoft crawler access
- AI crawler checker: tests 265 bots against your robots.txt in one scan.
- AI crawler diagnostic: fetches a page as each AI bot and names the layer that blocks it.
- robots.txt validator: shows allowed, blocked and partial status per bot.
- robots.txt generator: builds a file with presets for search, agents and training.
- batch URL checker: compares up to 20 sites side by side, with CSV export.
- llms.txt generator: writes the file AI assistants read for a site summary.
- schema markup generator: produces JSON-LD for eight common types.
- GEO audit: scores a page for generative engine optimization.
Want to see whether Azure AI Search actually visits you? Read how do I monitor AI bot traffic to my website?
How to block Azure AI Search with robots.txt
<code>User-agent: AzureAI-SearchBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is Azure AI Search safe to allow?
What does Azure AI Search do?
Understanding Azure AI Search's purpose helps you decide whether to allow or block it.
- Indexes web pages for AI-powered search answers
- Surfaces your content as citations inside AI search results
- Builds a knowledge index used to answer user questions
- Allowing it can increase visibility in AI search
- robots.txt behaviour not documented by the operator
Azure AI Search in context
Azure AI Search is a retrieval crawler that feeds AI search answers operated by Microsoft. In plain terms, it builds a search or answer index. Our database files it under AI and LLM crawlers and ranks it Tier 2, important crawlers from established AI and search operators. 74 of the 104 AI and LLM crawlers in our database share this tier.
Its safety rating is safe and its blocking impact is low. So the decision about Azure AI Search rests on what you want from Microsoft, not on its behaviour. How we rate safety and impact.
How site owners treat Azure AI Search
In our own scan of the Tranco top 10,000 (5,583 valid robots.txt files), 26 files (0.5%) name AzureAI-SearchBot in a User-agent line. That shows site owners treat the token as a real crawler worth a rule. It does not, on its own, prove who operates it.
Does it follow robots.txt?
Azure AI Search's operator does not clearly document how it treats robots.txt. Write the Azure AI Search rule anyway, then confirm in your logs that its requests stop.
Microsoft crawlers and close alternatives
Azure AI Search is one of 6 Microsoft crawlers in our database. A User-agent: AzureAI-SearchBot group controls Azure AI Search only; the other Microsoft tokens below need their own lines.
AzureAI-SearchBot: this crawler (Tier 2)AdIdxBot: Bing Ads Crawler, checks pages for an SEO, uptime or analytics service (Tier 3)bingbot: Bing Search, builds a search or answer index (Tier 3)BingPreview: Bing Page Snapshot, builds a search or answer index (Tier 3)BingVideoPreview: Bing Video Preview, builds a search or answer index (Tier 3)MicrosoftPreview: Microsoft Preview, fetches a page to build a link preview when someone shares it (Tier 3)
To give Azure AI Search the same answer as its siblings, stack User-agent: AzureAI-SearchBot with their lines above one set of rules; to treat Azure AI Search differently, give it its own group.
Other AI and LLM crawlers that do the same job (builds a search or answer index) include AddSearchBot from AddSearch, AIWebIndex from Lyrenth, atlassian-bot from Atlassian, Cloudflare-AI-Search from Cloudflare, Cloudflare-AutoRAG from Cloudflare, ExaBot from Exa. Deciding about Azure AI Search is usually a decision about the whole group, so check how your file treats these too.
We first recorded AzureAI-SearchBot on June 18, 2026. We could not find a page where Microsoft names it, so treat the token as reported rather than documented.
Which rule Azure AI Search actually follows
Azure AI Search reads exactly one group in robots.txt, the most specific one that names AzureAI-SearchBot, and never combines rules across groups. This short file shows the trap:
User-agent: *
Disallow: /private/
User-agent: AzureAI-SearchBot
Disallow: /drafts/- Find the group. Azure AI Search looks for a group naming
AzureAI-SearchBot. One exists, so it ignoresUser-agent: *completely. - Apply only that group. It is refused
/drafts/and nothing else. - The surprise.
/private/is open to Azure AI Search, because that rule lives in the*group it no longer reads. To keep it out of both, repeatDisallow: /private/inside its own group.
Test yourself: does a rule under User-agent: * apply to Azure AI Search if the file also has a User-agent: AzureAI-SearchBot group?
No. Once a group names it, Azure AI Search reads only that group. Put every rule you want it to follow inside its own group.
Test yourself: will blocking Azure AI Search remove your pages from AI answers?
Often, yes. Azure AI Search is a retrieval crawler that feeds AI search answers, so pages it cannot fetch can drop out of the answers or results it supports.
Test yourself: is User-agent: azureai-searchbot the same as User-agent: AzureAI-SearchBot?
Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.
Should you allow Azure AI Search? Decide by situation
| If you are... | Recommended setting |
|---|---|
| You publish content and want AI answers to cite it | Allow it. Azure AI Search fetches pages for answers, so blocking it can remove you from them. |
| You license content and want to stop AI training | Blocking it does not stop training, because Azure AI Search is a retrieval crawler that feeds AI search answers. Block the operator's training crawler instead. |
| You run an online shop | Allow it on product and category pages, which are the pages shoppers ask assistants about. |
| Your server is under load from bots | Rate-limit before blocking. It is rated safe in our database. |
Check Azure AI Search on your own site
- Open
/robots.txton your domain and search forAzureAI-SearchBot. If it is not named, it followsUser-agent: *. - List the
Disallowlines in the group Azure AI Search follows and test your key URLs against them; the longest match wins, andAllowwins a tie. - Look beyond the file. A firewall or bot manager can refuse Azure AI Search even when robots.txt allows it, and that never shows in the file.
- Run our crawler access checker to see how Azure AI Search and every other crawler we track are treated in one pass, including firewall refusals.
Common mistakes with Azure AI Search
The errors we see most often with Azure AI Search in the files and firewalls we test:
- Blocking Azure AI Search while trying to stop AI training. Retrieval crawlers fetch pages so answers can cite them; blocking it can remove you from those answers without affecting training.
- Letting a firewall or bot-fight mode refuse Azure AI Search while robots.txt allows it. The file looks right, but the crawler still gets a 403 or a challenge page.
- Forgetting that once a
User-agent: AzureAI-SearchBotgroup exists, Azure AI Search ignores every rule underUser-agent: *.
All three hide inside a file that looks correct, so check Azure AI Search from outside after every change.
Spotting Azure AI Search in your logs
robots.txt says what Azure AI Search may do; your access logs show what it actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "AzureAI-SearchBot" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -cAnd this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "AzureAI-SearchBot" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20Check the requests are genuine
Anyone can send the Azure AI Search user-agent, so confirm the source before acting on a match:
AzureAI-SearchBot: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Azure AI Search request with caution.
Frequently Asked Questions
What user-agent string does Azure AI Search use?
AzureAI-SearchBot. Evidence that the spelling is in real use comes from our own robots.txt study: 26 of the 5,583 valid robots.txt files in the Tranco top 10,000 name it (fetched October 20, 2026), not from Microsoft, which has not published crawler documentation naming it. Use it in robots.txt as the best available match, and treat a request carrying it as a clue rather than proof of who sent it.Is Azure AI Search safe?
Will blocking Azure AI Search hurt my SEO?
User-agent / Disallow: / without any SEO penalty.How do I block Azure AI Search in robots.txt?
/robots.txt file:User-agent: AzureAI-SearchBot Disallow: /
This instructs Azure AI Search not to crawl any path on your site. To block only specific sections, replace / with the path (e.g.,
Disallow: /blog/).Does Azure AI Search respect robots.txt?
AzureAI-SearchBot will stop a client that chooses to honour it; for enforcement, add a firewall or CDN rule as well.How do I verify if Azure AI Search is crawling my site?
AzureAI-SearchBot (for example grep -i "AzureAI-SearchBot" /var/log/nginx/access.log). Because the operator publishes no IP ranges or reverse-DNS pattern, a match shows that something used the name, not that Microsoft sent it.