EasyMorph uses the standard Azure SDK under the hood. I'd assume that extended uploads may trigger some internal timeouts in it. Although, it's hard to say for sure.
If splitting the files worked, great!
I also thought about delegating the work to the EasyMorph Server and triggering it remotely. Do the upload to Azure not from your laptop, but from EasyMorph Server that is plugged into a fast stable internet. For instance, make a task on your EasyMorph Server in the office that takes the files from some file storage and uploads them to Azure (given that your office internet is fast). You can trigger the task remotely (e.g. when travelling) in many ways, for instance:
- Using Web Tasks
- Using webhooks
- By sending an email with a specific subject
- By making the task to periodically check the folder to which the files are uploaded
- By asking someone in the office to trigger the task manually
When such a task is set up, all you will need is to upload these files to that storage using any utility that works well over unstable and slow connections, and then trigger the Server task remotely - it will do the rest.
Although, I might be overengineering here.