Comment by karel-3d
20 hours ago
Yeah, this is sensible.
I also want to add that there are large industries that LOVE Microsoft and LOVE the Azure/365 vendor lock-in. This corporate merger might be added value to those customers. (Azure has their own github called Azure DevOps and - from what I have seen - is quite bad, but deeply integrated into Azure stuff)
ADO is just the rebranded Visual Studio Team Services which is just the rebranded Team Foundation Service (which itself is the cloud version of ADO/VST/TF Server). It isn't really integrated in Azure aside from the naming, and it is intended to be more of a Jira/Bitbucket/etc replacement than GitHub.
I remember that every action you could do there needed somehow be approved in Azure Active Directory
Azure DevOps is.... okay. It's functional, and it's not really anything unique or innovative; but it never really strived to be anything like that. It started out as the online, service-based version of Team Foundation Server and was very clearly being cultivated into turning into "Github, but integrated into the Azure ecosystem" and that particular strategic need evaporated for Microsoft when they acquired the actual Github.
Azure DevOps went into zombie mode basically the same day the acquisition closed; I don't think it's received any new features since 2018.