You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/app-service/environment/ase-multi-tenant-comparison.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,16 +52,16 @@ Both App Service Environment v3 and the public multitenant offering run on [Virt
52
52
53
53
|Feature |App Service Environment v3 |App Service public multitenant |
54
54
|---------|---------|---------|
55
-
|Virtual network integration|Yes, App Service Environment v3 is deployed into a subnet in your virtual network by default |Supported, [must be explicitly enabled](../../app-service/networking-features.md#virtual-network-integration)|
55
+
|Virtual network integration|Yes, App Service Environment v3 is deployed into a subnet in your virtual network by default |Supported, [must be explicitly enabled](../../app-service/networking-features.md)|
56
56
|Private endpoint support|Yes, [must be explicitly enabled on the App Service Environment](networking.md#private-endpoint)|Yes, [must be explicitly enabled](../../app-service/networking-features.md#private-endpoint)|
57
57
|IP access restrictions for inbound traffic|Yes, [must be explicitly enabled](../../app-service/networking-features.md#access-restrictions)|Yes, [must be explicitly enabled](../../app-service/networking-features.md#access-restrictions)|
58
58
|Network security group (NSG) integration|Supports inbound and outbound traffic control |Can use NSG for inbound traffic control using the subnet that sourced the IP of a private endpoint (Note: requires private endpoints). Supports outbound network restrictions with NSG on the virtual network integration subnet. |
59
-
|UDR integration|Supports outbound traffic routing, [must be explicitly enabled](networking.md#network-routing)|Supports outbound traffic routing, [must be explicitly enabled](../../app-service/networking-features.md#network-secure-outbound-traffic-azure-firewall)|
59
+
|UDR integration|Supports outbound traffic routing, [must be explicitly enabled](networking.md#network-routing)|Supports outbound traffic routing, [must be explicitly enabled](../../app-service/networking-features.md#)|
60
60
|Route outbound traffic over virtual network|Yes, all apps are in the same subnet and all outbound traffic is routed through the virtual network by default |[Supported](../../app-service/overview-vnet-integration.md#routes)|
61
61
|[Block inbound traffic to App Service functionality hosted on non-HTTP ports](../../app-service/networking-features.md#app-service-ports)|Supported, NSG can be used to block inbound traffic to non-HTTP ports |Not supported. In some cases (FTP and remote debugging), functionality can be explicitly disabled on a per-application basis. However, inbound network traffic can't be blocked using NSGs since the underlying App Service platform hosting infrastructure owns the listed ports. |
62
-
|Pull Docker containers over virtual network|Supported, uses the App Service Environment's subnet|[Supported](./../app-service/networking-features.md#container-image-pull)|
63
-
|Azure Functions storage account access over virtual network|Supported, uses the App Service Environment's subnet|[Supported](./../app-service/networking-features.md#content-share)|
64
-
|Backup/restore over a virtual network|Supported, uses the App Service Environment's subnet|[Supported](./../app-service/networking-features.md#backuprestore)|
62
+
|Pull Docker containers over virtual network|Supported, uses the App Service Environment's subnet|[Supported](../../app-service/networking-features.md#container-image-pull)|
63
+
|Azure Functions storage account access over virtual network|Supported, uses the App Service Environment's subnet|[Supported](../../app-service/networking-features.md#content-share)|
64
+
|Backup/restore over a virtual network|Supported, uses the App Service Environment's subnet|[Supported](../../app-service/networking-features.md#backuprestore)|
65
65
|Maximum outbound TCP/IP connections per virtual machine instance|16,000|1,920 per P1V3 instance. 3,968 per P2V3 instance. 8,064 per P3V3 instance|
66
66
|Maximum SNAT ports per virtual machine instance|Dynamic: 256 - 1,024 depending on total instance count|128 per instance|
67
67
@@ -74,12 +74,12 @@ App Service Environment v3 tends to be more expensive than the public multitenan
74
74
|Pricing |[Pay per instance](overview.md#pricing)|[Pay per instance](../../app-service/overview-hosting-plans.md)|
|Availability zone pricing|[There's a minimum charge of 18 cores.](overview.md#pricing) There's no added charge for availability zone support if you have 18 or more cores across your App Service plan instances. If you have fewer than 18 cores across your App Service plans in the zone redundant App Service Environment, the difference between 18 cores and the sum of the cores from the running instance count is charged as Windows I1v2 instances.|[Three instance minimum enforced per App Service plan](/azure/reliability/reliability-app-service.md#pricing)|
77
+
|Availability zone pricing|[There's a minimum charge of 18 cores.](overview.md#pricing) There's no added charge for availability zone support if you have 18 or more cores across your App Service plan instances. If you have fewer than 18 cores across your App Service plans in the zone redundant App Service Environment, the difference between 18 cores and the sum of the cores from the running instance count is charged as Windows I1v2 instances.|[Three instance minimum enforced per App Service plan](../../reliability/reliability-app-service.md#pricing).|
78
78
79
79
### Frequently asked questions
80
80
81
81
-[How do I know which offering is right for me?](#how-do-i-know-which-offering-is-right-for-me)
82
-
-[Can I use App Service Environment v3 and the public multitenant offering together?](##can-i-use-app-service-environment-v3-and-the-public-multitenant-offering-together')
82
+
-[Can I use App Service Environment v3 and the public multitenant offering together?](#can-i-use-app-service-environment-v3-and-the-public-multitenant-offering-together')
83
83
-[Can I migrate from the public multitenant offering to App Service Environment v3?](#can-i-migrate-from-the-public-multitenant-offering-to-app-service-environment-v3)
84
84
-[Can I use App Service Environment v3 for my development and testing environments?](#can-i-use-app-service-environment-v3-for-my-development-and-testing-environments)
85
85
-[How do I get started with App Service Environment v3?](#how-do-i-get-started-with-app-service-environment-v3)
0 commit comments