We're using the Visual Studio Team Services Release Feature and I'm in the process of building an fully automated CI / CD Pipeline.
I've created an Azure Resource Manager template using the VS Template that creates the typically SaaS artifacts, namely a Web App + SQL Database.
I've created the three standard VSTS Release environments dev, staging and prod. Each environment now uses the ARM Template to create an isolated product environment in azure.
Release Environnment ( e.g. dev | staging | prod )
ARM Template
- Hosting Plan
- SqlServer
- Database
- Website
- AppInsights
Because each product environment / ARM template also creates an Azure SqlServer I've hit the Azure SQL Server limit of 6 per Azure Account after 2 VSTS Projects.
After I hit this limit of six Azure SQL Server's by account I felt like going down the wrong road by creating an Azure SQL Server for each VSTS Release Environment.
How should I deploy this kind of simple Azure PaaS / SaaS application by using VSTS and ARM Templates without drawing myself into a corner of limits?
Appreciate
If you are using a MSDN Subscription, you should have this kind of limitation.
But in an Enterprise Agreement / Production Subscription you should have no limitations, or simply raise a flag to the support it should fixed in few hours.