How can we improve Microsoft Azure Stack?

Methodology or suggestion for Azure Stack SLA calculation

There is ongoing ask from Service Providers to equip them with methodology or guide how to calculate aggregated SLA for Azure Stack installations which these Service Providers are going to operate. It is obvious that there is no direct SLA commitment from Microsoft side for Azure Stack availability thus at least recommendations would be really helpful. Especially having in mind that Microsoft itself has tremendous experience to calculate SLA for its Azure DCs and Cloud Services – which hopefully can be somehow shared with Partner Ecosystem.

39 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Andrey shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

3 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Yu Ling commented  ·   ·  Flag as inappropriate

    This is also many of my customers are asking about but we can hardly provide any reliable commitment without backup from MS.
    Really need an official guide as evidence.

  • Vitaly commented  ·   ·  Flag as inappropriate

    That's really huge challenge, because most of the customers want to see availability SLA of entire service in documents/treaties; But to calculate it - we need Microsoft to declare/commit AzS rack and internals availability SLA;

    So, we, as CSP, can guarantee only our DC availability SLA for our customers in case of AzS now - it's not acceptable in most cases;

    It would be also awesome to see some reliability for HW components (MTBF, Failure rate) from AzS Hardware vendors

Feedback and Knowledge Base