@Thea Lund Jørgensen , Thanks for posting this question. What App Service Plan (ASP) are you leveraging?
Firstly, just to highlight, Azure App Service represents a fleet of scale units. An app service always runs in an ASP.
1.You can configure the amount of time the platform will wait before it restarts your container. To do so, set the WEBSITES_CONTAINER_START_TIME_LIMIT
app setting to the value you want.
--The default value is 230 seconds, and the maximum value is 1800 seconds.
2.As a quick step to isolate the issue: Turn on Always On and test. (If you haven't done this already)
You may scale-up the App Service Plan and see if it helps. ( you may later scale-down post test, as required)
When Always On isn't turned on (default), the app is unloaded after 20 minutes without any incoming requests. The unloaded app can cause high latency for new requests because of its warm-up time. When Always On is turned on, the front-end load balancer sends a GET request to the application root every five minutes. The continuous ping prevents the app from being unloaded.
Additionally,
3.You may always leverage App Service diagnostics from Azure Portal> Navigate to your App Service app in the Azure Portal.
-In the left navigation, click on Diagnose and solve problems
- Review and run - “Availability and Performance” and - “Configuration and Management”
4.Enable and review logs to fetch more details about the issue.
Kindly let us know, I'll follow-up with you further.