Forum Discussion
Community ChampionApp registrations in Azure (One app or multiple)
We are coming across lots of possibilities to create App registrations in Azure for Power BI. for example
1. To run the Admin APIs to create reports against usage
2. to use Power BI Embedded
3. To Run dataflow and dataset data refreshes via Azure data factory instead of in Power BI Service (so they always run concurrently after the data has refreshed)
What we are wondering is. Would you create a power BI app registration for every possibility or would you create App registrations for each individual use case.
For example if you have 4 Workspaces HR, Sales, Admin, Orders and each has their own dataflows and datasets.
Would you create an app registration for each area. Or do you have one app registration that every service can use to run their dataflows and datasets?
Im thinking an app for each use case with a good naming convention?
Hi Debbie. I think it depends on the use you will give later. If you just need Apps Registration to use the API to control refreshes in a unique place, then you can go with just one app that helps IT to administrate all. But if you want to allow each department or workspace to keep their own access to the API to do X operations, then you might need one for each.
I have always used one because it's usually an admin or IT development like a service account.
I hope that helps,.
2 Replies
- ibarrau
Super User
Hi Debbie. I think it depends on the use you will give later. If you just need Apps Registration to use the API to control refreshes in a unique place, then you can go with just one app that helps IT to administrate all. But if you want to allow each department or workspace to keep their own access to the API to do X operations, then you might need one for each.
I have always used one because it's usually an admin or IT development like a service account.
I hope that helps,.
- DebbieE
thank you. Thats really useful
