We have published several company core reports/ datasets which were uploaded initially by accounts/ collegues who are leaving the company. It seems that after disabling the MSAD account or after withdrawing their O365 PBI license the datasets are not refreshed again and other end users run into errors while opening the particular reports. Why is this and how can we prevent this? (Can it only be done with a new, never to be deprovioned account?)
Hi @Seth_C_Bauer, user was owner of a workspace. User published the report. Default refresh was set up (nothing explicitly used). Useraccount was deprovisioned and Power BI licence was withdrawn. Other users opens reportd and get error: "This report couldn't access the data source. Contact [firstname], the author, to have it fixed. Email [firstname]"
@detlev This sounds like expected behaviour. Any reports that are relevant to a wider audience should be published to a group workspace so that others have access to the reports. Secondarily, the reports should not be using a personal gateway.
The only recourse here would be to activate the user that left (change the password), re-provision the Power BI license and move the reports he/she created to another workspace.
Or. If you have access to the PBIX, you could re-deploy, but that seems unlikely that you have that.
hi @Seth_C_Bauer The reports were indeed published to a 'company used' group workspace. (reports are shared via dashboards on this workspace). So Workspace is owner of the dataset.
Others have access to the reports via shared dashboards. Others have access to the data on the reports through a enterprice gateway to on premise SSAS models.
I miss the need of a publishers credentials in this chain of disclosing data.
gateway datasource credentials initalialy connect to SSAS on prem.
UPN of powerBI user is used as effective username to authenticate on and authorize in SSAS.
In this conecpt for me there is no role for the publishers credentials. But still it breaks the chain when the initial publisher is deprovisioned.
@detlevmake sure that your gateway connection to your SSAS is not using an employee to connect to your tabular instance. This might be the issue on the refresh.
@detlev Your final description is what you should have started with. It sounded like everything was in this persons individual workspace and tied to a personal gateway.
Since we've made it around to this point, I'll agree with @richardlhughes, you need to make sure the user isn't the credential used on the datasources.
Another thing to check... which i think I ran into is if the initial user set up the refresh on the datasource itself then you might need to update the refresh schedule. For some reason I recall that a user is stored on that bit.
Hi @richardlhughes We have never used employee credentials in a gateway datasource. We use serviceaccounts with never expiring credentials.
Hi @Seth_C_Bauer, thanks again for taking the time to uderstand and asnwer me. Highly appreciated!
which final description are you refering to? Since I only describe the situation as it is (and was before).
We do not use (and have not used) personal workspaces, only company wide one(s) with hundreds of reports.
Personal gateways are never used too, only enterprice ones.
Credentials on datasources (SSAS tabular) in gateways are setup with serviceaccounts.
The last part of your reply exactly points to my issue.
But it even amazes me more. Why would it store credentials in that bit???? I doesn't make sence to me.