Idea: Currently, when Power BI Paginated Reports are uploaded or deployed through the Power BI REST API, the data source mapping is automatically assigned to a “Personal Cloud Connection”. In many enterprise deployment scenarios, this is not sufficient because reports need to use an already existing, centrally managed cloud connection, such as an existing SQL Server or Azure SQL connection. At the moment, the correct cloud connection can be selected manually in the Power BI Service after the report has been uploaded. However, there does not appear to be a supported REST API, PowerShell command, deployment pipeline option, or other automated mechanism to assign or update the cloud connection mapping for paginated reports after deployment. This creates a gap for organizations that need fully automated CI/CD deployment processes for paginated reports. Requested functionality: Please provide a supported mechanism to automate the assignment or reassignment of existing cloud connections for Power BI Paginated Reports. This could be implemented through one or more of the following options: A REST API endpoint to update the data source mapping or cloud connection of an uploaded paginated report Support for assigning an existing cloud connection during the paginated report upload process Support for this scenario in deployment pipelines PowerShell support for updating paginated report cloud connections Service principal support for managing paginated report connection mappings Business impact: Without this functionality, every deployment of a paginated report requires manual post-deployment configuration in the Power BI Service. This prevents fully automated deployments, increases operational effort, and introduces the risk of human error, especially in environments with multiple workspaces, stages, or reports. For organizations using DevOps, CI/CD pipelines, and controlled deployment processes, the ability to automate this step is important for governance, scalability, and reliability. Example scenario: A paginated report is uploaded to a Power BI workspace through the REST API. After upload, the report is automatically mapped to a “Personal Cloud Connection”. However, the report should instead use an existing shared cloud connection, for example an existing SQL database connection used by the organization. Today, this reassignment must be done manually in the Power BI Service. The requested improvement would allow this mapping to be configured automatically as part of the deployment process. Benefit: Adding this capability would enable fully automated and enterprise-ready deployment processes for Power BI Paginated Reports, reduce manual work, improve governance, and make paginated reports easier to manage in professional Fabric and Power BI environments.
... View more