ADX purpose if using Fabric and multi-tenant support with a single Fabric instance

[steveohooto]

Hi all,

Having a good play with FinOps Hub and seem great! I have a couple of questions regarding architecture...

1. Is ADX required if using Fabric? We're using Fabric and pointing to that for our dashboards and got the reports working too. Looks fabs. This is in our test environment and as part of it I can see the dashboard in ADX (even though I can't see an ADX cluster in the resource group?!). When we redeploy in production, can we skip ADX entirely? Just let Fabric suck in the data from the Ingestion container in the storage account?

2. Any concerns in making a minor fork around the architecture, where each tenant of our group has their own storage account account that has the msexports and ingestion containers. We'd then have a single Fabric instance with each tenant having their own Workspace. Probably have a unique ADF per tenant too. For reasons of chargeback and politics. Wondered if anyone has any feedback or concerns on this approach?

Thanks