Data Residency for Marketplace Apps Status Update

[PurnaChandraBoyapati]

@SushantBista

• Tenant pinning API: We are currently looking into feasibility of providing an API for Marketplace Partners to identify the current pinned location of a tenant’s host product.
• App data migration estimations: We plan to introduce a new API for apps to provide a time estimate for an app data migration for a particular tenant/installation. This will aim to align the customer experience between the host product migrations and app migrations, and ensure the customer has the relevant information to plan for any required downtime.
• Realm pinning persistence for app re-installs: We are looking into updating the existing realm pinning flows to enable realm persistence during an app re-install. This will ensure existing app data sets remain in the same realm as the app installation. Further, the pinned realm for an installation can only be changed by the customer using the realm migration service.

Hi @SushantBista
have a question around Dataresidency

1. Lets say we have a Connect App( NOT complaiant with Data residency) and we have a customer using it (has some data of the customer stored with APP).
2. Later we enable Data residency for the APP and release the APP
3. Lets say the Tenant Host is in EU region, and since APP enabled EU region we start getting traffic to
   EU based regional baseURLs (i.e to store and process the Data in EU) one question here is how do we identify Proximity vs User pinning a region
4. How do we handle the data created when the app was not Data residency complaint ? do we handle migration of it too (i.e copy the data created in step 1 global to EU region ?)
   or is it guarenteed to be treated as global as mentioned here How to migrate customers to the correct region after releasing data residency support - #4 by SushantBista

please let us know(questions asked in 3&4 above) this seems to be critical information.

Thanks,
Purna.