Join us for an expert-led overview of the tools and concepts you'll need to pass exam PL-300. The first session starts on June 11th. See you there!
Get registeredPower BI is turning 10! Let’s celebrate together with dataviz contests, interactive sessions, and giveaways. Register now.
When calling
Source = PowerBI.Dataflows(null)
You get back a list of all dataflows you have access to in your default/primary tenant.
Is it possible to connect to dataflows you have access to outside of your default tenant? I've tried tinkering around with query to try to provide a tenant id similar to how you append ctid= to the URL to access a workspace in a guest tenant. But haven't succeeded yet.
@Pascal_KTeam
Anyone found a solution to this?
I mean I can explore an entire workspace in an external org using Azure B2B Guest accounts. I can even create a dataflow in the external org's workspace. But somehow it still seems impossible to connect to it using Power BI Desktop?
Also funny: I can create a dataflow in an external workspace, but even having the admin role in the workspace I can't manage the dataflow (settings, refresh etc.).
Any other consultants facing the same issues?
You can connect to external org dataflow from Power BI desktop. Below are the instructions
When you get the following screen, click on "Sign in options"
On the next screen, select "Sign in to an organisation"
Enter the domain of the organisation on the next screen i.e. "microsoft.com" or similar
Then select your account or enter your account details( i.e. the user name and password from your own tenant)
This should work
Hi @Anonymous ,
Please refer to the topic below.
https://stackoverflow.com/questions/40442647/share-power-bi-datasets-with-users-outside-organisation.
Best Regards,
Jay
Community Support Team _ Jay Wang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
I appreciate the help @GilbertQ!
To be clear, everything is contained within a single tenant, it's just not my primary tenant. A workspace has been configured within a client's tenant, and they've made the appropriate AD configuration changes to allow me, as an AAD B2B guest, to edit and manage content within that workspace.
This page mentions a limitation even with edit and manage content permissions is that you can't connect to a dataset in the service from PBI Desktop. That's been easy enough to work around, as OneDrive refresh seems to work normally and has allowed me to edit the dataset as I've needed, and you can connect secondary reports to the dataset from within the Service UI.
But I'm stuck on dataflows. I tried to refactor some of the heavier PowerQueries into dataflows, and creating the dataflows didn't present any issues. But there doesn't appear to be any way to actually use the dataflows I created. The Desktop application doesn't see them (presumably for the same reason it can't see guest tenant datasets), and I can't find anywhere in the Service UI to allow me to establish a connection either.
So I'm not sure if I'm overlooking something, or if the limitations of Azure B2B really do create a scenario where I'm able to create, edit, refresh, and maintain a resource (dataflows) while simultaneously having zero ability to actually consume it.
It is frustrating as this seems to be the only reason left which requires a tenant login. Azure B2B is brilliant from a security perspective and now that the Tenant Admin allows for Guest Users to be almost a 1st class citizen if the tenant wishes it's great.
Surely the easiest thing would be to use PowerBI.Dataflows([ctid]) to give tenant context in the same way as it is used now for accessing a client's Power BI envrironment as a Guest.
I'm now also stuck on this (again). Last time the client just created a user but I was hoping that this would be possible with a guest user by now.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
53 | |
34 | |
27 | |
26 | |
26 |
User | Count |
---|---|
62 | |
49 | |
30 | |
24 | |
23 |