Development (Version Control, Solution, Source, Publish) Governance Framework

Hi icassiem ,

Thanks for the added context. Since you only have Power BI admin permissions and no access to Azure or Fabric workspaces, the approach you outlined is correct. The two practical controls available to you right now are:

1. Using a shared folder (SharePoint or OneDrive) as the expected location for PBIX source files before publishing.

2. Extracting the Power BI Activity Log using PowerShell to build your own audit report that shows report usage and operations.

You can use the following cmdlet to extract activity logs if your account has the necessary admin rights:

PowerShell reference:
Get-PowerBIActivityEvent (MicrosoftPowerBIMgmt.Admin) | Microsoft Learn

API reference (alternative):
Admin - Get Activity Events - REST API (Power BI Power BI REST APIs) | Microsoft Learn

These logs cover usage, view activity, and some sharing/export events. Forwarded URLs or “destination” behavior isn’t tracked, but you will get visibility into which reports are being accessed and how often.

At this stage, outside of the folder structure and audit reporting, there aren’t additional enforcement controls available at the Power BI admin level. If requirements change or your team gains access to Azure Log Analytics or the broader Fabric platform, more capabilities become available for governance and monitoring.

Hope this helps. Please reach out for further assistance.

Thank you.