"I suspect that many still inaccurately equate or conflate “cloud” with “IaaS,” which is a perspective at least a full decade out of date. Without question, Amazon created and still leads the IaaS segment of the cloud—but the cloud of today looks nothing at all like it did 10 years ago when “cloud = IaaS” was a reasonable equation."
The "Cloud Revenue" number includes things like Dynamics, 365, etc.
Otherwise it's like saying "McDonalds wallops GEICO in burger revenue."
I feel that increasingly the real difference is between 'end-user facing cloud products' (which essentially always means SaaS) and 'developer-facing cloud products' (which includes all your IaaS/PaaS/some-SaaS).
Historically, the term for 'end-user facing cloud SaaS product' was 'a website'; we're just seeing tighter IAM integration in the enterprise space and more powerful products as a result of the increased capabilities of JS engines and better frameworks.
The difference is basically "this is stuff developers used to build products" vs "this replaces a shrink-wrap product that would historically have been delivered to a user desktop".
Cloud has never been "just" S,P, or I "aaS". But it seems clear to me if you're going to write an article comparing any company's so-called Cloud revenue to Amazon, you're going to be comparing IaaS numbers.
Amazon's non-cloud products probably use much much less data center infrastructure than Microsoft and especially Google.
https://www.microsoft.com/en-us/Investor/earnings/FY-2020-Q3...
Microsoft says 13.0 billion, this says 15.3 billion
I have no idea where these numbers are from.
What I am trying to say is that the criticism that you are "not allowed" to include PaaS and SaaS solutions to the cloud revenue doesn't seem correct either.
I understand why someone like AWS would not want that to be the new way of counting. It is profitable to appear as the unthreatened champion of cloud (the default choice), but the fact is that Microsoft is closer in size than what many people may think.