Notify or enforce tag values not allowed to contain common metadata strings
We ran in to an issue pulling and parsing our Azure billing data where values in our tags contained strings that matched other billing field names. And that cause our parsing to get confused and fail. A warning about the strings matching other metadata field names in the tag documentation or upon deployment would be great. Enforcement to not allow matching strings would be even better.
1
vote
