title: How Do I Configure API Management With Multiple Back Ends?
body: <p>I am hosting a service for clients where we have the same application deployed per client in Azure.</p>
  
  <p>It is essentially this per client:</p>
  
  <pre><code>Application Gateway -&gt;
  App Service Environment -&gt;
  API Management -&gt;
  VM with Application back end -&gt;
  Remote Azure SQl Data
  </code></pre>
  
  <p>The first 3 layers increase the costs quite significantly.</p>
  
  <p>Is it possible to configure it like this?</p>
  
  <pre><code>Application Gateway -&gt;
  App Service Environment -&gt;
  API Management -&gt;
      - Client 1 
          VM1 with Application back end -&gt;
          Remote Azure SQl Data1
      - Client 2 
          VM2 with Application back end -&gt;
          Remote Azure SQl Data2
      - Client 3 
          VM3 with Application back end -&gt;
          Remote Azure SQl Data3
  </code></pre>
  
  <p>i.e. the web layers route to the appropriate back end <em>somehow</em></p>
  
  <p>e.g. Maybe each client would access the web layer with a different URL.</p>
  
  <p><a href="http://client1.rest-application.azure.com" rel="nofollow noreferrer">http://client1.rest-application.azure.com</a></p>
  
  <p><a href="http://client2.rest-application.azure.com" rel="nofollow noreferrer">http://client2.rest-application.azure.com</a></p>
  
  <p>but they all go through the same application gateway.</p>