Are there alternative approaches for automated report deployment and workspace integration?

[yazdanb]

I’m trying to automate a process where we maintain a “base” set of reports in one branch/workspace, and then deliver firm-specific workspaces that include the base reports plus a few custom versions for each firm. The repo is in Azure DevOps

I’ve tested two approaches so far:

1. Azure DevOps pipeline + Git integration – ran into access/approval issues since my company tightly controls pipeline permissions.

2. Fabric REST APIs (Git integration) – ran into tenant-level restrictions where service principals aren’t currently allowed to use Git APIs.

Both methods technically work in proof-of-concept but I can’t get them approved or enabled in our tenant, so I’m blocked from full automation. Has anyone solved a similar problem (scaling report distribution across multiple firm/client workspaces) in a simpler or alternative way? Are there other approaches that might avoid these tenant-level Git restrictions?

[AmiraBedh · Accepted solution]

Hello !

Thank you for posting on Microsoft Fabric community.

You can store your pbix files in SharePoint or OneDrive and connect each client workspace via get from OneDrive/SharePoint with the optionKeep data up to date. When you overwrite the pbixin the folder, the service auto updates the item in the workspace (about hourly). 

https://learn.microsoft.com/en-us/power-bi/connect-data/refresh-desktop-file-onedrive

You can also use Fabric or PBI deployment pipelines without enabling git since parameters and datasource rules let you swap connections per stage and you can promote manually or via REST with a delegated user.

https://learn.microsoft.com/en-us/fabric/cicd/deployment-pipelines/create-rules