You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally, the Power Automate cloud flow in the solution would not use hardcoded static text for the Azure Blob Storage name or endpoint. If it used an environment variable rather than hardcoded text, it would be more clear that it is a placeholder to be set by the person deploying the tool. Such a change should also be reflected in the setup instructions for the repo so that future users know to set that environment variable's value after importing the zipped solution.
Maybe consider also including some updates in the documentation for how to find and specify the blob storage by its endpoint (for the scenario when the Power Apps solution is running under a different subscription than the Azure Functions, etc.).
The text was updated successfully, but these errors were encountered:
Ideally, the Power Automate cloud flow in the solution would not use hardcoded static text for the Azure Blob Storage name or endpoint. If it used an environment variable rather than hardcoded text, it would be more clear that it is a placeholder to be set by the person deploying the tool. Such a change should also be reflected in the setup instructions for the repo so that future users know to set that environment variable's value after importing the zipped solution.
Maybe consider also including some updates in the documentation for how to find and specify the blob storage by its endpoint (for the scenario when the Power Apps solution is running under a different subscription than the Azure Functions, etc.).
The text was updated successfully, but these errors were encountered: