App Service on Azure Stack Overview

App Service on Azure Stack is the Azure offering brought to Azure Stack. The App Service on Azure Stack installer will create the following set of role instances:

  • Controller;
  • Management (Two instances will be created);
  • Front-End;
  • Publisher;
  • Worker (in Shared mode)

In addition, the App Service on Azure Stack installer will create a file server.

What's New in Technical Preview 3 of App Service on Azure Stack?

App Service in the Azure Stack Portal

Technical Preview 3 of App Service on Azure Stack, builds on top of the second preview and brings a preview of Azure Functions to Azure Stack. Azure Functions is an event-based serverless compute experience to accelerate your development. New improvements to the stability of the service, updates to the Tenant Portal experience along with updates to the installer experience to give more configuration options.

Limitations of the Technical Preview

There is no support for the App Service on Azure Stack preview releases, although we do monitor the Azure Stack MSDN Forum. Don't put production workloads on this preview release. There is also no upgrade between App Service on Azure Stack preview releases. The primary purposes of these preview releases are to show what we are providing and to obtain feedback.

What is an App Service Plan?

The App Service resource provider uses the same code that Azure App Service uses. As a result, some common concepts are worth describing. In App Service, the pricing container for applications is called the App Service plan. It represents the set of dedicated virtual machines used to hold your apps. Within a given subscription, you can have multiple App Service plans.

In Azure, there are shared and dedicated workers. A shared worker supports high-density multitenant app hosting and there is only one set of shared workers. Dedicated servers are only used by one tenant and come in three sizes: small, medium, and large. The needs of on-premises customers can't always be described by using those terms. In App Service on Azure Stack, resource provider administrators can define the worker tiers they want to make available. Therefore having multiple sets of shared workers or different sets of dedicated workers based on their unique hosting needs. Using those worker tier definitions, they can then define their own pricing SKUs.

Portal Features

App Service on Azure Stack uses the same UI that Azure App Service uses, as is true with the back end. Some features are disabled and aren't yet functional in Azure Stack, because Azure-specific expectations or services that those features require aren't yet available in Azure Stack.

Next steps

You can also try out other platform as a service (PaaS) services, like the SQL Server resource provider and MySQL resource provider.