Merge pull request #15734 from ChrisCompy/master

update to creating web app in an ASE

articles/app-service-web/app-service-web-how-to-create-a-web-app-in-an-ase.md

@@ -5,7 +5,7 @@
 	documentationCenter=""
 	authors="ccompy"
 	manager="stefsch"
-	editor="jimbe"/>
+	editor=""/>
 
 <tags
 	ms.service="app-service-web"
@@ -20,16 +20,20 @@
 
 Creating web apps is nearly the same in an App Service Environments (ASE) as it is normally.  If you are unfamiliar with the App Service Environment capability then read the document here [What is an App Service Environment](app-service-app-service-environment-intro.md).
 
-[AZURE.INCLUDE [app-service-web-to-api-and-mobile](../../includes/app-service-web-to-api-and-mobile.md)] 
-
 To create an web app in an ASE you need to first start by having an ASE.   For details around creating an ASE read the document here: [How to Create an App Service Environment](app-service-web-how-to-create-an-app-service-environment.md).
 
-The first step to creating a web app is creating or selecting an App Service Plan (ASP).  Creating an ASP in an ASE starts the same as it does normally which is by going through the web app creation flow starting with New -> Web + Mobile -> Web App.
+The first step to creating a web app is selecting your Subscription.  If you have multiple subscriptions be aware that to create an app in your ASE, you need to use the same subscription that you used when creating the ASE. The next step involves selecting or creating a resource group.  If you are unfamiliar with resource groups there is more information here: [Managing your Azure resources][ResourceGroups].  Beyond helping to manage your resources, resource groups are also important when establishing RBAC rules for your apps.  
+
+After you have selected your subscription and resource group you then need to create or select an App Service Plan (ASP).  If you need to create a new ASP in your ASE then you will need to provide a name for the ASP, select the ASE you want from Locations and to select the Worker Pool you want the ASP to be in.  This is described in greater detail below.  If you are selecting an ASP in an ASE the app creation flow is the same as creating an app normally.  This is by going through the web app creation flow starting with New -> Web + Mobile -> Web App.
 
 ![][1]
 
 
-If you are using an App Service Plan that you have already created in your App Service Environment, select that plan, enter the name for your web app and select Create.  It's the same flow as when you create a web app normally.  The major difference here is that your web app will be reached at:
+If you are using an App Service Plan that you have already created in your App Service Environment, simply select that plan, enter the name for your web app and select Create.  It's the same flow as when you create a web app normally.  You can identify the ASPs in your ASE by looking at the location that is noted under the ASP name.  
+
+![][5]
+
+When you create an app it will will be reached at:
 
 [*sitename*].[*name of your App Service Environment*].p.azurewebsites.net
 
@@ -43,29 +47,29 @@ For now, your web app name needs to be unique across the entire Azure App Servic
 
 App Service Plans are a managed set of your web apps.  When you select pricing, the price charged is applied to the App Service Plan rather than to the individual apps.  To scale up the number of instances of a web app you scale up the instances of your ASP and it affects all of the web apps in that plan.  Some features such as site slots or VNET Integration also have quantity restrictions within the plan.  You can learn more about App Service Plans from the document here: [Azure App Service plans in-depth](../app-service/azure-web-sites-web-hosting-plans-in-depth-overview.md)
 
-If you are making a new App Service Plan, there are some differences to creating an ASP in an App Service Environment.  Among other things, your worker choices are different as there are no shared workers in an App Service Environment.  The workers you have to use are the ones that have been allocated to the App Service Environment by the admin.  This means that to create a new ASP, you need to have more workers allocated to your App Service Environment than the total number of instances across all of your ASPs in your App Service Environment.  If you don't have enough workers in your App Service Environment to create your ASP, you need to work with your App Service Environment admin to get them added.
+If you are making a new App Service Plan, there are some differences to creating an ASP in an App Service Environment.  Among other things, your worker choices are different as there are no shared workers in an ASE.  The workers you have to use are the ones that have been allocated to the ASE by the admin.  This means that to create a new ASP, you need to have more workers allocated to your ASE worker pool than the total number of instances across all of your ASPs already in that worker pool.  If you don't have enough workers in your ASE worker pool to create your ASP, you need to work with your ASE admin to get them added.
 
 Another difference with App Service Environment hosted ASPs is the lack of pricing selection.  When you have an App Service Environment you are paying compute resources used by the system and do not have added charges for the ASPs in that environment.  Normally when you create an ASP you select a pricing plan which determines your billing.  An App Service Environment is essentially a private location where you can create content.  You pay for the environment and not to host your content.
 
-### Selecting your App Service Environment ###
+### Creating an ASP for your App Service Environment ###
 
