Dataflow Privacy settings changing on their own

[dbartel]

I have had problems with several dataflows.  They are running fine one day and the next, they will take an excessive amount of time to refresh.  What I have discovered is that the privacy settings for one of my connections has changed which in turn causes a mis-match between the two, causing the queries to work much harder.  

I am the dataflow owner and as far as I can tell, the only one who can change these settings, yet they changing on their own.  Any ideas on who/what is changing my privacy settings and how to prevent it from occuring again?

[dbartel]

I think that I have finally figured out what is happening.

When I create a new dataflow, the datasource credentials for that new dataflow default to private.  This is not an issue, except that all connections that are owned by me for that same datasource change as well.  So in other words, if I create a new dataflow, I have to remember to quickly change the privacy level after the initial save, otherwise my existing data flows privacy levels will be changed and cause excessive refresh times or complete refresh failures.  

This seems like a bug to me.  New dataflow creation should not affect already established dataflows and their privacy levels.

[v-henryk-mstf]

Hi @dbartel ,

See if the related blog post was helpful to you.

Privacy Levels for Cloud Data Sources | Microsoft Power BI Blog | Microsoft Power BI

Chris Webb's BI Blog: Power BI Data Privacy Levels And Cloud /Web-Based Data Sources Or Dataflows Ch...

If the problem is still not resolved, please provide detailed error information and let me know immediately. Looking forward to your reply.

Best Regards,
Henry

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

[dbartel]

Thank you for your response.  My problem is not setting the privacy levels, it is that after I set them they change on their own, usually to Private, which causes the query to fail.  It just happened again over the weekend.  2 of the data sources remained public and one changed to public causing the refresh to fail.  I switched the private back to public and will wait to see how long it stays as public.