All they have to do to use AOSP is 1. start using it, 2. develop apps which are clients for their services, and 3. release a device with those clients preinstalled. There is no magic hidden step.
Everything from the accounts system, inter app communication, billing, push, is pluggable and they already have the servers for most of it setup, which is far and away the hardest part.
To put this in perspective moving Play Store builds to the Amazon store is generally a matter of replacing the billing and push APIs, if you've used them, which takes a few hours. (If you've used game services it might take longer, but again it's not actually hard). This is far easier than redeveloping your app completely for a different platform.
I've been involved with apps for which the move to Amazon was simply a 10 minute boot up on a Kindle Fire to establish it worked.
Nokia are bad at it, but you might recall the N-Gage that had a services layer that wasn't completely terrible. In Europe the operators usually ran this stuff, at least pre-Apple/Google, and there were a good few companies that existed by selling portals which were white labelled and branded as the operator stores.
These things certainly can be killed in bureaucracy, but the tech issues aren't too bad, especially if you're already sitting on a giant pile of servers and a billing solution for each country. At one point I knew one team running stores for about 20 operators (each country is essentially separate) with less than that in developers, and only a handful of sysadmins, if you can have such a thing.
http://www.microsoft.com/en-us/legal/intellectualproperty/IP...
So the real question is what could Microsoft leverage from AOSP? My instinct is they could probably build anything from AOSP into WinPhone far faster than they could utilize AOSP directly.