Lol but actually this is a good way to escalate priority. Better yet, point it at various Microsoft sites that aren't provisioned to handle the traffic and let them internally escalate.
I'm not a malicious actor and wouldn't want to interrupt their business, so that's a no-go.
On a technical level, the crawler followed HTTP redirects and had no per-domain rate limiting, so it might have been possible. Now the API seems to have been deactivated.
Lol but actually this is a good way to escalate priority. Better yet, point it at various Microsoft sites that aren't provisioned to handle the traffic and let them internally escalate.
In my experience, that'd turn into a list of exceptions, rather than actually fixing the problem.
I'm not a malicious actor and wouldn't want to interrupt their business, so that's a no-go.
On a technical level, the crawler followed HTTP redirects and had no per-domain rate limiting, so it might have been possible. Now the API seems to have been deactivated.