there is no specific report...but you can backup and then use the json...but human readable will depend on the human 😉 Its good feedback to add this feature...I'll share with the team!
@@AzureAcademy Wonderful, it seems logical since most every company/organization will want to include this in design documentation, blue books and the like.
Awesome video @Azure Academy I found the following limitations on the tool which questions its usability. Could anyone let me know how they are working around these please or am I missing something here? 1. If you want to have a workload/application name component that is free text, the tool does not have the capability to do this (the only free text field seems to be instance count). This means that I need to key in all my potential workload names to appear as a drop down which is quite cumbersome 2. I can generate the same exact names by mistake if I do not manually append the instance count. Shouldn't the tool prevent this by automatically appending the instance count from the last generated name to prevent deployment failures?
Hi. I invented and help maintain the Azure Naming Tool. Thank you for your feedback. To respond to your first bullet, we have received previous feedback regarding a free form input. As a team, we agreed that free form text would hinder standardization in a naming convention. However, several months ago we did add custom components to the tool which would allow for looser restrictions on the values. Plus, you could make the custom component optional, so it isn't used for all your names. For the second bullet, the tool allows you to create a standard and generate names. While we have a logging feature, it doesn't make sense to restrict used names until we can validate the names against Azure. Azure integration is on our backlog, and we hope to add it sooner than later. Going forward, please add an issue to our GitHub repo for any feature requests or bugs: github.com/microsoft/CloudAdoptionFramework/tree/master/ready/AzNamingTool. This allows us to consolidate feedback and prioritize work. Thanks!
Thanks for sharing, it looks really interesting if it was 5 years ago. Could you imagine how much time will team spend constructing those names. For now I recommend customers (if they have enough education with cloud/Azure) to rely on suffixes and common sense. I.e. if they think region is important put region inside of the name, if function - add function. Most of information should be provided through tags and not the name. I know overall it is sensitive topic and potentially depends on industry, however what I recommend everyone is invest more in education, rather naming standards :)
Tags are great and I stress them in every video, but you must have names, and I have seen way too many customers who don’t pay attention to names, can’t find stuff, not follow corporate standards, or worse setup spreadsheets or do ad you suggest and everyone “just knows” and then no one follows it. The tool takes away the guest work and keeps track of all the names, all built on best practices of running tens of thousands of clouds, but hey, you do you 😀
@@AzureAcademy Once i was asked why do we need naming strategy. I never thought about it before so did not give a good answer. And it's probably still so. As soon as names are human readable and help identify resource type it looks to be enough. What are your thoughts?
The best naming strategy is one you can stick to. To help you, Microsoft has done a lot of work with many thousands of companies to come up with the best practices for naming in the cloud, all of that has been packed into this tool. But remember the cloud is different then a traditional on prem data center. The cloud is for disposable resources. When their job is over, delete them and build another one. The cattle type names help you to do just that, and this is what’s the toll can help you
if only Microsoft actually made sensible naming restrictions in Azure, this tool might never have been needed … It is insanely frustrating to work with naming in Azure regardless of a tool or not. Especially the 15-character limit imposed on VM NetBIOS names and why can't the name of resources that do not depend on a DNS record not be changed? Are they not based on an ID? I lost multiple hours of critical work due to these issues recently.
In a windows world we still have NetBios…not an Azure limitation…Linux, non AD Joined VMs are longer all the time…but I hear ya…technical debt holds us all back
@@AzureAcademy I understand that since I work with windows virtual machines in Azure on a daily basis. I would like to specify different name for azure VM resource than name of virtual machine netbios name. But thanks for recognizing the issues 👍 what about the 24 character length of storage accounts and the inability to change name because it is bound to a dns name? What is the reason behind this 🤔
@@AzureAcademy I am well aware of this technical debt for Windows since I have worked with it for many years. However, I am really puzzled as to why such a thing as NetBIOS and WINS is not at least disabled or removed entirely from new Windows operating systems and Active Directory. Apart from frustrations it also poses security issues. Can you shed some light on this? Also what could be the limiting factor that prevents renaming resources in Azure as well as tying some of them to public DNS names?
In the Azure layer you cannot change the names of any resources. The 24 character limit on storage accounts is an arbitrary one…as for how that could be ok but a VM can’t be over 15…the storage account doesn’t always join the domain…where it does I believe you the limit
🔥AFTER THIS 👉 tinyurl.com/AzureAcademy-Governance 👈
Didn't know this tool, thank you for sharing!
It is brand new…happy to share
Great video, thanks Dean!
Thanks Stuart!
Is there any way to generate, for documentation purposes, a human readable report on what naming conventions have been set up?
there is no specific report...but you can backup and then use the json...but human readable will depend on the human 😉 Its good feedback to add this feature...I'll share with the team!
@@AzureAcademy Wonderful, it seems logical since most every company/organization will want to include this in design documentation, blue books and the like.
Agreed
Awesome video @Azure Academy I found the following limitations on the tool which questions its usability. Could anyone let me know how they are working around these please or am I missing something here?
1. If you want to have a workload/application name component that is free text, the tool does not have the capability to do this (the only free text field seems to be instance count). This means that I need to key in all my potential workload names to appear as a drop down which is quite cumbersome
2. I can generate the same exact names by mistake if I do not manually append the instance count. Shouldn't the tool prevent this by automatically appending the instance count from the last generated name to prevent deployment failures?
Good questions…let me see if I can get you some answers
Hi. I invented and help maintain the Azure Naming Tool. Thank you for your feedback. To respond to your first bullet, we have received previous feedback regarding a free form input. As a team, we agreed that free form text would hinder standardization in a naming convention. However, several months ago we did add custom components to the tool which would allow for looser restrictions on the values. Plus, you could make the custom component optional, so it isn't used for all your names. For the second bullet, the tool allows you to create a standard and generate names. While we have a logging feature, it doesn't make sense to restrict used names until we can validate the names against Azure. Azure integration is on our backlog, and we hope to add it sooner than later. Going forward, please add an issue to our GitHub repo for any feature requests or bugs: github.com/microsoft/CloudAdoptionFramework/tree/master/ready/AzNamingTool. This allows us to consolidate feedback and prioritize work. Thanks!
Thanks Jason
@@jasonmasten1691 Thank you so much, will do!
@@AzureAcademy Thank you so much for all the help!
Nifty! Looks like we can add a customer field too, have lots of customers with their own tenants and 0 consistency!
cool, so glad this will be a help to you!
this should simply be integrated into the azure portal experience ;)
I'm working on it! Stay Tuned!
Thanks for sharing, it looks really interesting if it was 5 years ago. Could you imagine how much time will team spend constructing those names. For now I recommend customers (if they have enough education with cloud/Azure) to rely on suffixes and common sense. I.e. if they think region is important put region inside of the name, if function - add function. Most of information should be provided through tags and not the name. I know overall it is sensitive topic and potentially depends on industry, however what I recommend everyone is invest more in education, rather naming standards :)
Tags are great and I stress them in every video, but you must have names, and I have seen way too many customers who don’t pay attention to names, can’t find stuff, not follow corporate standards, or worse setup spreadsheets or do ad you suggest and everyone “just knows” and then no one follows it.
The tool takes away the guest work and keeps track of all the names, all built on best practices of running tens of thousands of clouds, but hey, you do you 😀
@@AzureAcademy Once i was asked why do we need naming strategy. I never thought about it before so did not give a good answer. And it's probably still so. As soon as names are human readable and help identify resource type it looks to be enough. What are your thoughts?
The best naming strategy is one you can stick to. To help you, Microsoft has done a lot of work with many thousands of companies to come up with the best practices for naming in the cloud, all of that has been packed into this tool. But remember the cloud is different then a traditional on prem data center. The cloud is for disposable resources. When their job is over, delete them and build another one.
The cattle type names help you to do just that, and this is what’s the toll can help you
Btw can it run on ACI?
anywhere you run containers
if only Microsoft actually made sensible naming restrictions in Azure, this tool might never have been needed … It is insanely frustrating to work with naming in Azure regardless of a tool or not. Especially the 15-character limit imposed on VM NetBIOS names and why can't the name of resources that do not depend on a DNS record not be changed? Are they not based on an ID? I lost multiple hours of critical work due to these issues recently.
In a windows world we still have NetBios…not an Azure limitation…Linux, non AD Joined VMs are longer all the time…but I hear ya…technical debt holds us all back
@@AzureAcademy I understand that since I work with windows virtual machines in Azure on a daily basis. I would like to specify different name for azure VM resource than name of virtual machine netbios name. But thanks for recognizing the issues 👍 what about the 24 character length of storage accounts and the inability to change name because it is bound to a dns name? What is the reason behind this 🤔
@@AzureAcademy I am well aware of this technical debt for Windows since I have worked with it for many years. However, I am really puzzled as to why such a thing as NetBIOS and WINS is not at least disabled or removed entirely from new Windows operating systems and Active Directory. Apart from frustrations it also poses security issues. Can you shed some light on this? Also what could be the limiting factor that prevents renaming resources in Azure as well as tying some of them to public DNS names?
In the Azure layer you cannot change the names of any resources. The 24 character limit on storage accounts is an arbitrary one…as for how that could be ok but a VM can’t be over 15…the storage account doesn’t always join the domain…where it does I believe you the limit
Really don’t know why netbios or WINS for that matter are still around…could be fled legacy Authentication requirements
Thanks mate,
Wonderful tool.
One less thing to worry about 😊
Hey, what’s wrong with Australia, you don’t like us 😂😂😂 JK…
LOL ha ha, nope! Jk. One of the coolest places I have heard about! Lots of unique animals too
@@AzureAcademy
That's true.
Why don't you visit Australia??
I am sure you'll love it.
👍☺️👍