Forum Discussion
Interpretation of GUI window about privacy level
Anonymous You're right! Power BI’s privacy levels prevent combining Private (API key file) and Public (Azure Maps URL) sources in a single query for data protection. This blocks sending the API key if privacy levels differ.
Solutions:
-
Temporarily set both sources to Public (safe only for local dev).
-
Use "Ignore Privacy Levels" for the file (local testing only).
-
Move the API key to Azure Key Vault and set both to Organizational.
-
Use Power BI Service parameter credentials in production.
BBF
💡 Did I answer your question? Mark my post as a solution!
👍 Kudos are appreciated
🔥 Proud to be a Super User!
-
Hey there!
I tried to use that configuration (API-KEY = private, https://atlas.microsoft.com = public), but i got an error message, that these kind of data isn´t combinable:
Is it some kind of security issue, if i use the public attribute also for the api-key .txt - file? (what would be the consequences in this actual case?)
Can transmitting the api-key to the azure web service as a "combination"?
I first though, that the private option prevents, that the data get combined in a data model or query results, but sending the value to the web service is still possible?
Super UserAnonymous You're right! Power BI’s privacy levels prevent combining Private (API key file) and Public (Azure Maps URL) sources in a single query for data protection. This blocks sending the API key if privacy levels differ.
Solutions:
-
Temporarily set both sources to Public (safe only for local dev).
-
Use "Ignore Privacy Levels" for the file (local testing only).
-
Move the API key to Azure Key Vault and set both to Organizational.
-
Use Power BI Service parameter credentials in production.
BBF
💡 Did I answer your question? Mark my post as a solution!
👍 Kudos are appreciated
🔥 Proud to be a Super User!