Rather than vague statements that say nothing other than what our biases are, let us look at the specific facts of the case.
We can start with one issue mentioned in TFS. Microsoft complains that they aren't able to index Youtube as well as the site can index itself, with direct access to the database. Instead, Microsoft / Bing needs to either a) spider the site like every search engine does on every other site in the world, or b) use the APIs that Google has made publicly available at no charge . Microsoft complains that those APIs are insufficient. Let's consider that, by comparing them to the norms in the industry. How good are the Youtube APIs compared to the APIs that Microsoft provides for MSDN? Well, Google provides an API an Microsoft does not.
It iseasier for Bing to index Youtube than it is for Google to index MSDN.
One can imagine that it might be fair for someone say "you should give us just as good as we give you." Here Microsoft is saying "you give us an API, but we want you to provide a better one, while we provide none at all." A basic concept of fairness is that the expectations are the same for everyone- that one should not demand from others something you are not willing to do yourself. Until Microsoft makes an indexing API available for their own properties, it seems rather strange for them to demand others provide even better APIs to them.
Youtube supports HTML5 video, aka modern browsers. Microsoft complains that they are having trouble pulling YouTube's videos out of the web pages (where the ads to pay for it and track views are) and display them in their own app. Does Microsoft provide their content for free, to be pulled out of their web siye and served up separately? Can Google rip the MSDN content and display it in an app, rather than on Microsoft's web page? Microsoft doesn't allow that, so how can they insist that Google not only allow it, but make it essier for them?