We have a dataset in PowerBi.com that connects through the Enterprise Gateway to an on premise SSAS cube that we access through a direct connection. Security is implemented on the cube, and we can create local reports (PowerBi Desktop) by using this dataset in the service. This is all working as expecting.
At the moment, in PowerBi Desktop people can still create reports linked directly to the SSAS cube instead of using the dataset in PowerBi.com. This is possible because they do have access to the cube.
Is there a way that we can force end users to use this dataset, to avoid that they link directly to the SSAS cube?
Another way would be to avoid that they can publish reports that are created with a link to this SSAS cube?
Any suggestions on this topic?
Thanks in advance.
Evi Verschueren
Solved! Go to Solution.
@verscev The only thought I have off the top of my head would be to lock down the server that hosts the SSAS instance to only accept calls from the gateway server. That way, any IP that is not the server would fail. I haven't tried that, but I would think it could work.
@verscev The only thought I have off the top of my head would be to lock down the server that hosts the SSAS instance to only accept calls from the gateway server. That way, any IP that is not the server would fail. I haven't tried that, but I would think it could work.
Check out new user group experience and if you are a leader please create your group
100+ sessions, 100+ speakers, Product managers, MVPs, and experts. All about Power BI. Attend online or watch the recordings.