-Because an App Service Environment is essentially a private deployment location, you start by selecting the ASE you wish to use from your location picker.
+To create an ASP in an ASE you start by selecting Create New in the ASP selection UI and provide a name for your ASP just as you normally would outside of an ASE.  The next step is to select the ASE you wish to use from your location picker.  Because an App Service Environment is essentially a private deployment location, it shows under Location. 
 
 ![][2]
 
-After selection the UI will update and replace the pricing plan picker with a worker pool picker.  The location shows the name of the ASE system and the region it is in.  Under the URL the domain name for the ASE replaces the normally present .azurewebsites.net with the name of the App Service Environment.
+After selection of an ASE in the location picker, the ASP creation UI will update.  The location will now show the name of the ASE system and the region it is in and the pricing plan picker is replaced with a worker pool picker.  
 
 ![][3]
 
 ### Selecting your worker pool ###
 
-Normally in the Azure App Service and outside of an App Service Environment, there are 3 sizes that are available with the selection of a dedicated price plan.  In a similar fashion, customers that own an ASE can define up to 3 pools of workers and specify the size of the VM that is used for that worker pool.  Instead of selecting a pricing plan for your ASP, you select what is called a Worker Pool.  
+Normally in the Azure App Service and outside of an App Service Environment, there are 3 compute sizes that are available with the selection of a dedicated price plan.  In a similar fashion, customers that own an ASE can define up to 3 pools of workers and specify the compute size that is used for that worker pool.  What that means for tenants is that instead of selecting a pricing plan with compute size for your ASP, you select what is called a Worker Pool.  
 
-The worker pool selection UI shows the size of the VMs used for that worker pool below the name.  The quantity available refers to how many VMs are available for use in that pool.  The total pool may actually have more VMs than this number but this value refers to simply how many are not in use.  If you need to adjust your App Service Environment to add more compute resources see the doc here [Configuring your App Service Environment](app-service-web-configure-an-app-service-environment.md).
+The worker pool selection UI shows the compute size used for that worker pool below the name.  The quantity available refers to how many compute instances are available for use in that pool.  The total pool may actually have more instances than this number but this value refers to simply how many are not in use.  If you need to adjust your App Service Environment to add more compute resources see the doc here [Configuring your App Service Environment](app-service-web-configure-an-app-service-environment.md).
 
 ![][4]
 
-In this example you can see only two worker pools available. That is because the ASE administrator only allocated VMs into those two worker pools.  The third would show up when there are VMs allocated into it.  
+In this example you can see only two worker pools available. That is because the ASE administrator only allocated hosts into those two worker pools.  The third would show up when there are VMs allocated into it.  
 
 ### After web app creation ###
 
@@ -75,6 +79,7 @@ As noted earlier, the owner of the ASE is responsible for the size of the system
 
 After creating your web app and ASP it is a good idea to scale it up.  In an ASE you always need to have at least 2 instances of your ASP to provide fault tolerance for your apps.  Scaling an ASP in an ASE is the same as normal through the ASP UI.  For more details around scaling read the document here [How to scale a web app in an App Service Environment](app-service-web-scale-a-web-app-in-an-app-service-environment.md)
 
+
 [AZURE.INCLUDE [app-service-web-whats-changed](../../includes/app-service-web-whats-changed.md)]
 
 [AZURE.INCLUDE [app-service-web-try-app-service](../../includes/app-service-web-try-app-service.md)]
@@ -84,11 +89,13 @@ After creating your web app and ASP it is a good idea to scale it up.  In an ASE
 [2]: ./media/app-service-web-how-to-create-a-web-app-in-an-ase/createasplocation.png
 [3]: ./media/app-service-web-how-to-create-a-web-app-in-an-ase/createaspselected.png
 [4]: ./media/app-service-web-how-to-create-a-web-app-in-an-ase/createaspworkerpool.png
+[5]: ./media/app-service-web-how-to-create-a-web-app-in-an-ase/selectaspinase.png
 
 <!--Links-->
 [WhatisASE]: http://azure.microsoft.com/documentation/articles/app-service-app-service-environment-intro/
 [Appserviceplans]: http://azure.microsoft.com/documentation/articles/azure-web-sites-web-hosting-plans-in-depth-overview/
 [HowtoCreateASE]: http://azure.microsoft.com/documentation/articles/app-service-web-how-to-create-an-app-service-environment/
 [HowtoScale]: http://azure.microsoft.com/documentation/articles/app-service-web-scale-a-web-app-in-an-app-service-environment
 [HowtoConfigureASE]: http://azure.microsoft.com/documentation/articles/app-service-web-configure-an-app-service-environment
-
+[ResourceGroups]: http://azure.microsoft.com/documentation/articles/resource-group-portal/
+[AzurePowershell]: http://azure.microsoft.com/documentation/articles/powershell-install-configure/