Forum Discussion
Power Bi refresh
Hi Alll
I am getting below error while trying to refresh the PBI semantic model of my workspace and have been struggling for quite some time but not find the solution and the error is still there.
However when i do the manual refresh on power bi desktop on my virtual machine, it refreshes without any error.
I have tried to play with the security setting by switch it to ''Organisational / Private ,etc'' but it didn't solve it.
Grateful if someone can help to it.
Data source error: {"error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","pbi.error":{"code":"DM_GWPipeline_Gateway_MashupDataAccessError","parameters":{},"details":[{"code":"DM_ErrorDetailNameCode_UnderlyingErrorCode","detail":{"type":1,"value":"-2147467259"}},{"code":"DM_ErrorDetailNameCode_UnderlyingErrorMessage","detail":{"type":1,"value":"Information is needed in order to combine data. Please specify a privacy level for each data source."}},{"code":"DM_ErrorDetailNameCode_UnderlyingHResult","detail":{"type":1,"value":"-2147467259"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.DataSources","detail":{"type":1,"value":"[{\"kind\":\"Oracle\",\"path\":\"nfkl\"},{\"kind\":\"SharePoint\",\"path\":\"https://florealmu.sharepoint.com/sites/DigitalProjectsVaddis\"}]"}},{"code":"Microsoft.Data.Mashup.MashupSecurityException.Reason","detail":{"type":1,"value":"PrivacySetting"}}],"exceptionCulprit":1}}} Table: VD_TB_ACC_V1_ALL.
Cluster URI: WABI-WEST-EUROPE-redirect.analysis.windows.net
Activity ID: 7b5c331e-57dc-4fb0-ac10-8fc3dd06dd6a
Request ID: b4f1974a-78ba-5e87-aa05-9c707226f468
Time: 2025-05-21 08:17:47Z
Hi Naaib,
Thank you for reaching out to the Microsoft fabric community forum. Additionally, thank you to christinepayton, for his input regarding this issue. I have identified several alternative workarounds that may assist in resolving the thread.
To resolve this issue, start by opening your report in Power BI Desktop and checking the Power Query Editor for any steps that combine Oracle and SharePoint data using operations like Merge or Append. These operations trigger Power BI's privacy level enforcement, which must be explicitly configured for refreshes to work in the Power BI Service.Next, go to File > Options and Settings > Options > Privacy and ensure that “Always combine data according to your Privacy Level settings” is enabled. Then open Data Source Settings, select each data source, click Edit Permissions, and set both Oracle and SharePoint to Organizational (or Private, if appropriate). Re-authenticate if required.
After saving these settings, re-publish the report to Power BI Service. In the Service, go to your workspace > dataset > settings. Under Gateway Connection, verify that the On-premises Data Gateway is online and that both data sources are correctly configured under the same gateway cluster.
Then, in the Data source credentials section, enter valid credentials and set the privacy level to match the one used in Desktop (Organizational is recommended). Save the changes and perform a manual refresh in the Service to confirm the fix. If successful, you can proceed to set up a scheduled refresh.
Kinly refers to the below following documentation links for better understanding:
Privacy levels in Power Query - Power Query | Microsoft Learn
Configure scheduled refresh - Power BI | Microsoft Learn
Troubleshoot gateways - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.Thank you again for reaching out on the Microsoft Community Forum.
Hi Naaib
You're encountering the following Power BI error when trying to refresh a dataset in the service:
This is a Privacy Level issue between multiple data sources (Oracle and SharePoint). Power BI enforces privacy boundaries during mashup operations (when combining data from different sources). It behaves differently in Power BI Desktop versus Power BI Service.
Configure Privacy Levels Correctly in Data Gateway
Since your data comes from both Oracle and SharePoint Online, and you're likely using a Gateway (for Oracle), follow these steps:
1. Go to Power BI Service > Settings > Datasets- Find your dataset
- Click on “Settings”
- Scroll to Gateway connection and Data source credentials
2. Edit credentials for each data source- Ensure both Oracle and SharePoint data sources are added to the same Gateway cluster
- Set privacy levels:
- Choose Organizational for both, or Public if the data isn’t sensitive and it’s safe to combine.
3. Save and retry the refresh
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!
9 Replies
Hi Naaib,
Thank you for reaching out to the Microsoft fabric community forum. Additionally, thank you to christinepayton, for his input regarding this issue. I have identified several alternative workarounds that may assist in resolving the thread.
To resolve this issue, start by opening your report in Power BI Desktop and checking the Power Query Editor for any steps that combine Oracle and SharePoint data using operations like Merge or Append. These operations trigger Power BI's privacy level enforcement, which must be explicitly configured for refreshes to work in the Power BI Service.Next, go to File > Options and Settings > Options > Privacy and ensure that “Always combine data according to your Privacy Level settings” is enabled. Then open Data Source Settings, select each data source, click Edit Permissions, and set both Oracle and SharePoint to Organizational (or Private, if appropriate). Re-authenticate if required.
After saving these settings, re-publish the report to Power BI Service. In the Service, go to your workspace > dataset > settings. Under Gateway Connection, verify that the On-premises Data Gateway is online and that both data sources are correctly configured under the same gateway cluster.
Then, in the Data source credentials section, enter valid credentials and set the privacy level to match the one used in Desktop (Organizational is recommended). Save the changes and perform a manual refresh in the Service to confirm the fix. If successful, you can proceed to set up a scheduled refresh.
Kinly refers to the below following documentation links for better understanding:
Privacy levels in Power Query - Power Query | Microsoft Learn
Configure scheduled refresh - Power BI | Microsoft Learn
Troubleshoot gateways - Power BI | Microsoft Learn
Data refresh in Power BI - Power BI | Microsoft Learn
If this post helps, then please give us ‘Kudos’ and consider Accept it as a solution to help the other members find it more quickly.Thank you again for reaching out on the Microsoft Community Forum.
Hi Naaib,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi Naaib,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
The error is about privacy levels -y ou can find these settings in Power BI Desktop under data source settings. It sounds like your file contains multiple data sources, and when you do this you need to set the privacy level on all sources to the same level or refresh will fail. It's not an auth type thing, it's its own dropdown in the settings for each source.
Hi Naaib
You're encountering the following Power BI error when trying to refresh a dataset in the service:
This is a Privacy Level issue between multiple data sources (Oracle and SharePoint). Power BI enforces privacy boundaries during mashup operations (when combining data from different sources). It behaves differently in Power BI Desktop versus Power BI Service.
Configure Privacy Levels Correctly in Data Gateway
Since your data comes from both Oracle and SharePoint Online, and you're likely using a Gateway (for Oracle), follow these steps:
1. Go to Power BI Service > Settings > Datasets- Find your dataset
- Click on “Settings”
- Scroll to Gateway connection and Data source credentials
2. Edit credentials for each data source- Ensure both Oracle and SharePoint data sources are added to the same Gateway cluster
- Set privacy levels:
- Choose Organizational for both, or Public if the data isn’t sensitive and it’s safe to combine.
3. Save and retry the refresh
🌟 I hope this solution helps you unlock your Power BI potential! If you found it helpful, click 'Mark as Solution' to guide others toward the answers they need.
💡 Love the effort? Drop the kudos! Your appreciation fuels community spirit and innovation.
🎖 As a proud SuperUser and Microsoft Partner, we’re here to empower your data journey and the Power BI Community at large.
🔗 Curious to explore more? [Discover here].
Let’s keep building smarter solutions together!Hi Naaib
Your refresh is failing in the Power BI Service because you're combining data from two sources—Oracle (on-prem) and SharePoint (cloud)—and Power BI needs matching privacy levels set to combine them securely. While it works in Power BI Desktop, the Service enforces stricter rules and throws an error if privacy settings conflict.
To fix this:
-
In Power BI Desktop, go to Data Source Settings, and set both Oracle and SharePoint to the same privacy level (e.g., Organizational).
-
Re-publish the report after setting this.
-
Make sure your Oracle is correctly mapped in the gateway, and SharePoint is treated as a cloud source.
-
Avoid using “Ignore Privacy Levels” unless you’re testing—it won’t apply in the Power BI Service.
This should resolve the refresh error you're seeing.
-
