Forum Discussion
Copilot in embedded Power BI reports via iframe
Hi nick_leshkevich,
Thank you for reaching out to Microsoft Fabric Community.
Your approach is correct to validate the behaviour before enabling copilot in production.
- Copilot for embedded reports is currently supported only in User Owns Data (embed for your organization) scenarios. If your application uses the App Owns Data embedding model like for example using a service principal or master user, copilot in embedded reports is currently not supported.
- If you are using user owns data, copilot respects the signed in user's permissions, including RLS. Using a dedicated demo workspace with test users and RLS configured for separate customer data is the recommended way to verify that each user can access only their own data before rolling it out to production.
Thanks and regards,
Anjan Kumar Chippa
Hi nick_leshkevich,
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution I have provided for the issue worked? or let us know if you need any further assistance.
Thanks and regards,
Anjan Kumar Chippa
Your test plan looks like the right approach. I would start with a dedicated workspace/capacity, limited users, and sample data with RLS enabled. Test with multiple demo accounts and include negative scenarios (for example, asking Copilot about another customer’s data) to confirm isolation.
Also review tenant and workspace Copilot settings carefully, because enabling tenant-level features can affect availability beyond your pilot scope. Validate permissions, sensitivity labels, audit logs, and semantic model security before moving to production.
A controlled pilot is the safest way to confirm Copilot behavior with embedded reports and customer-facing data.