If your team ever gets frustrated by ARM, have them shoot me an email for my old proposal on how to fix it (source: used to work at Azure and perennially frustrated by ARM design)
Can I say "most of them"? Basically it simplifies ARM and the Azure API significantly and makes Azure operate more like "infrastructure as code". But I'd need to look at the latest version of Azure to see specifically what the remaining pain points are now. I could have a more specific conversation in a different setting.
I remember the first meetings about ARM when the resource IDs were presented, and a few people immediately asked "what if someone wants to rename a resource"? Years later you still could not do that (I'm hoping they've fixed that by now?).
It seemed to me that ARM was the result of some design by super smart committee, and got a lot wrong. When I was there more senior folks told me not to worry, that's just the Microsoft way (wait for version 3). I do have to admit that it's turning out they knew more than me (shocking!), as over time I've seen some of the stuff that was inexplicably terrible in v1 become much, much better in later versions.
If you manually rename a resource and refer to it by resource ID, I don't think ARM understands anything about it and assumes it's a new resource. That's just from using ARM, though, I don't know it's internals.
They are investing a good amount in ARM lately though. The vs code language server is pretty good and export template got much better
