SAS URI Input Field to connect to a blob api for azure storage
For security reasons. If we want to give access to a third party on a particular container only for them to archive their messages, we wouldn’t want to give them access to the whole storage account which might be having other important transactional tables/containers/files/queues.
E.g. If I want to give them access to inputarchivecontainer and outputarchivecontainer, I will share those 2 URLs with third party. They don’t need to know (read/write/anything) about the other containers/tables in that storage where we are keeping our sensitive information
It should be made a part of the 10-12 blob storage actions design because we have them in place already for ready use.
Currently, HTTP Post can be used as a workaround, but with HTTP, POST request can throw a timeout/internal server error. If we have the above option to connect to a connector api beforehand thru 2 input field – Connection Name, SAS Uri - then we just have to select the API like we do currently (by filling 3 input fields)
Mikael Sand commented
The same goes for Azure File Storage. Tired of using Azure Functions every time I need to access external (SAS-auth) Azure File Storage.