Skip to main content
Two women looking at different data statistics and thinking about its location.

Data residency for Atlassian Cloud product plans

Alice Bakhoff

Last year Atlassian gave their Enteprise (the most expensive, but also with the largest number of features) plan customers the possibilty to choose, where their product data is hosted.

 

Understandably, a feature like this caused a desire among many customers on Standard and Premium plans to also choose where their data is located.
 

 

 

Data residency now available also for Standard and Premium plans

Nevertheless, Atlassian didn’t leave the feedback from their customers unattended and in July 2021 they announced the following:

  • existing Cloud subscriptions will have data residency turned on without any additional costs for use by autumn 2021 (September-October).
  • new Cloud subscriptions created on or after June 30, 2021 will have data residency turned on and available for use.

 

Data residency is available for Jira Software, Confluence and Jira Service Management products.



Atlassian divides data locations into three groups: global (including Singapore, Australia, Germany, Ireland and US-East and US-west), Europe and the United States of America. By default, the data is hosted in the nearest data center.


Atlassian is also working on adding additional locations like Australia, Canada, Japan and United Kingdom. 

 

What kind of data can and can not be pinned?

Briefly it can be said that user account information, technical information and analytical data can not be pinned. Data added to Jira tickets (attachments, comments, descriptions etc.) and Confluence page and field data can be pinned, for example to EU region.

 

The following table lists in-scope product data types that can be pinned, and out-of-scope product data that can’t: 

 

Product Can be pinned Can't be pinned
Jira Software
  • all attachments
  • board and sprint data
  • comments
  • in-product notification data
  • Jira issues and field content (including system and custom fields)
  • Jira search data
  • project configuration data (including workflows, custom field configuration, and board configuration)
  • connected DevOps data (including commits, branches, pull requests, builds, deployments. feature flags, remote links)
  • product analytics

 

Jira Service Management

  • all attachments
  • comments
  • in-product notification data
  • Insight object data and schema configuration data
  • Jira issues, request types, and field content (including system and custom fields)
  • Jira search data 
  • project configuration data (including workflows and custom field configuration)
  • queue data
  • all Jira Service Management features powered by Opsgenie
  • customer accounts
  • incident management functionality data
  • knowledge base category data (if integrated with Confluence)
  • product analytics
  • SLA configuration data
Confluence
  • all attachments
  • comments
  • Confluence page and blog data
  • in-product notification data
  • page and comment likes
  • page metadata
  • source data for notifications in emails
  • permission and restriction configuration data
  • product analytics 
All products  
  • Atlassian Marketplace and app data
  • cached content (up to 30 days)
  • data in transit (up to 30 days)
  • product, audit, and operational logs
  • product analytics
  • team profile information data
  • third-party product integration data
  • user account information data
  • user analytics

 

Why some data can not be pinned? 

Similarly to Microsoft, Atlassian hosts some data in different locations.

 

Atlassian stores user account information in a central identity service, and a small, controlled set of replica services. They don’t pin these services, and the user account information in them, because it is hosted around the world to meet the performance needs.


It means that this information is not stored in Atlassian’s products at all. Instead, the products store representative IDs that they use to retrieve it from their identity services.

 

Atlassian Trust Center describes their Cloud platform security and privacy standards in more detail.

 

Atlassian Marketplace is comprised primarily of third-party app partners. These partners are not a part of Atlassian. However, Atlassian is working on the ability for the customers to choose the location where their app data is hosted.


Jira Service Management features powered by Opsgenie aren’t incorporated into the Jira platform and aren’t eligible to be pinned to a location.

 

Opsgenie as a standalone has the possibility choose some of the data location (in the EU or US).

 

 

If you need any additional information…

We will be happy to explain the different aspects regarding data residency in Atlassian Cloud product platform in more detail. 

 

If you are new to Atlassian and need some additional information or help, do not hesitate to contact us; we provide consultations and trainings and can help with everything regarding Atlassian products and plugins. 

 

 

Add new comment

Plain text

  • No HTML tags allowed.
  • Lines and paragraphs break automatically.
  • Web page addresses and email addresses turn into links automatically.