[haxiel]

Hi, Azure admin here. The Azure Policy service includes a set of built-in policies to handle tags. There's one policy that requires new resource groups to be created with specific tags. Another policy allows resources within the resource group to inherit the same tags. I think this combination of policies would solve the tagging problem quite neatly, though I haven't tested it myself.

[hkh]

Hi, I think the key issue with both the Azure policy, and the Amazon services is that they only work after a pull request has been merged. Then the build fails, and the engineer has to come back to their code, make a new Pull Request and then send it again, till it passes.

That's the feedback we got from users, so with Infracost, the Pull Request itself tells the engineer what needs to be done, along with exact code line numbers etc before going any further, so everything is fixed within the same pull request. Also, it works across all cloud providers, so FinOps can set central tags in a uniform manner no matter where the engineers are launching resources.