User1068175894 posted
If you can parse the file inmediatelly to store it in table storage you may as well store it directly in sql server so I wouldnt use table storage if sql server is your final destination
If you want to dissociate the process of uploading the file with the process that parse it and store it, either to handle a bigger load or for audit purpose (keeping a copy of everything that was uploaded, keep track of files that errored out for retry,
etc), in this case you upload the files to blob storage.
You could go serverless and create an Azure Function with a BlobTrigger that gets executed when a new file gets into the blob
----------------------------
Please remember to click "Mark as Answer" the responses that resolved your issue.