The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
i have created power bi dashboard which tracks pre sales activity in my company, this dashboard is using file uploaded on teams channel as data source. currently i am using my company (OAuth2) credentials to refresh the dashboard. if i leave company then dashboard would not be able to refresh. how can i make data credentials generic ( independent of invidiviual login) so that dashboard refresh is not impacted by user leaving the company
Solved! Go to Solution.
Hi @powerbiexpert22,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
Hi @powerbiexpert22,
Thank you for reaching out to the Microsoft fabric community forum. Also, thanks @m4ni, @wardy912, for those insights on this thread. Along with the super user’s solution this is an alternative to using personal credentials, you can store the source file (e.g., Excel or CSV) in a OneDrive for Business folder or SharePoint document library owned by a shared or service-managed account.
Then, in Power BI Desktop, connect to the file using the OneDrive Business or SharePoint Folder connector with a stable file path. After publishing the report, configure the scheduled refresh in Power BI Service using this account's credentials.
This ensures that the refresh remains unaffected if an individual user leaves. Make sure the account has the required permissions and a Power BI Pro license (or use a Premium workspace). This method provides a reliable, organization-owned data source.
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.
Thank you for using Microsoft Community Forum.
Hi @powerbiexpert22,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @powerbiexpert22,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hi @powerbiexpert22,
I hope this information is helpful. Please let me know if you have any further questions or if you'd like to discuss this further. If this answers your question, please Accept it as a solution and give it a 'Kudos' so others can find it easily.
Thank you.
In such cases its is best practice to use an account with elevated permissions but not linked to a user. Usually admin accounts or service principles can be created for this purpose. Your IT division should be able to create a dedicated account under Entra ID (assuming you're using Azure identity) which has the ability to refresh and its not going to be removed when someone leaves.
The account usually has a workspace admin level permissions.
HTH.
The easiest solution would be to create a service account.
Use this account to:
This ensures that the refresh process is not tied to any individual employee