Ressource custom tagging

%3CLINGO-SUB%20id%3D%22lingo-sub-570799%22%20slang%3D%22en-US%22%3ERessource%20custom%20tagging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-570799%22%20slang%3D%22en-US%22%3E%3CP%3EKnowing%20the%2015%20tags%20limitation%20per%20ressource%2C%3C%2FP%3E%3CP%3EIs%20there%20anyway%20we%20could%20generate%20a%20specific%20tag%20that%20would%20be%20read-only%20for%20the%20lifetime%20of%20that%20resource%20in%20order%20to%20revoke%20contributors%20the%20ability%20to%20change%20that%20specific%20tag%20name%20and%20value%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20would%20like%20to%20achieve%20is%20to%20automatically%20generate%20a%20unique%20tag%20for%20each%20resource%20that%20would%20be%20encrypted%20and%20that%20would%20contain%20some%20specific%20information%20regarding%20that%20resource%20(Client%20name%20%2F%20Dept%2C%20RessourceType%2C%20RessourceGroup%2C%20RessourceType%2C%20etc).%20Since%20the%20value%20is%20limited%20to%20256%20characters%2C%20I%20would%20use%20a%20table%20where%20each%20character%20has%20a%20specific%20signification.%20That%20would%20be%20used%20for%20reporting%20but%20also%20to%20repopulate%20other%20tags%20of%20each%20resource%20in%20the%20case%20some%20contributors%20change%20their%20values.%3C%2FP%3E%3CP%3EThanks%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-570799%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-575859%22%20slang%3D%22en-US%22%3ERe%3A%20Ressource%20custom%20tagging%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-575859%22%20slang%3D%22en-US%22%3E%3CP%3ESeems%20like%20this%20would%20get%20more%20attention%20in%20Azure%20Feedback%20-%26gt%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ffeedback.azure.com%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Ffeedback.azure.com%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Visitor

Knowing the 15 tags limitation per ressource,

Is there anyway we could generate a specific tag that would be read-only for the lifetime of that resource in order to revoke contributors the ability to change that specific tag name and value ? 

What I would like to achieve is to automatically generate a unique tag for each resource that would be encrypted and that would contain some specific information regarding that resource (Client name / Dept, RessourceType, RessourceGroup, RessourceType, etc). Since the value is limited to 256 characters, I would use a table where each character has a specific signification. That would be used for reporting but also to repopulate other tags of each resource in the case some contributors change their values.

Thanks :)

2 Replies

Seems like this would get more attention in Azure Feedback -> https://feedback.azure.com

Permission on TAG can't be set, you can add a feedback as already suggested.