Share Your Experience: Data Residency in Cloud

[Uli Mauersberg]

Hi Enterprise Community!

My name is Uli, and I’m a Product Designer at Atlassian.

We’re currently exploring ways to enhance the Admin Hub Data Residency experience for cloud, and we’d love to hear your thoughts! 

We would love your feedback on the following:

• How do you currently use Data Residency?
• What aspects of the experience work well for you?
• What challenges have you encountered?
• Are there features or capabilities you wish were available?

Many thanks!

[Benedikt A.]

We use Data Residency in Europe. 

One of the biggest problem we had: when moving to our region, data from 3rd party products got lost without former hint. (Tempo Worklog)

Also, the Data Residency move was sheduled to a specific date, but the actual move was done two weeks later, which caused additional trouble, as we are date sensitiv due to billing processes and such.

To sum it up: we will not move to any other region again if we can avoid it in any way!

[Uli Mauersberg]

Thank you for taking the time to share your experience. We truly appreciate your feedback—it helps us understand where we can make meaningful improvements.

[Sami Shaik]

We use Data Residency from the EU. However, our apps execute from the US and other regions, which is causing some issues during workflow transitions.

[Craig Castle-Mead]

Hi Uli,

The registration link forces you to create an account and complete a full profile on userinterviews.com (including a lot of personal information). This isn’t the usual process that happens, had a similar issue with https://community.atlassian.com/forums/Enterprise-articles/Paid-research-opportunity-for-Atlassian-Administrators/ba-p/2999201?utm_source=atlcomm&utm_medium=email&utm_campaign=&utm_content=post earlier and Patrick said the research team helped resolve the issue. Suggest you contact them to resolve the issue. 

CCM

[Uli Mauersberg]

Thank you Craig

[Josh]

@Uli Mauersberg - I'm an enterprise customer with multiple instances including sandboxes:

For instances that do not have set (pinned) residency, the admin UI does not show where the data currently resides. it's just a — symbol in the Location column. However, the data sits in different AWS zones and we're able to see that when we connect Bring Your Own Storage locations for the Backup and Restore beta. It would be great if we could see where the data is in the admin UI, even if it isn't specifically pinned somewhere.

This might be outside the scope of the feedback that you're requesting, but we started experiencing timeout issues with the Atlassian Analytics delta share when the sources spanned multiple zones. We have a stopgap solution, but this would be another helpful thing to warn users about somewhere in the UI.

The ability to see supported locations per app in the instance is helpful. Would it be possible to highlight the lowest common denominator options for a given instance (e.g. "all apps support US and EU") as a summary? This functionality would be most helpful for larger instances with many apps in use.

The "APPS ELIGIBLE TO MOVE" visual at the top of the data residency page doesn't actually provide any information on the specific apps, so I'm wondering what function it's intended to serve?

[Kit Mitchell]

Thanks Uli! Australia is currently undergoing a large pivot across industries to ensure data is stored within the country. With the push to cloud, several organisations are delaying migration or simply not adopting your product because Bitbucket does not have any data residency options. Additionally, the delay to 2026 for this to be updated has had a negative impact on our ability to migrate customers or even upgrade customers this year. We now have to tell some customers that they will need to wait until next year - by then they may have found a different product that suits their needs.