My organization uses a number of developers that regularly cycle on and off projects, and would like to centralize ownership of data configurations for numerous reports with different data sources via a single 'service' account.
Does anyone have insight into the potential challenges of this desired state? We currently use a variety of data sources (including AAS, SQL db, SharePoint files) and we know that the service account would likely require access to all of these data sources.
(As an aside, we currently copy our IT help desk if a data refresh fails, via the Schedule Refresh menu)
Solved! Go to Solution.
Yes, we're currently using the new feature to send an email to a service account for dataset failure notifications.
However, there is still a strong desire to configure and manage our data sets via a service account.
Are we likely to experience problems if we utilize a service account in that way?
can you provide some more details on this?
Actually I am looking to do the same for my dataset i.e. configure the scheduled refresh using a service account.
Does this mean I use "Windows" authentication and I have to login to Power BI using my service account so that it uses its credentials for windows login?
If yes, this means I also provide a Power BI license to service account.
Check out the November 2023 Power BI update to learn about new features.
Read the latest Fabric Community announcements, including updates on Power BI, Synapse, Data Factory and Data Activator.
130+ sessions, 130+ speakers, Product managers, MVPs, and experts. All about Power BI and Fabric. Attend online or watch the recordings.