Best way to use Domains, Workspaces for GDPR regions??

Sep '24 • General

In my free trial of Fabric, I have been conceptually modelling how I would set-up the organisation to solve these business problems.

'Keep the data separated by geo/functional areas'

'Across all our geo-regions if this event occurs trigger a power automate flow to initiate a global response'

From what I have learned in various videos using domains and workspaces will sub divide the organisation into the various geo-regions or GDPR areas to allow multi-access.

Shortcuts can then be used to existing Data/Data Warehouses/Views in those regions in creating a new Fabric DW or an event table. A new reflex can then trigger Data activator into the resulting Power automate flows. (or whatever else is decided to trigger).

The questions I have, given the trouble I had with domains and workspaces,

Is this a good way to model geo political/GDPR/Cross departmental functions?

Have you done this differently? (e.g. Functional verticals then geo/region)

Has anybody set-up something similar like this that they would be willing to share here?.

Apologies for the simplistic diagram.

The assumption here is that the organisation sits on one Fabric instance, and data storage is within the GDPR/country domains as required.

Regards

Stuart

2 comments