“App Service Plan” is “features set” + capacity
“App Service Plan” has “pricing tiers” (Free, Shared, Basic, Standard, Premium)
Apps in the same subscription and geographic location can share a plan.
Apps sharing a plan:
- have access to all capabilities and features defined in the plan
- run on resources defined by the plan
An app in App Service can be associated with only one App Service plan.
Apps and plans are contained in a resource group.
A resource group serves as the lifecycle boundary for every resource contained within it.
Different apps can be allocated to different physical resources. One usage scenario: allocate one plan for production, with dedicated resources, and another one for dev/staging, with shared resources.
Having multiple plans in a single resource group enables the definition of an application that spans across geographical regions. For example, a highly available app running in two regions includes two plans, one for each region, and one app associated with each plan. All copies of the app will be associated with a single resource group. Managing the app health is easier this way.
When creating a new app one should consider creating a new resource group.
When adding a new component for a larger application (for example, an admin portal for an existing web app), create the new component in the existing application resource group.
The Azure portal (http://portal.azure.com) does not allow one to create a service plan; instead, such a plan can be created when creating a new web site.
One can use PowerShell to create a plan, see http://blogs.msdn.com/b/shad_phillips/archive/2014/11/06/changing-azure-hosting-plans-with-powershell.aspx.
List resource groups (lookup new cmdlets after September 2015):
Switch-AzureMode -Name AzureResourceManager Get-AzureResourceGroup | select ResourceGroupName
List server farms:
Switch-AzureMode -Name AzureResourceManager Get-AzureResource -ResourceType Microsoft.Web/serverFarms | select ResourceName, ResourceGroupName, Location