Earlier quoted context omitted.
And how bad would it be if it wasn't so successful? Apple gets to point fingers at Microsoft for not being able to keep up if things go south.
That would only matter if Apple was having infrastructure problems. If people just didn't want the product, those claims wouldn't make sense.
To put it another way, I frequently tell people "Businesses choose Java because if it fails, it isn't because they choose Java." This means that if the Director of IT says to build with the industry standard of Java (or .Net), it is not the Directors fault if/when the project fails. The project manager, the developers, QA, middle management, etc failed to do it correctly. It is a safe choice since it is industry standard and thus well proven. If it takes longer and costs more, it means it was a much more difficult problem then they expected, but since they used Java they got it working.
If on the other hand, they went with Rails/Django/Node.js/Erlang/NoSQL/etc, and it fails, the Director chose to use "new and untested" technologies, he/she is the root cause. Regardless of the fact that it could just be that realistic goals/management were never used.
I am not trying to say Azure is industry standard or the safe choice, but the way to shift blame is the same.