Hi @Rosy081 ,
When integrating a Power BI workspace with an Azure DevOps Git repository for version control, privacy concerns primarily revolve around data security, metadata exposure, and access control. While the integration does not transfer actual report data, it does store metadata, dataset structures, report configurations, and model relationships, which could reveal business logic and sensitive insights if accessed by unauthorized users. Ensuring role-based access control (RBAC), multi-factor authentication (MFA), and least privilege access policies is crucial to prevent unauthorized modifications or data leaks.
Additionally, if PBIX files are included in the repository and contain embedded data, there is a potential risk of exposure, making it essential to restrict access and use private repositories. Since the integration does not automatically transfer personally identifiable information (PII), any PII stored within Power BI model definitions, embedded queries, or report descriptions should be carefully reviewed. To maintain compliance with GDPR, HIPAA, or internal governance policies, organizations should assess what information is included in version-controlled files and ensure encryption at rest and in transit for secure storage and data transfer. Properly configuring repository security, monitoring audit logs, and implementing best practices in DevOps integration will help mitigate privacy risks while leveraging version control effectively.
Did it work? ✔ Give a Kudo • Mark as Solution – help others too!
