Forum Discussion
Interpretation of GUI window about privacy level
- 1 year ago
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!
-
Anonymous Try to set in this way:
| Data Source | Privacy Level |
|---|---|
C:\api-key.txt |
Private |
https://atlas.microsoft.com |
Public |
If the privacy levels are incompatible (like combining a Private and a Public source), Power BI blocks the operation β or isolates them (which sometimes makes the query inefficient or impossible to run, depending on how data needs to flow).
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?
- BeaBF1 year ago
Super User
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!
-