Datagateway yes or no? - or how to keep the Portfolio organized

[Anja-G]

Hello everyone,

we're introducing Power BI in our enterprise (currently running a proof of concept) and we're still trying to plan our future organisation of the tool concerning where does the data come from, if and how to schedule the updates and so on. My boss' stance is: only data that comes from our single source of truth, namely Azure DWH. Problem is - of course - there so much interest in this solution "Power BI" that it's impossible to route every single data via Azure DWH. Also, my opinion is: Power BI should be flexible enough that users can use their own data and build their own data model. But that kind of view will no doubt lead to uncontrolled growth of Datasources and countless connections and dead Dashboards that will never be used.

I know, we need data gateway to provide a platform for regular updates and automatic schedules and we will do that. But how do we stragetically plan the whole construct to make it as structured as possible without creating a monster?

How do you go about that situation? Is it possible for an admin to have an overview over every connection and govern it? How do you make sure, people don't "randomly" connect servers to Power BI with usernames and passwords they managed to get their hands on? After all, it's my responsibility to make sure the data is safe and governed and can't be seen by unauthorized coworker

[sergej_og · Accepted solution]

Hey Anja,
I think you have right thoghts about using gateway and keep your tenant as clean as possible not to become a monster.
You have different setting options as Service admin to cover a few of your requirements.
e.g. after setup and register a gateway in your tenant you can give people explicit right to use your gateway. So they can create their own connections and build their own reports. On the other hand these user have to know what they do - you have to teach them if you don´t want to have a messy tenant! 🙂
I think you will be the hoesekeeper for your tenant so protect yourself of unefficient (messy) tasks.
I do now and then a bit houesekeeping and kick some unused conncetions.

To protect data of unauthorized user you have also different options (different security levels).

It sound you have a big project in front of you.
Split this big picture in small ones and do not open everything for everyone 🙂
Thats my lesson learned so far.

Regard
Sergej

[Anja-G]

Hello Sergej,

thank you for your thought through answer. I will definitely keep your ideas in mind and I like your options. I didn't know about the managing options in the datagateway. This is a great way to keep the connections in check. 

Anja

[sergej_og]

Thank you Anja,
maybe one more thing. If you (as an admin) create a connection you can also give explicit permissions to use this one connection to your collegues. Not using the whole gateway only specific conncetions.
I think thats pretty cool to keep the thing clean and avoid a messy connection overview in your tenant.

Regards
Sergej

[Idrissshatila]

Hello @Anja-G ,

So in mu opinion, the data should be stored in a server that is always on. There should be an ETL process that gets data, transform it and store it in a data warehouse and makr this process automatic.

so now you have your data processed and stored in a warehourse, the role of the IT is to make restrictions and give access to this data so that not everyone can get to the data, only authorized users can do.

If I answered your question, please mark my post as solution, Appreciate your Kudos 👍

Follow me on Linkedin
Vote for my Community Mobile App Idea 💡