I am building a PowerApp that uses and Azure Flow to upload a picture to a specific storage account. It does not seem possible to dynamiclly pick a specific storage account, instead you have to configure the connection while building the flow, then you can only pass the blob, the file name and the subfolder and not the storage account name and key. I need to pass all the parameters at the same time, using conditions to select from a list on connections does not seem to be an option either.
I need the paramters from step 2 at this link to be paired with the parameters in step 5 of this link:
I will have 110 storage accounts since i have to bill my partners monthly for the storage they use and need to seperate these files but storage account when i upload the images.
Any other ideas on how to do this or can there be an override when calling blob functions to pass the storage account informaiton in line from the calling app which has all of this data?
Could you please share a screenshot of your flow's configuration?
Do you want to pick a specific storage account dynamically and then create a connection to Azure Blob Storage connector?
Do you want to obtain account name and access key through triggers/actions of Azure Blob Storage?
There is no way to pick specific storage account dynamically and then create a connection to Azure Blob Storage connector within Microsoft Flow currently. If you would like this feature to be added in Microsoft Flow, please submit an idea to Flow Ideas Forum:
In addition, I afraid that there is no way to obtain account name and access key of a storage account through triggers/actions of Azure Blob Storage within Microsoft Flow.
Kris,Thanks for you response. I would prefer not to "create a storage connector" before i need to use it, this would make onboarding new users and new businesses much easier for this project - it would allow me to just create the business and user (o365 users) entries in my databases, then after i created the storage account in Azure (seperate for billing purposes), then i could just add the account name and key to the database for dynamic consumption. Here is the basic flow, pretty simple stuff:
And here is where i loop through my offline photo collection to upload the images to the correct storage locations:
Based on what you are saying, which i figured already - there is no way for me to make this happen right now. So i will have to store everything in one storage account until there is a solution. And yes i will add this to the ideas site.
Thanks in adavance for any thoughts.
Interesting addition to this issue; When you actually push this app out to non-admins, as part of the first logon, you have to sign in to and/or accept the connections to Office365 users, Azure AD, SQL Azure and Azure Blob storage - this all really kills the end user experience of launching a PowerApp to users - not to mention all of the sample apps that i can;t get rid of.
Anyway, my point is, that when a non-admin end user is logging on for the fist time, they can change the blob storage account details and it will disregard the ones that you have specified in Azure Flow. WAIT, WHAT? Thats right, the user can decide to connect to a different database or a different Azure storage account.
In PowerApps, we need a way at the app level, to lock this down! and basiclaly say that the end users have to use the connections that are built in and deployed with the app. Kind of line the 'Execute As' functionality in SQL Server, i should be able to say, that the users of this app can execute the Flow as me (or some other desinated user) when it is being used in the context of a deployed application.
Check out the new Process Advisor community forum board!
Check out new user group experience and if you are a leader please create your group
Participate in the Power Virtual Agents Community Challenge
Power Platform release plan for the 2021 release wave 2 describes all new features releasing from October 2021 through March 2022.
Dont miss our very own April Dunnam’s The Developer Guide to the Galaxy! Find out what the Power Platform has to offer for the traditional developer.