Hi Community,
I’ve had several customer discussions on Rovo data residency in the past week, and I thought I’d highlight a few key topics customers were looking to address.
As you continue to scale AI enabled apps for Rovo, data residency becomes a top priority for many teams—especially those with strict compliance or regional requirements.
I want to clarity how Rovo’s data residency works, what types of Rovo data are pinned in-region, and how you can enable this for your org.
Data residency now gives you control over where your in-scope Rovo data is hosted, helping you meet your local compliance and regulatory requirements - or compliance requirements for your customers.
With data residency support now generally available for Rovo, you can pin your Rovo data to the same region as your Jira, Confluence, or JPD data—just like you do for other Atlassian cloud apps.
These data types can be pinned in-region: chat session logs, agent configuration, Rovo bookmarks, and third-party (3P) content data.
This means that each of these data types can be pinned within your selected geo to support your compliance with data residency requirements and organizational policies.
You’ll be able to select your preferred region and migrate Rovo data yourself.
Go to Atlassian Administration. Select your organization if you have more than one.
Select Security → Data residency.
Here’s our support page on data residency if you need more info and here are a few more FAQs:
Can I change my data residency region after initial selection? - Yes, you can request to have your in-scope app data pinned to a new location.
Can I stay up to date on additional locations Atlassian will support? Yes - see our cloud roadmap.
Where can I confirm my current data residency settings and regions? Navigate to Atlassian Administration → Security → Data residency.
Tx. Tom
Tom Pieterse
0 comments