Forum Discussion

Burma's avatar
Burma
Helper I
8 years ago

Privacy Levels control - where is it?

Hi,

 

I'm having an issue configuring privacy levels for data sources in Power BI service. It's manageable in the Desktop, but I can't find any option for that in the online service, does it even exist?

 

What I've noticed, is that privacy level settings for data sources set in Power BI Desktop are simply ignored when publishing online. Furthermore, the privacy level is implied from the credentials I set online for the data sources. I.e.:

  • If I use anonymous connection to the data source, it is implied to be Public (even if I set it as Organizational in the desktop)
  • If I use organizational credentials for a data source, it is implied to be Organizational (even if I set it as Public in the desktop)

Is there any way around it?

 

Underlying issue: I need to call a web service (that I myself develop within my company) with a POST request & Body. In Power BI it is forbidden to use anything but anonymous authentication for Web.Contents when Content is specified (as in here:

Web.Contents("https://....azurewebsites.net", 
	[Headers=
		[#"Content-Type"="application/json", 
		#"x-functions-key"="..."], 
	Content = Json.FromValue([Parameter = #"Table"]), 
	RelativePath = "/api/..."]
)

). The data that I need to pass the web service comes from a source, for which I need to use organizational credentials.

 

 

I am able to do this in Desktop without the setting "Ignore privacy levels when combining the data", because I set all the data sources as organizational, not public. When I publish this online, Power BI can't refresh mentioning incompatible privacy levels.

 

Any ideas?

Need Help

6 Replies

  • v-piga-msft's avatar
    v-piga-msft
    Resident Rockstar
    8 years ago

    Hi Burma,

     

    Based on the official document which has list:

     

    The Ignore the Privacy levels and potentially improve performance does not work in the Power BI service. As such, Power BI Desktop reports with this setting enabled, which are then published to the Power BI service, do not reflect this behavior when used in the service.

     

    You also could have a good look at this document Power BI Desktop privacy levels.

     

    Best Regaerds,

    Cherry

    • Burma's avatar
      Burma
      Helper I
      8 years ago

      v-piga-msftCherry, thank you for the advice, however that's not the issue. As I've mentioned, we are not using "Fast Combine" or "Ignore Privacy Levels" options, even in the Desktop (and everything works fine). The issue is that Power BI Service does not allow manual classification of the data sources, so we can't assign "Private" or "Organizational" or "Public" for the data source. Instead, privacy levels for the data sources in Power BI Service are automatically deduced from the type of authentication used, which creates a compatibility issue.
       
      There is an option to assign privacy levels (even for the could data sources) in On-Premises Data Gateway, however that scenario is also not viable, because On-Premises Data Gateway does not support OAuth2 authentication, which is required. Also going that direction would be redundant, because gateway is unnecessary for the cloud data sources.
       
      The easiest approach for the product team might be:

      • Allow the privacy levels classification of the data sources in Power BI Service manualy, instead of doing it automatically now
      • Allow other types of authentication for Web.Contents besides "Anonymous" (even when Content payload is set)
      • Enable OAuth2 in On-Premises Data Gateway (that, however, is not very good)
      • v-piga-msft's avatar
        v-piga-msft
        Resident Rockstar
        8 years ago

        Hi Burma,

         

        Firstly, Power BI only support anonymous authentication for Web.Contents currently.



        The easiest approach for the product team might be:

        • Allow the privacy levels classification of the data sources in Power BI Service manualy, instead of doing it automatically now
        • Allow other types of authentication for Web.Contents besides "Anonymous" (even when Content payload is set)
        • Enable OAuth2 in On-Premises Data Gateway (that, however, is not very good)


        For your first two suggestions, you could submit your ideas in Power BI idea Forum and         add your comments there to improve Power BI and make this feature coming sooner.

         

        For the third suggestion, it has been supported in Power BI Service currently, you could find the option under Manage Gateway.

         

         

         

        Best Regards,

        Cherry