Syncing a local database in a VS2015 mvc6 web app to Azure is INSANELY complicated!
I have been a Microsoft developer for more than two decades. The process of syncing a local database, in an MVC6 app, to Azure is the most screwed up, counter-intuitive and ridiculous services I can recall Microsoft ever offering. You should be ashamed to have a product offering as badly designed as this one is.
Publishing the web app itself from inside VS2015 takes some time, but is drop dead simple. The database transfer needs to be exactly as simple, from the developer's perspective. Because if I'm willing to continue to use, and pay for, Microsoft products from end to end, from development through production, that's the >>only<< experience I should have.
If I wanted to go through a ******** dance involving incompatibilities between products, I'd used a multi-vendor solution. Which, BTW, would be substantially cheaper, in terms of upfront acquisition costs, than Microsoft's offerings.
If you're going to charge premium prices, and you do (since open source is "free"), you have to offer a premium experience. Or at least not a whacked out, ******** one.