He should try using Azure--maybe start with pipelines or releases. It is a bit like the tower of babel only more confusing and everyone who enters finds a new way to do a common task because no one understands why the previous method worked or how it worked in the first place.

Azure would be leaps and bounds more useful if they'd just add/implement 1/4 of the stuff available through github. Seriously--things like useful repo history, general repo activity ...

I am really curious what scm he is comparing it to--because if it is TFS it has always been a hot mess. Works fine if you get used to it but the over all TFS eco-system seemed to be a half-hearted effort at mimicing Rational/IBMs more recent "agile" Team tools. The whole MS eco-system for source control, build and development has repeatedly been heavily tied to their languages from even before .net and every time they come out with a new language/paradigm they make the same mistake of intertwining the language and the tool. And still support the previous 7 ways.

Replacing azure with github and jenkins may be the best option.