Add support for Azure Sql

[markhbrown]

One thing to keep in mind is that the sql server name needs to be lower case. So this may not fit in with the current working of yo vsts as it created resources with upper case.

What else I've found when you are supplying the admin password for the sql server and providing it via the variable section for the Azure Deployment task you need to have it in quotes - that's what's been causing the issue that we discussed via twitter (I also removed the ConvertTo-SecureString also as I didn't need it).

Any questions give me a shout but thought I'd add pointers that have stumped me along the way.

[DarqueWarrior]

Each time I start to add this to yo Team I get stuck on what the initial database schema should be? I don't want to create a database that is useless. If you are just using this for demoware it is not that big of a deal. But if you really want to grow this into something real it gets tough. It would be really easy to add a SQL Server and DB to the ARM template that gets created. We can set the connection string using the ARM template. If this is a grow up situation then that is as far as I think I should take it.

This then leaves the DB portion of the pipeline up to the user. Do they use EF Code First, SSDT or ReadyRoll?