There must be some fun intracorporate debates discussing how this is positioned relative to the Azure Container Registry, also offered by a division of Microsoft.
https://azure.microsoft.com/en-us/services/container-registr...
https://azure.microsoft.com/en-us/services/container-registr...
If they did talk, I expect it would mostly be to decide on segmentation.
Microsoft still seems to be quite coy on what the actual long term plan is, but from at least some appearances there seems to be one in this case. (I've heard lots of rumors but no easy to find reputable sources that Azure DevOps eventually gets eaten as a brand by the GitHub brand and an eventual (auto-)migration. I still don't know if I can trust those rumors, but that seems like one of the better options to me.) At the moment in the short/medium term it seems like Microsoft is trying to dual brand the same products to target different customer types.
You can tell that Microsoft absolutely respects GitHub as a brand and just based on raw public changelogs and available roadmaps there seems to be a lot more investment in labor and "spirit" in GitHub than Azure DevOps right now.
Again, there are nothing more than rumors at this point. Yet there was always something of an impression that when Microsoft's bharry retired the lights might go out on Microsoft's TFS/VSO/Azure DevOps legacy, and the timing of the GitHub purchase coincides with that idea that GitHub is a full replacement.
I've even heard some of how strongly Microsoft sales people are trying to encourage on-premises server installs to move to GitHub Enterprise (and away from legacy TFS products).
Many signs seem to be pointing to GitHub will be the last product standing (powered by Azure).