Investigate a Power Query Privacy Block Without Disabling Source Isolation
A query that combines a local file with another data source can raise a privacy prompt even when both sources open individually. The issue may concern information exchanged while the query runs, rather than whether you personally can read the two inputs.
In Excel for Windows, first record the affected query and every source it combines. Describe what each contains and who is authorised to receive that information. Use source names rather than copying sensitive rows into a troubleshooting message.
Separate source classification from enforcement
Power Query privacy levels isolate data sources. Private is intended for sensitive or confidential information, Organizational for a trusted group, and Public for publicly available information. Query folding can turn transformations into source-side queries, so combining inputs may involve data movement beyond the final worksheet. Microsoft documents that privacy checks can block an exchange between sources.
Open Data, Get Data, Data Source Settings. Select the actual source and inspect Edit Permissions and its Privacy Level. Check the classification against the contents and authorised audience. A broadly accessible endpoint does not make the confidential file being combined with it public.
If ownership or the permitted destination is unclear, obtain that decision before loosening a classification. A reduced demonstration using fictional records can help describe the intended transformation without exposing the real inputs.
Keep the scope of a setting clear
Excel's Data, Get Data, Query Options contains Privacy settings for Global and Current Workbook scopes. These control whether the classifications are enforced. Microsoft warns that ignoring privacy levels, sometimes called Fast Combine, can expose sensitive information. Making a blocked query run is not evidence that its data movement is acceptable.
After an authorised classification correction, reopen the relevant setting to confirm the source and scope, then rerun the query. Record whether the original privacy message remains and whether the intended result loads. If it remains blocked, preserve the message and the source inventory for the workbook owner instead of disabling isolation as a general troubleshooting shortcut.
Finally, assess the audience of the resulting workbook separately. A correct query configuration does not decide which recipients should receive the finished data.
Sources: Microsoft: Power Query privacy levels; Microsoft: Excel privacy settings.