There are over 100,000 Microsoft employees worldwide and likely only a handful might know these specifics. None of those would be available here or even on any website supported by Microsoft since that's not their job, maintaining the systems is.
In any case you have absolutely no need of their assistance or even this specific information, all you need to do is determine what those specific error messages mean, which I highly doubt really matter in any case. If you do really care then researching them from the point of reference of the application involved is what matters as I mentioned earlier.
The issue with Whois.com is that it 's designed for domain lookups, so when requesting an IP it simply offers the ARIN WHOIS response which only provides IP block information. Using a true IP lookup such as the one you mentioned is what I had assumed you'd done, so that explains the difference in our results. I never called you a fool though, that's your own interpretation of my assumption.
You need to concentrate on the error messages themselves rather than which source addresses may be "causing" them, since obviously your own server is exposed to the Internet. Open Internet IP addresses are typically scanned by hundreds or even thousands of potentially malicious actors every day, as well as dozens of non-malicious search engine servers.
Some of these are also security related servers looking for outdated applications or services in order to report them in aggregate or for other related research. Based on the name including MSN I suspect this address is simply performing search engine scanning.
I would venture a guess that the errors you are getting are due to invalid or missing fragments within your web pages, though researching the precise errors and correlating them with others indicating which exact URL was being requested at the time might help you determine what triggered them.
Rob