Azure Infrastructure as Code

The goal should be that the outcome will be the same no matter how many times you run it. So if the target does exist, but it's configured weirdly, the outcome should be the same. That's kind of what are the principles of the infrastructure as code tools. If you run it again, it will override the settings. This is something called item, item potent, or item potent. And it does it enforce that over time or is it just sort of that initial setup for the app? It just the initial one.