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

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
earg73
Advocate III
Advocate III

DirectQuery in Power BI

I tried to load some views using DirectQuery mode and I get the error message "Impersonation is not supported in DirectQuery mode. Turn off impersonation or switch to import mode."  What does this mean?

1 ACCEPTED SOLUTION

@earg73 I was able to fix this error by ensuring that the user that i'm using to connect to the SQL server was specificity mapped as a user on the actual database contained within my view. even if your user is a admin make sure that they are also mapped to the db that your view is accessing. 

Business Intelligence Architect / Consultant

View solution in original post

23 REPLIES 23

@earg73 I was able to fix this error by ensuring that the user that i'm using to connect to the SQL server was specificity mapped as a user on the actual database contained within my view. even if your user is a admin make sure that they are also mapped to the db that your view is accessing. 

Business Intelligence Architect / Consultant

I'm getting the same issue.  Let me ask if the circumstances are similar:  When importing (get data), I'm logging onto a SQL server database on a local machine or network server. I have to specify credentials for logon (impersonation) because the default for login username uses a concatenation of computername and username (mycomputermyusername)instead of mynetworkname\myusername.  I have to do this for SSIS and SSAS as well, but they have no issues with impersonation. 

 

My thought is that import is set up to allow impersonations, but direct query is not.  Unless I can set the default for the login username, it looks like the only way to bring in the data is by import.

 

Any ideas?

Anonymous
Not applicable

I'm thinking that perhaps it has something to do with the EffectiveUsername property setting, which is explained pretty nicely in the knowledge base (LINK).

 

Have you verified that this setting is working properly?

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.