Bryan Soltis

This feature is currently on our roadmap. The site currently relies on the component types to be a very specific name/structure and these values not able to be changed. The...

Big update being tested! Hoping to release next week....   - Bryan

Hi @Parlax & @tkossa, I wanted to let you know we released V2.2.0 of the Azure Naming Tool that includes support for Custom Components. Please check it out and let...

Hi @Jonatan-V , That's a great suggestion! We are working with other Microsoft teams to get the image hosted in a public registry and hopefully will have that soon! -...

Hi @JClarke90, This is a feature we are considering, but it has implications on name length/symbols/etc. when it's a free form text field. We will continue to research the concept...

Hi @andreabisiach, Thank you for your feedback! The JSON files within the tool are heavily customized to combine lots of different aspects for resource types (name, short name, regex, invalid...

Hi Andrea, OK, I believe I understand your feedback now. You are suggesting always loading the resourcetypes.json/resourcelocations.json from a public location, and then allowing an override capability for the desired...

Great ides. We are working on getting the image included in mcr.microsoft.com, however, it's a bit of a process that will take some time. We know many people will want...

Hi @iamjatingohil, Thank you for your feedback. The issue you are seeing is most likely due to multiple resource types having the same "short name" value. In your case, both...

To clarify, our upcoming fix WILL allow for duplicate names with resource types. Hope this helps! - Bryan