Deployment pipeline - Deploy reports and dashboards for Contributor

[boris_juste]

In the Deployment Pipeline, allow "Deploy reports and dashboards" for Contributor to have same deployment right from Power BI Desktop and Deployment Pipeline.

[Craig_Hill1]

Agree, this is much needed, Contributors Can already Publish into workspaces, not having them in the process does not make much sense, since they can bypass the Deployment pipeline.

[mahesh_kommanur]

Agree, voted up. It's much needed, to support a secured workspaces & delegated devops process; We regulate the workspace admin role and all of our developers & change control owners are only granted Member or Contribute access. If a developer can publish an artifact to a workspace with contribute access, he should be able to deploy those via pipelines too.

[Chris_Greer1]

Agree, We have PHI data and require access controlled through AD groups, we have to restrict the use of Member role since it includes the ability to share. This idea would allow us to increase the use of pipelines within ours and I imagine other health care orgs

[cousind2]

Yeah, this would be really useful. Our use case:

We only allow things to be published to production once they've been through a gateway that checks for things like data quality, accuracy and accessibility, so only certain users have member permissions on the Production workspace. The current pipeline setup is inflexible as users with the ability to deploy to test can share the report too, short-cutting this process and creating risk.

Additionally, on first deployment you need to provide the connection settings for a new dataset in each pipeline stage, which makes the above process a bit janky. As a reviewer I may not have permissions to a data source, so I need to elevate someone to publish to production and setup the dataset connections, and then revoke that access. It's not a good CI/CD setup as-is. (though admittedly having a split pipeline for datasets and reports has largely fixed this for us in our biggest, more Enterprise scale deployments. No good for smaller setups tho!)

[Chris_Diekvoss]

Agree totally. A contributor already has the permission to publish directly I don't understand how using the pipeline is any more dangerous. The current need to be a member also open the risk of people being able to modify the security/permissions. At my org we are using Azure AD groups but a member can circumvent that.

[nishalit]

An update allowing contributors to deploy was released.