Barker, Nick, To better assist you on this issue, kindly provide the following info:
Based on my understanding of your scenario, as I understand you have provisioned your webapp on Azure App Service. What specific timeout are you referring to? What is the exact scenario are you attempting to accomplish? Do you receive any specific error message?
- Always On: To prevent your web app from being idled out due to inactivity, you can enable “Always On.” Navigate to your app service in the Azure portal, go to the Configuration blade, and turn on “Always On.” Note that this feature requires at least the Basic SKU.
- SCM_COMMAND_IDLE_TIMEOUT: If you want to set a specific timeout value, you can configure the
SCM_COMMAND_IDLE_TIMEOUT
setting. This value determines how long the SCM process waits for an idle command before timing out. For example, you can set it to 3600 seconds (one hour) by adding this setting in your app’s configuration.
Additionally,
Azure Load Balancer has a default idle timeout setting of four minutes. This setting is generally a reasonable response time limit for a web request. so, App Service returns a timeout to the client if your application does not return a response within approximately 240 seconds (230 seconds on Windows app, 240 seconds on Linux app). If your web app requires background processing, we recommend using Azure WebJobs. The Azure web app can call WebJobs and be notified when background processing is finished. You can choose from multiple methods for using WebJobs, including queues and triggers.
Checkout this doc for more info: Application performance FAQs for Web Apps in Azure
Kindly let us know, I'll follow-up with you further.
If the answer helped (pointed, you in the right direction) > please click Accept Answer - it will benefit community members to find the answers quickly.