<p>Azure Application Gateway allows you to provide one public IP for those App Services.</p>

<p>You have to make the following steps:</p>

<ol>
<li>Provision Application Gateway</li>
<li>Add listeners with host name for eachof the App Services</li>
<li>Add backends for each of the App Service</li>
<li>Create HTTP Settings with <em>Override with new host name</em> and <em>Pick host name from backend target</em> options</li>
<li>Add rules to connect listeners corresponding to backends</li>
</ol>

<p>At the end customer has to white-list one public IP assigned to Application Gateway and create DNS entries to point all App Services addresses to one public IP. </p>

<p>Materials:</p>

<ul>
<li><a href="https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-web-app-overview" rel="nofollow noreferrer">Application Gateway support for multi-tenant back ends such as App
service</a></li>
<li><a href="https://docs.microsoft.com/en-us/azure/application-gateway/how-application-gateway-works" rel="nofollow noreferrer">How an application gateway works</a></li>
</ul>

CC BY-SA 4.0
2020-04-11T15:24:59.767Z
2020-04-11T15:24:59.767Z
Paweł Tajs
<p>I have 3 components of my architecture running in 3 separate Azure App Services. Each app service has 4 outbound IPs. So whenever I have to deploy my app onto the client's premise, I have to whitelist 12-16 IPs on their on-premise Firewall. </p>

<p>Is there any way I can deploy a NAT which uses only 1 public IP and I can provide just 1 IP to the client?</p>

<p>If I manage to make this architecture work then how would I modify my API calls to these services, since at the moment I'm using their 1 public IP to access their individual service, with just 1 IP how will I distinguish API calls made to different app service.</p>

<azure><networking>
Mapping Outbound IPs to 1 IP in Azure App Services
Vedant Kashyap
# Mapping Outbound IPs to 1 IP in Azure App Services

(Asked by: username_0 on 2020-03-02)

I have 3 components of my architecture running in 3 separate Azure App Services. Each app service has 4 outbound IPs. So whenever I have to deploy my app onto the client's premise, I have to whitelist 12-16 IPs on their on-premise Firewall.

Is there any way I can deploy a NAT which uses only 1 public IP and I can provide just 1 IP to the client?

If I manage to make this architecture work then how would I modify my API calls to these services, since at the moment I'm using their 1 public IP to access their individual service, with just 1 IP how will I distinguish API calls made to different app service.

**Tags:** azure, networking


---

## 1 answers

### Answer by username_1 on 2020-04-11. Score: 1

Azure Application Gateway allows you to provide one public IP for those App Services.

You have to make the following steps:

1. Provision Application Gateway
2. Add listeners with host name for eachof the App Services
3. Add backends for each of the App Service
4. Create HTTP Settings with *Override with new host name* and *Pick host name from backend target* options
5. Add rules to connect listeners corresponding to backends

At the end customer has to white-list one public IP assigned to Application Gateway and create DNS entries to point all App Services addresses to one public IP.

Materials:

* [Application Gateway support for multi-tenant back ends such as App
  service](https://docs.microsoft.com/en-us/azure/application-gateway/application-gateway-web-app-overview)
* [How an application gateway works](https://docs.microsoft.com/en-us/azure/application-gateway/how-application-gateway-works)


---

