Skip to content

Commit f6a15ba

Browse files
committed
How it works
1 parent 4c5d598 commit f6a15ba

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

articles/app-service/overview-access-restrictions.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: App Service Access restrictions
3-
description: App Service Environment networking details
3+
description: This article provides an overview of the access restriction features in App Service
44
author: madsd
55
ms.topic: overview
66
ms.date: 08/15/2022
@@ -9,12 +9,21 @@ ms.author: madsd
99

1010
# Azure App Service access restrictions
1111

12+
Access restrictions in App Service is equivalent to a firewall allowing you to block and filter traffic. Access restrictions apply to **inbound** access only. Most App Service pricing tiers also have the ability to add private endpoints to the app, which is an additional entry point to the app. Access restrictions do not apply to traffic entering through a private endpoint. For all apps hosted on App Service, the default entry point is publicly available. The only exception is apps hosted in ILB App Service Environment where the default entry point is internal to the virtual network.
13+
1214
## How it works
1315

16+
When traffic reaches App Service, it will first evaluate if the traffic originates from a private endpoint or is coming through the default endpoint. If the traffic is sent through a private endpoint, it will be sent directly to the site without any restrictions. Restrictions to private endpoints are configured using network security groups.
17+
18+
If the traffic is sent through the default endpoint (often a public endpoint), the traffic is first evaluated at the site access level. Here you can either enable or disable access. If site access is enabled, the traffic will be evaluated at the app access level. For any app, you will have both the main site and the advanced tools site (also known as scm or kudu site). You have the option of configuring a set of access restriction rules for each site. You can also specify the behavior if no rules are matched. The following sections will go into details.
19+
1420
:::image type="content" source="media/overview-access-restrictions/access-restriction-diagram.png" alt-text="Diagram of access restrictions high-level flow":::
1521

1622
## App access
1723

24+
If the setting has never been configured, the default behavior is to enable access unless a private endpoint exists after which it will be disabled. You have the ability to explicitly configure this behavior.
25+
26+
1827
## Site access
1928

2029
## Advanced use cases

0 commit comments

Comments
 (0)