Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowThis browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Azure DevOps Services
You can choose the location for your data during initial sign-up and creation of your organization.
Azure DevOps data is available in the following geographical locations:
By default, your organization uses the closest location. However, you can choose a different location when you create your organization. If you change your mind later, you can migrate your organization to a different location.
Except as noted later in this article, Azure DevOps maintains all customer data within your selected geographical location. Customer data includes the following data types:
Azure DevOps works with and uses many Microsoft Azure services. For more information on customer data retention by location, see Data residency in Azure.
Azure DevOps stores information that's global in nature, such as user identities and profile data, as follows:
Azure DevOps stores token data, such as personal access tokens and Secure Shell (SSH) keys, in a US datacenter.
We recommend using groups with your tenant policy allowlists. If you use a named user, be aware that a reference to the named user's identity resides in the US, EU, and Southeast Asia (Singapore).
We don't transfer customer data outside your selected location. However, we transfer your data if we need to take any of the following actions:
If necessary, you can transfer your data by using preview, beta, or other prerelease services. These services typically store your data in the United States, but they might store it globally.
Note
For builds and releases that run on Microsoft-provided macOS agents, your data is transferred to a GitHub datacenter in the United States. GitHub owns and manages this datacenter location with compliance certifications, such as SOC 1 Type 2 and SOC 2 Type 2.
Microsoft doesn't control or limit the locations from which you or your users can access your data.
Note
Because there's only one region in Brazil, customer data in Brazil is replicated to the South Central US region for disaster recovery and load balancing. For more information, see Data residency in Azure.
Events
Mar 17, 9 PM - Mar 21, 10 AM
Join the meetup series to build scalable AI solutions based on real-world use cases with fellow developers and experts.
Register nowTraining
Certification
Microsoft Certified: DevOps Engineer Expert - Certifications
This certification measures your ability to accomplish the following technical tasks: Design and implement processes and communications, design and implement a source control strategy, design and implement build and release pipelines, develop a security and compliance plan, and implement an instrumentation strategy.
Documentation
Find or change the geography of your organization - Azure DevOps Services
Find your organization's default location or update your organization's region in Azure DevOps.
Data protection overview - Azure DevOps Services
Learn how Microsoft helps protect your projects and data in Azure DevOps.