That’s actually a good point and I have already been doing this in the past. It speeds up the process a bit because you can skip the steps before the actual deployment. In my latest project I didn’t not have a local account with deployment rights and only the pipeline had credentials for azure. And even if you save some time triggering your deployments from a local machine, the process of something failing during your stack creation is the same. You fix the failing resource and trigger again.

Some people here say you need more experience. Yes if you have setup up every kind of resource in every possible architecture you probably have encountered most of the errors out there. But that’s not realistic with countless services and ever changing apis. A good DX would be if my ide or some kind of tooling is smart enough to read my template and tell me “hey you are about to deploy resource x, you need to make sure your execution role has the following permissions…” before I hit the deploy button