The new Copilot-powered narrative visual in Power BI is a game-changer for delivering automated insights and enhancing storytelling within reports. However, it’s currently unsupported in embedded scenarios where the app owns the data - specifically when the report viewers are external users outside the host organization's tenant.
This limitation significantly impacts partners, SaaS providers, and ISVs who rely on Power BI Embedded to deliver rich, AI-powered analytics experiences to their customers. Enabling narrative visuals in app-owns-data setups would unlock tremendous value by bringing Copilot's summarization and insight-generation capabilities to a broader audience.
Please consider extending support to these scenarios to help us bring the full power of Copilot to all users, regardless of their tenant affiliation.
Thanks.
Yagiz
4 Comments
- Since evaluating each request takes a long time here, I have built my own Power BI Custom Visual that connects to Azure OpenAI for instant AI summaries/insights. I no longer require assistance.
otarbMicrosoft Employee
YagizOzd happy to share that Copilot narrative visual now supports the app‑owns‑data scenario https://community.fabric.microsoft.com/t5/Power-BI-Updates-Blog/Power-BI-May-2026-Feature-Summary/ba-p/5182174#_Toc230033627- Hello, thanks for the update. It worked for me for few days after your news, but afterwards I kept getting this "Authentication failed" error. Any idea how to overcome this? I don't think this is some session reset that should be doing on client side. Edit: Looks like I can't post screenshot as comment so let me describe: 1. Narrative visual says "Content unavailable". 2. Browser logs (F12) has "Network" tab as "error": { "code": "AI_AuthenticationFailed", "message": "Authentication failed for all authenticators" } } 3. Browser logs (F12) has "Console" tab as reportembed.externals.bundle.min.6bf9b5df7575baacb716.js:312 POST https://wabi-west-us-d-primary-redirect.analysis.windows.net/explore/nl2nl/completions 401 (Unauthorized)
- otarbHow are your API permissions configured? Please make sure your service principal has MLModel.Execute.All or Item.Execute.All in addition to the item-specific scopes (Report.Read.All or Report.ReadWrite.All). If you're still hitting the issue, feel free to email me at [email protected] and I can help investigate further.
