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

Question

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

Simard, Bruno 20

Hello,

Seeking clarification on geographic redundancy for Azure DevOps Services. Current understanding: changing the region requires an explicit request. Company mandate requests geographic redundancy everywhere in Azure, including Azure DevOps Services. Questions:

Does Microsoft provide automatic geographic redundancy / failover for Azure DevOps Services in the event of a complete regional outage, or is recovery always a manual, request-driven process?
If a region becomes completely unavailable, what is the expected RTO and RPO for an Azure DevOps Services organization? Is there a documented failover process or SLA for this scenario?
Is there any supported mechanism to “fail over” an existing organization to another region quickly (self-service or expedited support), or must tenants be recreated/migrated?
Recommended best practices to achieve geographic resilience for Azure DevOps Services (backup/export strategies, multi-region designs, or alternatives) for enterprise requirements?
Which Microsoft support/engagement channel should be used to plan or request such redundancy for a production organization?

Any pointers to official docs, support processes, or contacts for planning geo-resilience for Azure DevOps Services would be appreciated.

Thanks.

Pashikanti Kumar 1,640 Points de réputation Personnel externe Microsoft Modérateur

2025-09-30T01:38:10.7833333+00:00
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
Simard, Bruno 20 Points de réputation

2025-09-30T12:37:58.9833333+00:00

Thanks for the quick response Pashikanti! No surprises here but it's good that it's official for us now. Have a nice day!

Réponse acceptée par l’auteur de la question

1 réponse supplémentaire

Votre réponse

Simard, Bruno 20 Points de réputation

2025-09-30T12:37:58.9833333+00:00

Thanks for the quick response Pashikanti! No surprises here but it's good that it's official for us now. Have a nice day!

Answer 1

Pashikanti Kumar 1,640 Personnel externe Microsoft Modérateur

salut Simard, Bruno,

Microsoft a récemment annoncé que les déplacements géographiques des organisations sont temporairement suspendus. Veuillez consulter le document ci-dessous pour plus de détails.

Image de l’utilisateur

https://learn.microsoft.com/fr-ca/azure/devops/organizations/accounts/change-organization-location?view=azure-devops

J'espère que la réponse fournie est utile.Veuillez "Accepter la réponse" si les informations vous ont aidé. Cela nous aidera ainsi que d'autres membres de la communauté.

Answer 2

DANIEL PELTE 23,900 Modérateur bénévole

Bonjour,

Sur ce forum on utilise la langue Française. Si ça vous dérange allez sur le Forum U.S.

Bonne continuation.

La modération.

Daniel

Partager via

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

1 réponse supplémentaire

Votre réponse