Well, in addition to the actual basis of the case indeed being "tying" with regards to Internet Explorer, whether you like it or not, being tame compared to Google's voracity for the same behavior, forcing 20 apps to be tied on Android devices.
They do indeed form restrictive licensing agreements with OEMs. Through the MARA, anyone who dares create an Android device that doesn't have Google's blessing is permanently cut off from Google services.
Google's APIs no doubt favor their own services over competitors, where many features of synergistic behavior between services exist which are not represented in their public API.
And Google has absolute intent on continuing these practices. New marketing campaigns and shilled blog articles regularly advertise about the brilliance of their current direction, and they continue to add more and more restrictions on OEMs with every passing year.
(Using "Underlying these disputes were questions over whether Microsoft altered or manipulated its application programming interfaces (APIs) to favor Internet Explorer over third party web browsers, Microsoft's conduct in forming restrictive licensing agreements with original equipment manufacturers (OEMs), and Microsoft's intent in its course of conduct." from the Wikipedia article as a source for the other parts of the Microsoft case. Note the article clearly defines the IE tying issue as the principal claim.)