Optimizing for stability during the global health pandemic

Gloridel Morales

Update: We are beginning to resume our release cadence and anticipate posting release notes for our next feature payload next week. We will continue to focus on stability and reliability and follow safe deployment practices with an eye toward minimizing risks during the global health pandemic.

Thank you for your patience these past couple of weeks.

Azure DevOps serves as the foundation of the engineering system for many of our customers, as well as for most of Microsoft itself. With so much uncertainty arising from the COVID-19 global health pandemic, during this time we believe our overriding focus for Azure DevOps needs to be stability and reliability. Our customers need to be confident that their ability to develop, build, and deploy changes to their services will not be compromised.

As such, we are pausing our normal sprintly feature deployments until at least April 7, 2020. This will delay our typical schedule by two to three weeks. During this time we will continue to deploy critical updates needed to fix bugs or address stability, reliability, or security issues. If this schedule changes, we will post updates to this post.

To see current and historical information on Azure DevOps status and incidents, see the Azure DevOps service health here.


Discussion is closed. Login to edit/delete existing comments.

  • Stuart Bean 0

    Hi, you broke the build servers today, https://status.dev.azure.com/_event/182998791. Can you let the team who maintain the build server images that you have a change freeze at the moment. This caused us issues.

    • Gloridel MoralesMicrosoft employee 0

      Hi Stuart. We are very sorry for the downtime and impact this caused. We will do a public postmortem on this incident, as it impacted a lot of customers. We made the decision to push the image update because we had other customers who needed it to get unblocked.

Feedback usabilla icon