AzureAI-SearchBot
AzureAI-SearchBot is a bot operated by Microsoft that indexes pages so an AI answer engine can cite them. AzureAI-SearchBot crawls web pages on behalf of Azure AI Search customers who point an indexer at a public site. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
AzureAI-SearchBot at a glance
| User agent | AzureAI-SearchBotToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | Microsoft |
| Purpose | AI search crawlers |
| Respects robots.txt | Not documented |
| Verification method | None published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | AzureAI-SearchBot |
| Operator documentation | None published |
AzureAI-SearchBot crawls web pages on behalf of Azure AI Search customers who point an indexer at a public site. The traffic belongs to that customer rather than to Microsoft Search.
Allow or block AzureAI-SearchBot
Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.
User-agent: AzureAI-SearchBot
Disallow: /Blocks every path for this crawler only.
User-agent: AzureAI-SearchBot
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: AzureAI-SearchBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
Blocking AzureAI-SearchBot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.
Block every crawler in the directory at onceIs that really AzureAI-SearchBot?
A user-agent header is a string the client chooses. Scrapers copy AzureAI-SearchBot precisely because site owners allow it. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof.
Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.
Other crawlers run by Microsoft
Related crawlers
Identify crawlers automatically instead of by hand
Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.