Is there a fast / automatic geographic failover option for Azure DevOps Services?

Hi Simard, Bruno,

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Here is a detailed response addressing your questions about geographic redundancy and failover for Azure DevOps Services:

Automatic Geographic Redundancy / Failover

• Azure DevOps Services currently does NOT provide automatic geographic failover in the event of a complete regional outage.
• Recovery or failover is a manual process initiated by Microsoft upon explicit request. Customers cannot self-trigger failover to a different region.
• Changing the Azure DevOps organization region requires contacting Microsoft Support, and is not an instant or automated operation.

Recovery Time Objective (RTO) and Recovery Point Objective (RPO)

• Official Microsoft SLAs for Azure DevOps specify 99.9% availability, but detailed RTO and RPO values for region-wide disaster recovery are not publicly documented.
• In case of a region outage, failover timing depends on:
  • The magnitude of the outage.
    • Microsoft’s operational decision to initiate failover to the secondary region.
      • Data replication lag between primary and secondary regions (typically asynchronous).
• Expect some data loss (RPO) and downtime (RTO) during failover due to asynchronous geo-replication.

Supported Failover Mechanisms

• There is no supported self-service or expedited failover mechanism for customers to switch Azure DevOps organizations between regions.
• Organizations must be recreated or migrated with Microsoft assistance if the region becomes unavailable.
• Microsoft may perform planned or unplanned failover for severe outages, but this is not under customer control.

Use Azure DevOps Support plans through the Azure portal or Microsoft Premier support for production-impacting incidents.

Engage Microsoft Account Managers or Customer Success Account Teams early for custom geo-resilience planning.

Best Practices for Geographic Resilience

• Backup and export your data regularly: Use Azure DevOps Services export features or third-party tools to backup repos, pipelines, and artifacts to external storage or alternate regions.
• Multi-region design: Currently limited in Azure DevOps; consider segmenting teams/orgs across regions if critical to operations.
• For critical workloads, integrate with Azure Repos Git mirror and external artifact repositories with geo-redundancy.
• Be prepared with disaster recovery and restore plans, including export/import of critical data using APIs.

Reference

Data protection overview - Azure DevOps Services | Microsoft Learn

Azure Support Plans Comparison | Microsoft Azure