Advance Notice: Connect Data Residency Customer Rollout

[SeanBourke]

Hi @NikitaKamai,

@NikitaKamai

While so far it looks as now the status for the app is to be Not Eligible because of this, which in reality has nothing to do with how things are.

I appreciate that similar feedback has been shared by the community and this has been shared with the customer facing UI team. We are currently exploring how we can better represent app statuses to customers. In the interim, I recommend ensuring that you have accurately completed your Privacy and Security tab responses, as this is likely to be used by customers to better understand how an app utilises and stores their data.

@NikitaKamai

However, our customers are deeply concerned about data transition, which in fact takes place through our servers on occasions of content exporting and for some of the macros parsing. These cases are directly related to customer data handling and as such are part of the Data Residency.

While adoption of data residency and realm migrations has primarily been focused around in-scope data, I also appreciate that some partners have adopted data residency within their Connect apps for other reasons, such as server proximity to customers. If you already support data residency, or believe it would be valuable, extending that to also support realm migrations helps to ensure that your app pinning is aligned to the customer’s product.