@Pamela Reynolds Thanks for reaching here!
So, to add further for solving a SNAT port exhaustion issue for App Service, you can follow the general guidance in the Problem Solving section of Outbound connections in Azure, which applies to App Service web applications. The guidance includes:
- Reusing connections in the application
- Using connection pooling in the application
- Using less aggressive retry logic in the application
- Using keepalives to reset the outbound idle timeout
In addition, you can also try these App Service-specific solutions:
- Make sure the backend services can respond quickly
- Scale out the App Service plan to more instances
- Use App Service Environment, which has more SNAT ports for each worker instance, due to its smaller instance pool size
A load test should simulate real world data at a steady pace.
Suggest you refer below detailed blog links would be helpful-
- https://4lowtherabbit.github.io/blogs/2019/10/SNAT/
- Azure App Services: Efficient Management of SNAT Connections
Let us know if further query or issue remains.