http://docs.opencv.org/2.4/modules/contrib/doc/facerec/tutor...
I saw some demos of M$FT's apis at a recent tech event and it wasn't obvious that the results with their system were significantly better. The biggest hole seemed to be that camera frames were being sent to the cloud, and there were issues with the presenter's quota (forget the exact problem).
But overall, I think the Cognitive Services are a step in the right direction. They generally make sense for businesses who don't have a full-time team of ML/CV experts.
There are serious companies (like Netflix) that put their entire infrastructure on cloud platforms. If the concerns the OP raises are valid, no company for whom ML is a big (read: high usage, high paying) feature is going to rely on these cloud services. And startups that do rely on the cloud services for their MVPs are going to move off as quickly as they can. I can't think of any successful cloud platform for which MVPs and small features are the main customer use case. Heroku comes to mind, but even then there are mid-size companies that do rely mostly on Heroku.
But also - what happens when you wish to expand and grow? My guess is, if this capability was developed in house, you would almost certainly find it easier to not just scale without incurring a "success tax", but most importantly you are now exposed to the deep bowels of the ML process which should certainly give you far greater insight into potential tangentially related services.
An example: you use a natural language processing API and get all the brand mentions in some text the customer has submitted - certainly a useful service for competitive research. As your company scales, now you are more or less beholden to the ML service - if nothing else at least for the consistency of results, which is likely to make you super cautious about rolling your own. But you don't know how the results (brand mentions) were actually inferred. If you were to ask, "Hmm.. what other types of entities can I extract and have it be more useful for our customers? What about only getting brand mentions if it is in the same paragraph as a complaint?" - you might face some options which you might not really like - for one, the way the ML API is structured might actually make this operation expensive (after all, the data is pretty adjacent before being sent to the ML API, but not necessarily so once it is processed). Also, since you never understood how the brand mentions were extracted, it is very likely you are missing out on a ton of insight you could gain by rolling out your own capabilities.
And not to mention: if the ML capability has been outsourced, and if ML is indeed going to drastically impact your industry, then you would certainly not want to be in the position where your competitor can easily disrupt you merely because they spent the time to develop such capabilities in house.
For the vast amount of companies where ML isn't in any way core, this is great. For example we've got a little internal app that includes a profile picture.
Currently we pre-crop photos before uploading. Obviously not the best solution. Putting together a little javascript thingy to allow the user to crop is somewhere deep in the backlog. Now this exists I'm very tempted to implement a little feature to auto crop around the face on upload. Nothing there to steal, definitely not worth rolling our own ML system to do it but a very nice thing to now be available in our toolkit.