looking for some solutions? You are welcome.

SOLVED: Azure policy to require a certain Tag be created, but not with a default value?


Is there a way to create an Azure policy that requires a Tag exist on a resource when it's created, but not check for a specific value? All the examples I've seen are for "check if tag X is there, and has value Y".

I want to simply let the user know "you need to put tag X on this resource" because the value is user-defined so I can't enforce a specific value.

For example - I need "BillingCode" on every resource, but only the person creating the resource knows their correct billing code since it's different for each person or project.

Posted in S.E.F
via StackOverflow & StackExchange Atomic Web Robots

No comments: