Forum Discussion

webartoli's avatar
webartoli
Regular Visitor
8 months ago

Embedding and Copilot

I a report that i can embed via iframe with copilot. (so all requriments are met). Where i can find any documentation about customization. In playground I'm unable to enable copilot.   Does some...
Need Help
  • webartoli's avatar
    webartoli
    Regular Visitor
    8 months ago

    Thanks for the response.
    I have seend this page multiple times, and I'm able to use Copilot embedding the report via link or iframe, I'm using a piad capacity with MSDN credits.

    The question is: can I hide filter sidebar, or pages selector ?
    O normally use playground with options (in an user-owns-data context) that the documentation is mentioning but there are no docs and no option in playground to show copilot panel.

    I also wonder to use app-owns-data but seems not supperted yet (even if not explicitly stated in the documentation)

    • tayloramy's avatar
      tayloramy
      Super User
      8 months ago

      Hi webartoli, 

       

      I'm not positive, but I don't think that the pages and filter slidebars can be hidden. 

       

      I'm also pretty sure that user-owns-data is required. 

       

      As far as I can tell, checking that button when creating the embed code should be all you need to do as long as you are on a paid capacity: 
      Now available: two new Copilot experiences | Microsoft Power BI Blog | Microsoft Power BI

       

      If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

      • webartoli's avatar
        webartoli
        Regular Visitor
        8 months ago

        For sure pages and sidebars can be hidden, we have already several specific integration in production.
        Most of the features that can be triggered programmatically, are available in playground dev sandbox and can be tested live.

        There are a lot of configuration that can be performed editing settings/config (docs here) but copilot is not mentioned in any case. Seems a lack of documentation/feature.

        So the problem is: we already have a strong integration in place with a UX very well integrated.
        Users want copilot (of course) and we want to give it but it seems a huge step back in terms of design.