For example, my city gets aerial imagery taken ~yearly, with resolution better than 1 ft/px. This is very precise, and the updates are frequent; yet, still insufficient to answer typical mapping questions, such as "can I get there from here, using this vehicle?" That's what a map should be able to answer: both map and aerial image can tell you "there is a vehicular track", but only the map will tell you "and it's private, and even if you don't care for signs, this gate over here is locked, so no, this does not route; you can't go over that road here, as it has a bollard in the middle; that bridge is too flimsy for you; that street is one-way but opposite; you need to go that way, but there's toll collected; otherwise, there's a lengthy detour."
Only some of these features can be inferred from an image. (Of course, the map needs to be kept up-to-date with all this data, but that's a very different story)
Same problem with rivers... a lot of rivers show up the same color as the forest on satellite images so you'd never know there was a river there even if you can "see" the water.
Depending on the angle of the satellite, this problem exists in large cities as well. Roads are obscured by skyscrapers even at the slightest angle, and roads disappear from the picture without telling you if they went underground into tunnels or just ended.
Now, satellite pictures overlaid with map data, that works. But just satellite pictures by themselves isn't enough to navigate.
Not to mention that afaik the "map data" itself isn't actually available from either MS or Google - they only sell usage of it through their limited APIs.
The data TomTom and HERE have is focused on navigation use cases - it doesn't have so much 'visual' stuff as OSM but has has large quantities of information that is only relevant for car navigation, e.g. historical traffic patterns and lane assignments.
Did you have a "best" in mind.
I'd definitely not consider plain satellite imagery to be map data.