I've always found MSDN's online access to be dreadfully slow. The lack of a proper rich client - dynamically updating index in particular - for MSDN content in VS2010, so far, is disturbing to me - I generally find APIs using the index followed by contextual tree navigation, both of which don't work nearly as well in web apps.
It really comes down to this: why work at a company whose products you're not excited about? This is part of Google and Apple's success. You were an intern then, so you're fine, but more senior, high-level employees better be using your company products--otherwise, they're doing a shitty job and need to be fired.
Microsoft has a lot of products. It would be unnatural for every employee who worked there to be excited about every single one of those products. I can understand the cognitive dissonance issues of working in a division that produced products that you weren't excited about, but as for the entirety of Microsoft I think that's an unrealistic idea.
The only way to be excited equally about all of Microsoft's products (in preference to all of their competitors) is to have drunken the kool-aid so deeply that you've lost the ability to judge anything fairly. This is a far more dangerous scenario than a company that produces some products that are second run in comparison to some of their rivals. The former is a recipe for a company full of zealots who drive the company into the ground due to their lack of fair judgement, the former is to be expected of any company that has a huge and widely varied product offering spanning multiple industries.
At the time, MSN search was so bad that this proposition was ludicrous. In fact, every Office developer I knew used Google with a "site:msdn.microsoft.com" restriction to search their own API docs.
I wonder if Bing is now good enough that employees feel pressure to use it instead of Google.