Timeout request! Yeah, I know you have addressed this issue at least once! When developing your endpoints and it takes a considerable amount of time, you need to consider if you require a more robust endpoint implementation. For this batch process, you can evaluate using Azure batch accounts. You can create different lightweight VMs and, through Azure Factory and Blob Storage, run your .NET codes to populate or update your DB. You can use this tool from Data Factory V1, which means that V2 is even easier to start with the running pipeline's implementation. What this tool does for you is zip your main DLLs and store them in a specific container of your storage account. If you want to redeploy your solution, you only need to replace that zip. Review collected by and hosted on G2.com.

If you want to do a service integration where this on-premise needs to add your IP to a whitelist, you will need to do a complicated VPN configuration. Why? The VM is running behind and works only in the private Azure network, and if you try to get this public IP, you will have different IP pools each specific time. Review collected by and hosted on G2.com.