Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
1 year ago
Solved

Power Automate button and embebed app issue button is not displayed

I am experiencing challenges with displaying a Power Automate button in Azure App Services. The button appears in Power BI Desktop and the web service but not in the app services. As a result, the end user cannot utilize the function I created when pressing the button. Does anyone have any suggestions on how to resolve this issue?

  • Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.

     

    Your issue is tied to embedding limitations, especially when using the App Owns Data model. This model lacks a user context, which is required for the Power Automate visual to render and function correctly. To resolve this, first test using the User Owns Data model instead. This approach retains the actual user's identity and typically allows the Power Automate button to work as expected in embedded reports.

     

    If switching the model isn’t feasible, open the browser’s developer console (F12) while viewing the embedded report in Azure App Services. Look for blocked requests to flow.microsoft.com or powerautomate.microsoft.com, CORS errors, or CSP violations. If any appear, update your Content Security Policy headers and iframe sandbox attributes to allow Microsoft scripts and popups.

     

    Also, confirm that the attached Power Automate flow is in the Default environment or one accessible to the embedding context. Go to the flow’s Run-only user’s settings and ensure the users or service principal are authorized to run it. If needed, move or reconfigure the flow accordingly. To isolate the issue further, try embedding the same report in a basic HTML page using the Power BI JavaScript SDK. If the button appears there but not in Azure App Services, it's a configuration issue within App Services likely CSP or rendering engine limitations.

     

    As a final workaround, use a regular button (in Power BI or your app) to trigger the same Power Automate flow via HTTP request. This avoids the visual altogether while keeping the functionality consistent in all environments.

     

    If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
    Thank you.

4 Replies

  • v-hashadapu's avatar
    v-hashadapu
    Icon for Community Support rankCommunity Support

    Hi Anonymous , Thank you for reaching out to the Microsoft Community Forum.

     

    Your issue is tied to embedding limitations, especially when using the App Owns Data model. This model lacks a user context, which is required for the Power Automate visual to render and function correctly. To resolve this, first test using the User Owns Data model instead. This approach retains the actual user's identity and typically allows the Power Automate button to work as expected in embedded reports.

     

    If switching the model isn’t feasible, open the browser’s developer console (F12) while viewing the embedded report in Azure App Services. Look for blocked requests to flow.microsoft.com or powerautomate.microsoft.com, CORS errors, or CSP violations. If any appear, update your Content Security Policy headers and iframe sandbox attributes to allow Microsoft scripts and popups.

     

    Also, confirm that the attached Power Automate flow is in the Default environment or one accessible to the embedding context. Go to the flow’s Run-only user’s settings and ensure the users or service principal are authorized to run it. If needed, move or reconfigure the flow accordingly. To isolate the issue further, try embedding the same report in a basic HTML page using the Power BI JavaScript SDK. If the button appears there but not in Azure App Services, it's a configuration issue within App Services likely CSP or rendering engine limitations.

     

    As a final workaround, use a regular button (in Power BI or your app) to trigger the same Power Automate flow via HTTP request. This avoids the visual altogether while keeping the functionality consistent in all environments.

     

    If this helped solve the issue, please consider marking it 'Accept as Solution' so others with similar queries may find it more easily. If not, please share the details, always happy to help.
    Thank you.

  • v-hashadapu's avatar
    v-hashadapu
    Icon for Community Support rankCommunity Support

    Hi Anonymous , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
    Thank you.

  • v-hashadapu's avatar
    v-hashadapu
    Icon for Community Support rankCommunity Support

    Hi @DPGM , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
    Thank you.

  • v-hashadapu's avatar
    v-hashadapu
    Icon for Community Support rankCommunity Support

    Hi @DPGM , Please let us know if your issue is solved. If it is, consider marking the answer that helped 'Accept as Solution', so others with similar queries can find it easily. If not, please share the details.
    Thank you.