Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
tsinclair
Regular Visitor

Azure SQL Datasource Credential Storage

I have two workspaces (WorkspaceA and WorkspaceB) set up in PowerBI Web each containing independant datasets that connect to the same Azure SQL Database.

The database contains multiple schemas (SchemaA and SchemaB). Two users have been set up on the database (UserA and UserB) with minimal read access to their respective schemas. UserA should not be able to access SchemaB and UserB should not be able to access SchemaA.

Credentials are entered into this form from within the dataset settings for each workspace -

 

image.png

 

In PowerBI I enter my connection details for the Azure SQL datasource in WorkspaceA -

 

servermy-test-sqlserver.database.windows.net
databasemy-test-database
Authentication methodBasic
User nameUserA
Passworduser_a_password
Privacy levelPrivate


I can then sign in and refresh the dataset with no issues.

I then setup the connection details for the Azure SQL datasource in WorkspaceB -

servermy-test-sqlserver.database.windows.net
databasemy-test-database
Authentication methodBasic
User nameUserB
Passworduser_b_password
Privacy levelPrivate


I can then sign in and refresh this dataset with no issues but if I then switch back to WorkspaceA and force a manual refresh of its dataset, I will then encounter this error -

 

image.png

 

The credentials entered for WorkspaceA's datasource have been overriden by the credentials for WorkspaceB's datasource even though each datasource has been set up with a privacy level of private, created within seperate datasets and published to seperate workspaces.

It seems the datasource credentials are tied to me as a user and identified based on the target database and server and are following me between workspaces rather than be restricted to a unique dataset which was the behaviour I had anticipated. Is there a setting somewhere that I may have missed that could resolve this or is this an issue with how datasource credentials are stored that may require some changes by Microsoft?

Changes to the permissions setup on the SQL side are not an option.

Any help is much appreciated.

Thanks!

1 REPLY 1
v-cherch-msft
Employee
Employee

Hi @tsinclair 

Please check if below posts could help.If it is not your case,you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

https://community.powerbi.com/t5/Service/Dataset-won-t-refresh-from-Azure-SQL/td-p/302239

https://community.powerbi.com/t5/Service/Error-The-SELECT-permission-was-denied-on-the-object-TABLES...

Regards,

Community Support Team _ Cherie Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.

Top Solution Authors
Top Kudoed Authors