Data Residency

Here are the three steps you can follow for configuring the data residency for Pio Applications.

Step 1: Read the Atlassian Documentation to Understand data residency provided by Atlassian.

https://support.atlassian.com/security-and-access-policies/docs/understand-data-residency/

Step 2: Review the following table listing in-scope data types that can be pinned and out-of-scope product data that can’t.

Product	✅ Can be pinned	❌ Can’t be pinned

Product	✅ Can be pinned	❌ Can’t be pinned
All Pio Marketplace Applications	All data stored in the Forge database Credentials Configurations Logs Audit Logs	Data in transit

As you have noticed, all the data stored by Pio Applications can be pinned. It is also good to note that Pio Importer Applications don’t store external data in the storage. They connect to external systems, i.e., Microsoft Entra ID (a.k.a Azure AD), Microsoft Intune, Jamf, Okta, Datadog, Salesforce, etc, and collect the data. Then, process all the information in memory for a few seconds and transfer the data immediately to JSM Assets. The data in transit is not stored and thus can not be pinned.

Step 3: Read the following Atlassian Documentation to pin Pio application data to a location.

https://support.atlassian.com/security-and-access-policies/docs/moving-your-marketplace-apps-data-to-another-location/