> square peg through the round hole ... Why do we want to make this hard? I work in a job where I don't get to make product decisions, I just have to "make it

> square peg through the round hole ... Why do we want to make this hard? I work in a job where I don't get to make product decisions, I just have to "make it work" on the cloud. Despite this, the only applications I've worked on in the last three years have all been ASP.NET web apps with SQL databases. Even with this pretty vanilla combo, I found hundreds of bugs or interoperability issues in Azure. These aren't esoteric things, they're not round pegs and square holes. These are Microsoft-shaped pegs that ought to fit into Microsoft-shaped holes. Things get messy the instant you step off the "tech demo MVP" happy path. Like I said: Third-party code that talks to SQL, Storage Accounts, or SQL databases other than the one of their two Platform-as-a-Service offerings! Even if you stick to just functions and Azure SQL Databases, there are still limitations and issues. Templating is painful or impossible. Data-plane RBAC is missing in action. Etc... If you're a solo developer working a tiny app deployed with click-ops to a single region, then I suppose it is "fine". For everyone else, it's not so fine...