We’re happy to announce that we’ve released a new high availability checklist to help you increase the resiliency and availability of your applications in Azure.
We know uptime matters to you and Azure gives you great tools and services to help increase your availability. However, we noticed that many people have yet to take full advantage of these benefits of Azure. Azure resiliency is a shared responsibility model. As a result, we created this checklist to provide common ways to increase your application’s availability in Azure, using best practices, tools and techniques. These suggestions come from both good design patterns as well as the experience of our architects who work with customers building on Azure.
One new addition in this checklist is the inclusion of a short description of what happens if you don’t follow the listed guidance. Based on our discussions of best practices with customers using Azure, a common question we heard was, “What will happen if I don’t follow this suggestion?” We realized that, not only do you want to know what the best practices are, but also why they are important. In response to that feedback, we’ve answered the question of what happens if you don’t use each suggestion within the guidance. We hope this helps you achieve your goal of making better decisions on the design of your Azure applications as well as understanding any particular tradeoffs that you might decide to make.
We hope this checklist helps you with your current and future Azure applications. We welcome any feedback you have on this checklist, so please feel free to leave comments in the comments section below, on the article page directly, or email us at ResiliencyFeedback@microsoft.com.