Skip to content

Commit f646c99

Browse files
authored
Merge pull request #185293 from madsd/revert
revert changes
2 parents 2282278 + cab3a23 commit f646c99

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

articles/app-service/environment/overview.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ author: madsd
55
ms.topic: overview
66
ms.date: 11/15/2021
77
ms.author: madsd
8-
ms.custom: references_regions, fasttrack-edit
8+
ms.custom: references_regions
99
---
1010
# App Service Environment overview
1111

@@ -48,12 +48,6 @@ The ASE is a single tenant deployment of the Azure App Service that runs in your
4848

4949
Applications are hosted in App Service plans, which are created in an App Service Environment. The App Service plan is essentially a provisioning profile for an application host. As you scale your App Service plan out, you create more application hosts with all of the apps in that App Service plan on each host. A single ASEv3 can have up to 200 total App Service plan instances across all of the App Service plans combined. A single Isolated v2 App Service plan can have up to 100 instances by itself.
5050

51-
> [!NOTE]
52-
> It is possible for the App Service plans and the apps they host to be provisioned in a different Subscription to the App Service Environment. This can be useful for segregating access. The prerequisties are:
53-
> - The Subscriptions must share the same Azure AD Tenant
54-
> - The App Service Environment, App Service plans and apps must be in the same region
55-
> - Today you cannot create App Service Plans and apps in a different subscription using the Azure Portal. Instead, use either [Azure REST API](/rest/api/appservice/app-service-plans/create-or-update) or [Azure Resource Manager Templates](/azure/templates/microsoft.web/allversions).
56-
5751
## Virtual network support
5852

5953
The ASE feature is a deployment of the Azure App Service into a single subnet in a customer's virtual network. When you deploy an app into an ASE, the app will be exposed on the inbound address assigned to the ASE. If your ASE is deployed with an internal virtual IP (VIP), then the inbound address for all of the apps will be an address in the ASE subnet. If your ASE is deployed with an external VIP, then the inbound address will be an internet addressable address and your apps will be in public DNS.

0 commit comments

Comments
 (0)