Microsoft.Sql/servers/databases - collation entry not supported by Azure SQL db

201-sql-database-transparent-encryption-create ([Template link](https://github.com/Azure/azure-quickstart-templates/blob/master/201-sql-database-transparent-encryption-create))

### Issue Details
In an existing Azure SQL db I use collation "SQL_Latin1_General_CP1_CI_AS" but when authoring the ARM template in VS 2017 (like the one in this quick start) i always get an irritating squiggly saying that it does not conform to the schema. But on the other hand - if I use the collation closets to the one I want (SQL_Latin1_General_Cp1_CI_AS_KI_WI) I get an deploy error (see image below)


If I ignore the schema violation and deploy it anyway everything work like a charm!

Tried exporting the arm template from the Azure Portal on an existing SQL DB and it seems to be sticking.


Start with the linked 201-sql-database-transparent-encryption-create quickstart and compare its collation entry with the existing Azure SQL database behavior described. Reproduce the VS 2017 schema warning and the deployment error for SQL_Latin1_General_CP1_CI_AS versus SQL_Latin1_General_Cp1_CI_AS_KI_WI; done means the schema and deployment behavior agree with the supported collation.

Written by the indexing model from the issue text.