Hi @artema,
For the use case where the servers are located in a single region, EU in this case, it is a valid approach to define a single regionBaseUrl.
To comply with the data residency requirements, you’ll need to ensure that all the in-scope data is stored within this region.
With data residency, customers who pin their app to a region will not lose access to your app.
Within the customer facing data residency UI, customers who have their product pinned in EU will currently see the app pinned in global. If you adopt the additional regionBaseUrl and the realm migration APIs, these customers can then align their app traffic to EU. After a new version of the app with the EU realm support has been released, any new installations on products in EU will automatically pin towards the EU URL; however other regions will point to your baseURL or global.
The rollout of the data residency UI is planned to start on the 29th of March, see the the rollout Advance Notice: Connect Data Residency Customer Rollout topic about that.
Thanks,
Caterina