What is Atlassian Cloud Data Residency?

The Australian software company is steadily implementing changes to Atlassian Cloud tools in its transformation process. This time, you should learn more about a feature that allows you to locate where to store the data you handle in your Atlassian products. Learn more about the details of the data residency for Atlassian Cloud products.

Atlassian Data Residency is a feature that allows global administrators of Atlassian Cloud tools to specify where to host certain pieces of information from their tools, known in IT as regions or "realms," distributed among different locations. It's currently possible to choose between the European Union, the United States, or globally.

This feature is useful for organizations that operate in regulated areas, and in some cases, it might be the point of decision about whether or not to migrate to Jira Cloud. This feature is currently available for the Enterprise Cloud plan and for the new Standard and Premium plan subscriptions without extra cost.

Everything you need to know about Atlassian Cloud Security >>

What is data residency, and how do I know if I need it?

Atlassian data residency allows you to control where the data is hosted in Jira Software, Jira Service Management, and Confluence and allows you to choose to distribute the data globally or to a defined geographic location, such as Europe or the USA. Atlassian is currently working on offering it in Australia, Canada, the UK, and Japan.

This feature is often attractive to organizations that operate in regulated industries such as finance, government, or healthcare and may be necessary for them to operate in a cloud environment. In other cases, it generally helps meet enterprise data management requirements.

Initially, this feature was exclusively available in the Cloud for Enterprise plan, following the Atlassian Cloud First strategy, and as of June 30, 2021, Standard and Premium plans also have it available for new subscriptions. Throughout October 2021, existing cloud subscriptions will also have this feature. It's important to remember that this functionality does not incur an additional cost, as it's implementing a native feature.

Estimating Atlassian Cloud migration costs >>

Once operating, data residency allows you to see where the data included in the scope of your tools are hosted by your organization's administration (admin.atlassian.com). To do so, you must have administrator permissions. From there, access the data residency option in the security section.

This page will list the products in your organization, the location of each product, and the AWS regions to which the location corresponds. If a product is pinned to a location, your data included in its scope remains in place. You'll also be able to request to pin your data to a new location in case it is available for X tool and X location.

Differences between locations and AWS regions

The location of a product is the geographic boundary where the data included in that scope is housed, and each location corresponds to one or more AWS regions, which are physical locations around the world where AWS pools its data centers, as illustrated below:

It's important to note that there are limitations for some locations, such as Switzerland, where the Atlassian Data Lake is unavailable. The same applies to some functions regarding Atlassian Analytics, Opsgenie reports, and Assets reports. You can learn more about it here.

By default, all tools are hosted in the global location, including all AWS regions, as shown in the table above. For these tools, Atlassian determines where the data included in the scope is located, and to optimize the performance of the tools, they do not limit the movement of data from these tools and move the data between AWS regions as needed.

In the event that you need the in-scope tool data to remain in a specific location and the data residence is available to your tool, you can request that the in-scope data be moved to a specific location and pinned there.

Atlassian Cloud data residency doesn't store all data

Atlassian is committed to guaranteeing security in the Cloud, complying with standard security certificates and other measures, and carrying out a global privacy program complying with GDPR requirements, CCPA, LGPD, and more, requirements that have led them to treat all user data in the same way, using technical and organizational measures to protect the information they store (and what they don't). Atlassian's privacy program is designed to meet both legal requirements and the needs of each cloud product's customer.

Please find below what information Atlassian doesn't commit to storing for data residency in cloud tools:

1. User account information

Atlassian stores user account information in a central identity service and a small controlled set of replication services; however, they don't lock these services or user account information into them because they host them around the world to meet the performance needs of our customers.

Atlassian processes information this way to limit its footprint within organizations' systems, i.e., that information is not stored at all. Instead, they store representative IDs that they use to retrieve information from their identity services. Because of this, data residency cannot be applied to user data. If this is a challenge for you, we invite you to read more about it at the Atlassian Trust Center we've shared before.

2. Jira Service Management data works with Opsgenie

Put simply, Jira Service Management combines the capabilities of what used to be known as Jira Service Desk with the incident management offered by Opsgenie, which, according to Gartner, has turned this tool into a visionary ITSM solution.

Currently, the Jira Service Management functions powered by Opsgenie are not embedded in the Jira platform, so they are unsuitable to be fixed to a location. This is one of Atlassian's to-do items on its roadmap for Cloud that you can check at any time. Nevertheless, consider the following:

•    Certain Jira Service Management product data will always be hosted in the US, even if you choose to have your Jira Service Management in the EU.
  
  
•    When you move your Jira Software and Jira Service Management, you will experience downtime, although users can still access the features offered by Opsgenie.
  
  
•    If you have an Opsgenie that is not integrated with Jira Service Management, you can host certain data in the EU or USA.

What's Opsgenie, and how it helps >>

In Atlassian's documentation, you can learn more about data residency for Opsgenie.

3. Atlassian data residency and Marketplace Apps

Remember that the Atlassian Marketplace is a marketplace created by Atlassian partners that provide apps, such as ourselves, with Projectrak and Exporter. Therefore, Marketplace app data isn't covered by the data residency guarantee.

Atlassian is taking specific actions to enhance cloud capabilities. One of them is the recently announced Realm migration for Connect apps, a feature that allows users of particular apps in the Atlassian Marketplace (those developed on the Connect platform) to move their data from specific regions to others. You can find more information about this feature and how to implement it here.

However, different options are being explored to make this option available, and customers can choose the location where they want their application data to be hosted. If you would like to receive updates on the progress of these initiatives, you can check the cloud roadmap. Also, this Atlassian guide to data residency shows more about this option applied to Atlassian Marketplace apps.

Data residency advantages

•    Telling you where your Atlassian Cloud tools data and content is hosted.
  
  
•    Ensuring that Atlassian tool data, such as issues and pages, is stored only in the United States or European Union.
  
  
•    Meeting organizational and regulatory data compliance requirements.

There is a myth claiming that not enabling data residency will make Jira or Confluence perform faster, but that isn't entirely true. Atlassian uses its global infrastructure to host data as close to customers as possible to deliver maximum performance and productivity.
While data residency provides an additional level of certainty that the data will not leave the indicated geographic area, Atlassian's cloud infrastructure is designed to provide customers worldwide with the best possible experience. On the other hand, enabling data residency may result in slower overall performance for users outside the specified geographic area.

As you have read, data residency is a complex topic that needs to be evaluated in detail, as Atlassian is journeying toward the cloud, and its process of becoming a Cloud-First company is a scaled process. However, it is taking firm steps, and once again, we remind you that you can check the public roadmap of deployments they are making in Atlassian Cloud month by month. You can also check your possibilities by receiving help from experts in the area at the Atlassian Cloud Migration hub.