Downstream 403 Error For 1 Staff Member

[Mat42]

I'm running out of ideas.

We have one staff member who is experiencing issues with accessing dataflows. Everyone else can access things fine, but he is getting Downstream 403 errors for a bunch of reports. The reports are all in different workspaces but they do have connections to the same dataflows in common. Everyone else can access the dataflows fine.

Refreshing the reports produces this error:

And connecting to the dataflows fresh elicits this error:

We've worked out that they're using the 'Dataflows' connector, which seems to be causing the error and when they switch to the 'Power BI dataflows (Legacy)' connector it seems to work fine, but this isn't causing a problem for anyone else doing the same thing.

Nothing has changed at their end; no new log in credentials, no new laptop, no password changes. The only thing that was slightly different was that someone else downloaded the report, made cosmetic adjustments to the report (not the data) and republished it. But the person having problems was the original creator and owns the semantic model (we've tried changing oweners to see if that changes anything).

This problem seems to be happening both in the online service and on desktop so I'm thinking that there's a credentials issue in there somewhere, I just don't know where.

We've come to the conclusion that they'll probably need to swap the connector from Dataflows to the legacy connector, but it's going to be an awkward process. Besides, I'd like to know what's going on.

Can anyone offer any insight as to what might have caused this and any possible routes to fixing it?

[Mat42 · Accepted solution]

Totally forgot I asked this question due to many many other issues arising.

We got things running by swapping out the connector and never did work out why that connector causes a problem. But, I have discovered that it seems to be causing people a problem all over our tenant, so we're investigating that.

[Akash_Varuna]

Hi @Mat42 Since you mentioned it is working fine with legacy one it might be because of the cached credentials maybe try clearing the credentials and re connecting and try taking the ownerhsip of the workspace fully maybe it might be because of the credentials then republish the report and dataflow