Forum Discussion
PowerApps / Automate in embedded environment
Based on your description, it appears that you are trying to enable clients to trigger a flow in an embedded environment, but are facing some limitations with Power Automate and PowerApps.
You are correct that Power Automate is not currently supported in an embedded (app owns data) environment. However, there may be alternative solutions to achieve your objective, such as implementing a custom API endpoint that your clients can call to trigger the flow.
Regarding PowerApps, it is true that users need to authenticate using their own Microsoft account to be able to use the app. However, you may be able to create a custom connector in PowerApps that uses a service account for authentication, allowing clients to trigger the flow without the need for their own Microsoft account.
Another potential solution could be to use Azure Logic Apps, which supports triggering flows through HTTP requests. This could allow you to create a custom API endpoint that clients can call to trigger the flow, without the need for Power Automate or PowerApps.
In summary, while there may be limitations with Power Automate and PowerApps in an embedded environment, there are alternative solutions such as creating a custom API endpoint or using Azure Logic Apps that could help you achieve your objective.
Based on your description, it appears that you are trying to enable clients to trigger a flow in an embedded environment, but are facing some limitations with Power Automate and PowerApps.
You are correct that Power Automate is not currently supported in an embedded (app owns data) environment. However, there may be alternative solutions to achieve your objective, such as implementing a custom API endpoint that your clients can call to trigger the flow.
Regarding PowerApps, it is true that users need to authenticate using their own Microsoft account to be able to use the app. However, you may be able to create a custom connector in PowerApps that uses a service account for authentication, allowing clients to trigger the flow without the need for their own Microsoft account.
Another potential solution could be to use Azure Logic Apps, which supports triggering flows through HTTP requests. This could allow you to create a custom API endpoint that clients can call to trigger the flow, without the need for Power Automate or PowerApps.
In summary, while there may be limitations with Power Automate and PowerApps in an embedded environment, there are alternative solutions such as creating a custom API endpoint or using Azure Logic Apps that could help you achieve your objective.
Hi Adam, thanks so much for taking the time to write this, lots of helpful ideas. Nate