I'm diving into ideas for building tools to enhance cloud workflows, specifically with Azure. From your experiences, I'd love to know: Which Azure services do you find challenging to automate? Where do you think Azure's tooling is still lacking? Hearing from real users in practical scenarios would really help me out!
4 Answers
Honestly, the way CosmosDB handles permissions is a pain. It still doesn’t support standard RBAC for reading and writing, which makes it pretty cumbersome to work with. It’s frustrating to deal with different RBAC settings for control and data planes.
Many users find the Application Gateway clunky because you have to deploy the whole resource at once via Bicep. This means making incremental changes for backend pools or path maps is quite tricky. Azure Search also seems tough for many since it can’t handle one-to-many relationships in search records properly.
Totally agree. We avoid using Bicep for the App Gateway because it just complicates things more. Each part of a new site's setup is scattered across different menus and takes ages to save. It's frustrating, to say the least!
I can't believe they haven't simplified the App Gateway yet. It's always been such a hassle.
Many agree the Application Gateway and Front Door require a lot of manual work, especially when making minor changes, which can take too long. Plus, AKS can be clunky due to all the different open-source tools. It's like they don't prioritize security as they should.
IAM and policy management still feels very painful in terms of automation. You can script it out, but figuring out what's wrong when things break—like with permissions or roles—is such a headache. Plus, getting networking setups right is just as tricky; one tiny misconfiguration can have you stuck for hours. Azure tools might be powerful, but they don’t always feel user-friendly for developers.
Absolutely! The separate permissions for those planes can drive you nuts. It makes everything just that much harder.