Forum Discussion
How to add data ai agent into Published App?
Hello,
Is there any way to add an AI data agent to a published app?
I have published data ai agent and trying to add a new item:
Best,
Jacek
I
Hi jaryszek ,
Thank you for confirming. Since the link is not working outside the App either, this confirms the issue is not related to the App configuration or republishing, but rather to the agent setup or tenant configuration. I recommend first verifying that the agent is fully published and not in draft, and that you are copying the latest URL directly after publishing. Next, ensure the workspace hosting the agent is accessible and properly assigned to the required capacity, and that there are no tenant level restrictions in the Admin Portal under Tenant Settings limiting AI, Copilot, or agent access to specific security groups. Even when testing as a Tenant Admin, feature level restrictions can still apply. Additionally, try opening the link in an InPrivate or Incognito browser session to rule out token or caching issues. If the problem continues, please share the exact error message shown when accessing the link, as that will help determine whether this is a permission scope issue, environment configuration problem, or a service limitation.
12 Replies
Hi jaryszek ,
Thanks for reaching out to Community Forum.
Currently, you cannot add a Data AI Agent directly as an item in a Published Power BI App / Fabric App. Data AI Agents are workspace level artifacts, and only certain content types like reports, dashboards, and semantic models are supported in Apps. For this reason, the agent won’t appear in the Add item list when setting up the App. To work around this, you can give users Viewer or higher access to the workspace so they can access the Data AI Agent directly.
Alternatively, you can create a deep link to the agent and include it in a report within the App, such as through a button or text box, so users can navigate to the agent from the App. If you want to enable conversational analytics within the App, you might consider enabling Copilot on the semantic model, which offers a similar Q&A experience in reports.
This is a current product limitation, not a configuration issue, and future updates may allow native support for Data AI Agents in Apps.
Refer these Microsoft Documentations -
https://learn.microsoft.com/en-us/fabric/data-science/data-agent-sharing
https://learn.microsoft.com/en-us/fabric/data-science/data-agent-microsoft-copilot-studio
https://learn.microsoft.com/en-us/fabric/data-science/concept-data-agent
https://learn.microsoft.com/en-us/power-bi/consumer/end-user-apps
https://learn.microsoft.com/en-us/power-bi/collaborate-share/service-create-distribute-apps
Thank you .Ok so I put Data AI Agent with deep link into my app and got:
What I am doing wrong. what is missing?
So after publishin data agent and creating the new app I just add a link from published data ai agent.
Best,
Jacek
Hi jaryszek ,
According to Microsoft documentation and community guidance, Fabric Data AI Agents, also called AI Skills, are workspace level artifacts and cannot be embedded directly inside a published Power BI or Fabric App as native app content. Apps currently support items like reports, dashboards, semantic models, and paginated reports, but Data AI Agents are not yet a supported content type. Because of this limitation, when you try to add a deep link in a way that makes the app render the agent inline, it can result in a broken or garbled page. The App simply is not designed to host or display the agent interface within its layout.
The supported approach is to first publish the Data AI Agent in the workspace and then add it to the App as a navigation link rather than embedding it. After publishing the agent and making sure it is shared with the right users, open the App in edit mode, add a link in the navigation menu, and paste the direct URL of the published Data AI Agent. Once you republish the App, users can click that link and access the full agent experience separately. It is also important to ensure users have the proper permissions to the workspace and the agent, otherwise they may see access errors. For now, this link based method is the recommended and supported workaround until native App integration for Data AI Agents becomes available.
Hi jaryszek,
Based on what you've confirmed so far, the setup should function as expected if the agent is published, the navigation link in the App is set up correctly, and the App has been republished. Since those steps are complete, the issue is likely related to permission scope or tenant-level configuration affecting agent access from the App. To help identify the cause, could you let me know if the link works when opened outside the App, if the issue affects all users or just some, and if you're testing with a user who only has App access or direct workspace access? This will help determine if the problem is related to access or the environment.
Thank you.
Hello,
thanks.
1. Unfortunately, the link does not work outiside app also.2. I am testing with the tenant admin user.
Best,
JacekHi jaryszek ,
Thank you for confirming. Since the link is not working outside the App either, this confirms the issue is not related to the App configuration or republishing, but rather to the agent setup or tenant configuration. I recommend first verifying that the agent is fully published and not in draft, and that you are copying the latest URL directly after publishing. Next, ensure the workspace hosting the agent is accessible and properly assigned to the required capacity, and that there are no tenant level restrictions in the Admin Portal under Tenant Settings limiting AI, Copilot, or agent access to specific security groups. Even when testing as a Tenant Admin, feature level restrictions can still apply. Additionally, try opening the link in an InPrivate or Incognito browser session to rule out token or caching issues. If the problem continues, please share the exact error message shown when accessing the link, as that will help determine whether this is a permission scope issue, environment configuration problem, or a service limitation.
