Azure App Service Static IP Restrictions

IP Restrictions allow you to define a priority ordered allow/deny list of IP addresses that are allowed to access your app. The allow list can include IPv4 and IPv6 addresses. When there are one or more entries, there is then an implicit deny all that exists at the end of the list.

The IP Restrictions capability works with all App Service hosted work loads, which include; web apps, api apps, linux apps, linux container apps, and Functions.

When a request is made to your app, the FROM IP address is evaluated against the IP Restrictions list. If the address is not allowed access based on the rules in the list, the service replies with an HTTP 403 status code.

The IP Restrictions capability is implemented in the App Service front-end roles, which are upstream of the worker hosts where your code runs. IP Restrictions are therefor effectively network ACLs.

IP restrictions flow

For a time, the IP Restrictions capability in the portal was a layer on top of the ipSecurity capability in IIS. The current IP Restrictions capability is different. You can still configure ipSecurity within your application web.config but the front-end based IP Restrictions rules will be applied before any traffic reaches IIS.

Adding and editing IP Restriction rules in the portal

To add an IP restriction rule to your app, use the menu to open Network>IP Restrictions and click on Configure IP Restrictions

App Service networking options

From the IP Restrictions UI, you can review the list of IP restriction rules defined for your app.

list IP restrictions

If your rules were configured as in this image, then your app would only accept traffic from and would be denied from any other IP address.

You can click on [+] Add to add a new IP restriction rule. Once you add a rule, it will become effective immediately. Rules are enforced in priority order starting from the lowest number and going up. There is an implicit deny all that is in effect once you add even a single rule.

add an IP restriction rule

IP Address notation must be specified in CIDR notation for both IPv4 and IPv6 addresses. To specify an exact address, you can use something like where the first four octets represent your IP address and /32 is the mask. The IPv4 CIDR notation for all addresses is To learn more about CIDR notation, you can read Classless Inter-Domain Routing.

You can click on any row to edit an existing IP restriction rule. Edits are effective immediately including changes in priority ordering.

edit an IP restriction rule

To delete a rule, click the ... on your rule and then click remove.

delete IP restriction rule

Programmatic manipulation of IP restriction rules

There currently is no CLI or PowerShell for the new IP Restrictions capability but the values can be set manually with a PUT operation on the app configuration in Resource Manager. As an example, you can use and edit the ipSecurityRestrictions block to add the required JSON.

The location for this information in Resource Manager is: ID/resourceGroups/resource groups/providers/Microsoft.Web/sites/web app name/config/web?api-version=2018-02-01

The JSON syntax for the earlier example is:

"ipSecurityRestrictions": [
    "ipAddress": "",
    "action": "Allow",
    "tag": "Default",
    "priority": 100,
    "name": "allowed access"