Forum Discussion
Dataflows Workload can not be disabled in Capacity with multi-geo
Currently in documentation on multi-geo dataflows are listed as non-supported feature:
Without any additional information on what is it that is not supported...
However when I configure and new capacity node and assign it to a different geography I notice a few curious things:
1. Dataflows Workload can not be disabled ( the switch off is greyed out) and limiting max memory for it is not possible(5% is min)
2. I am able to create dataflows in workspaces assigned to this new capacity just fine and even create reports based on dataflows stored in workspaces assigned to a different capacity
Can anyone with experience in multi-geo capacity configuration chime in and provide some clarifications here?
2 Replies
v-yingjlCommunity Support
Hi Anonymous ,
Did your account have service admin or global admin access if you cannot disable dataflows workload?
The minimum memory of dataflows depend on your capacity SKU:
You can refer this document: Configure workloads in a Premium capacity
Best Regards,
Yingjie LiIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Question is to why the Dataflows workload can not be disabled for the capacity located in remote region.
You can see on the screenshot that the workload is marked as active, but the toggle itself is shaded grey meaning that it can not be switched off.
Since documentation states that dataflows are not supported with multi-geo (I am reading this aka: they are stored by Power BI in ADLS Gen 2 in home tenant) I would think we should be able to disable them to discourage users from creating any and potentially breaking compliance/data residency requirements?
If I create capacity in home region dataflows workload behaves as expected and toggle is operational.
TIA