Azure App Service TCP/IP Port Exhaustion
<p>I recently got a "recommendation" from Azure regarding reaching the upper limit for TCP/IP ports in my App Service. </p>

<blockquote>
  <p>TCP/IP ports near exhaustion Your app service plan containing app
  ****** is configured to use medium instances. The apps hosted in
  that App Service plan are using more than 90% of the 4096 available
  TCP/IP ports available per medium instance. You can upgrade the
  instance size to increase the outbound connection limit or configure
  connection pooling for more efficient use.</p>
</blockquote>

<p>Is there a difference in <strong>Limits for App Service Plans</strong> (scale up)? or can I <strong>Configure my App Service</strong> to use more ports? Or is there any <strong>other solution</strong> for this?</p>

<p>An obvious solution would be scaling out, but since CPU and Memory usage is low I would rather not use this option if not necessarily. </p>

<p>As background, the service is an API built with ASP.NET Core MVC using .Net 4.6.</p>