Forum Discussion
Helper IService account - license
As we dont want our reports to stop working everytime password expires or the owner of the report leaves the company we are considering to create a service account. But is it OK to do that as multiple users will signin with that service account according to the license model? Or what is the recommended practices for not having a constraint to a specific user with password resets etc?
The individual sign in is different from datasource access. So you should always have that running under a service account. The acces to reports is given based on User Groups/ Roles and the report runs on a seperate account. The user sign-in would be individual ID based and give him access to the reports only .The Data Source should always be hidden from the user and be running with confidential credentials of a service account.
4 Replies
- AbhiSSRS
Solution Sage
The individual sign in is different from datasource access. So you should always have that running under a service account. The acces to reports is given based on User Groups/ Roles and the report runs on a seperate account. The user sign-in would be individual ID based and give him access to the reports only .The Data Source should always be hidden from the user and be running with confidential credentials of a service account.
Hi! For data sources refreshes that accept Service Principal /Entra ID, you can use Workspace Identity. https://learn.microsoft.com/en-us/fabric/security/workspace-identity
Having a team sign in as the same user named Service Account is really not the best since it violates the license terms, and such "user's" password will still expire and will need to be reset, disabling the password reset / multi factor authentication creates security problems as well.
