Costs will start to decrease when you start to use multitenant solutions on a PaaS basis.

The preceding example of a SQL server is a good way to explain the business aspects a little more. In general, the SQL licensing model is expensive. On top of this, you also need high-class resources to run a powerful database for an application. If you could just use an existing SQL server with your database, this would certainly cost less per database, and if you think about your IT infrastructure, how many SQL servers are running with only a single database on them? How many resources could be set free if you started using these databases on a single SQL server cluster?

If we go a step further and move this example to a private-cloud environment with hybrid connectivity, you will have to rethink the story a little bit. If you are running the Azure Stack environment, this means that you will have run the SQL server environments yourself. If you are using an Azure Stack environment in a service provider, you would not have to be responsible for running the environment. This needs to be considered when planning your hybrid cloud environment.

As Azure Stack owns the concept of resource providers, you will notice that each additional resource provider will follow the same concept to interact with the ARM technology. In general, you will see that each new PaaS solution from Azure Stack will bring their own virtual machines (with a minimum of one) with their own web service and some ARM integrations.

For GA, you will find the following three additional resource providers with PaaS solutions:

• Microsoft SQL Resource Provider
• MySQL Resource Provider
• App Service Resource Provider