Updated high availability and disaster recovery app design guidance

Adam Glick

We’re pleased to announce that we’ve updated our guidance article on disaster recovery and high availability for applications built on Microsoft Azure.

We heard from you that one of the most useful documents we provided in designing your applications for Azure was our guidance around designing for high availability and disaster recovery. In addition, we heard that you also wanted an easier way to get directly to the content that you are most interested in. Since our original guidance was quite detailed, we’ve broken this guidance up by the use case, providing guidance for both high availability and disaster recovery separately.

The new high availability for applications built on Microsoft Azure article helps you understand how Azure works and how you can employ various strategies to achieve higher availability for your applications on Azure.

The new disaster recovery for applications built on Microsoft Azure article takes you through various disaster recovery scenarios while helping you consider the differences in cost, complexity, recovery time objective (RTO), and recovery point objective (RPO).

We hope this guidance helps you build better, more resilient applications on Azure. We’ll continue to review and improve our guidance and your feedback is key to helping us make sure we’re giving you the right content, in the right way, at the right time. Your feedback on these articles is always appreciated and encouraged so please feel free to leave comments in the comments section below, on the article pages directly, or email us at ResiliencyFeedback@microsoft.com.

For the latest updates and information on Azure Government, be sure to subscribe to our blog here or by clicking on the RSS icon.


Discussion is closed.

Feedback usabilla icon