Provide SLA for single instance Azure
Currently Windows Azure Plafrorm offers SLA of 99.95% for compute service for Azure solutions that comprizes of 2 or more role instances.
However, very often Azure is used to prove untested business ideas. It does not make sense to have to pay upfront for high-availability and additional components (Azure AppFabric Cache for Session state, etc). A lot of ISV will want to go to market with one instance and if the business idea works - scale out.
So it would make sense that Microsoft defines an SLA for a solution comprizing of one role - obviously we would not expect 99.95% something like 90% SLA would be enough. For this to work we would also like that the updates in the datacenter do not happen during working hours in a given geography.
Why not have a 99.5 SLA for single-instance VMs and leave the higher 99.95 SLA for servers configured in an availability set? Unless you can justify an N+1 scale out strategy it's just way too cost-prohibitive for SMB clients to justify availability sets. Many of our small clients won't pay for that but won't go to something with no SLA. At least 99.5 would be something. I wonder how much $$ MS leaves on the table due to customers that won't go to something with no SLA or no cost-effective way to get an SLA.
@Dennis, yes 90% sounds a bit over the bar; but having dealing with customers, its very difficult to tell that there is no SLA for single instance (which can be worse that 90% and cannot be questioned :) ). I would not take the literal number that @Michal is saying but I feel he means give a number rather than saying no SLA even if its far worse.
Do you realize that 90% of a year is less than 11 months?!? What would the point be of guaranteeing no more than 1.2 months of down time per year?
90% of a day is only 21.6 hours! Would 2.4 hours of down time each day really be acceptable?
Are you experiencing a lot of down time on a role with only a single instance?
David Rodriguez commented
Looking for the same here!