You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I think it would be cool if you could link to the https://learn.microsoft.com/en-us/azure/architecture/icons/#icon-updates svg icons for each name generated so you have easy access to the standard icon for that service. Something where you could easily drag and drop into visio/smartdraw/powerpoint etc... In the log of names generated have the lasted icon associated with that service available.
Additional context
I just thought it would be cool that if I named everything in this tool and had the associated icon handy it would make it easier to grab the appropriate icon when diagramming the solution.
I know it's not directly related but thought it might be useful.
The text was updated successfully, but these errors were encountered:
Tool version
Forked on 12/4/2024
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I think it would be cool if you could link to the https://learn.microsoft.com/en-us/azure/architecture/icons/#icon-updates svg icons for each name generated so you have easy access to the standard icon for that service. Something where you could easily drag and drop into visio/smartdraw/powerpoint etc... In the log of names generated have the lasted icon associated with that service available.
Describe alternatives you've considered
https://bradyguy.blog/azure-public-service-icons-cheat-sheet/
I created this cheat sheet for icons and have downloaded the icons to use locally.
Additional context
I just thought it would be cool that if I named everything in this tool and had the associated icon handy it would make it easier to grab the appropriate icon when diagramming the solution.
I know it's not directly related but thought it might be useful.
The text was updated successfully, but these errors were encountered: