Allow network security groups to be created and renamed
Currently, it seems I can't create security groups without creating an instance, or rename them for that matter. Or can I?
My use case: I created an instance and and 'SSH' security group with it. Then decided I want to test HTTP as well via public IP. Oh well, I can't rename the SSH group to e.g. 'SSH+HTTP', nor can I create a new group to change the NIC to.
Jukka Palomäki
shared this idea
This remains on our long-term backlog as something we want to offer
-Mario [MSFT]
17 comments
-
Anonymous
commented
this is so lame, 5 yrs later and we cannot rename nsg and bunch of other resources...
-
Shane Foley
commented
Come on .... as Eric mentioned ... 5 yrs and nothing!
-
Eric
commented
5 years and still no movement on this thing that literally everyone wants? Why isn't renaming objects handled the same way as in AD? The real identifier is the SID, which does not change. The friendly name can be changed as often as the user wishes and it has no impact whatsoever on the underlying functionality, because AD is using the SID, not the friendly name. Not so in Azure?
-
Mark Plummer
commented
If it's easier, simply make the NAMES of azure items the CODE (which cannot be renamed) and provide a second FRIENDLY_NAME which we can view and sort etc. and can rename at will. You then don't need any refactoring, and we have our requirements met.
-
Ruben
commented
Long-term backlog? 5 years later and is still not done. Ridiculous. You can easily rename objects in AWS and Google cloud. I'm not sure why Microsoft has not implemented this thing yet. Your long-term I can tell you're going to lose lots of clients. You're just lucky Windows OS platform got your back.
-
Anonymous
commented
I emphatically agree with the poster and all previous commenters. Being able to rename the rules themselves would ALSO be most helpful - I'm halfway through a network segmentation project, and the scope just changed from "apply the rules to the subnets" to "apply the rules to the individual VMs." Now, sure, I can simply take the same NSG and apply it to the NICs of the individual VMs... but my original naming convention included frequent use of the word "Subnet" in my rule infrastructure. I really would prefer not to have to recreate all of my rules with altered names.
-
Anonymous
commented
Renaming resources is like refactoring code, it really would be helpful.
-
Juha Palomäki
commented
If renaming is hard, being able to create a copy of the existing group via GUI would help also.
-
Mark
commented
Pretty basic functionality to be missing tbh
-
Anonymous
commented
Can we make it so ANYTHING can be renamed? This is quite cumbersome that the platform does not allow any Resource to be renamed. Perhaps including the Resource Name in the ResourceId was the challenge with allowing renames to occur. And perhaps that can be the solution to implementing it as Resource Id's being dynamically generated do not appear to be a use case, thus allowing the ID's to stay the same even when a Resource is renamed.
-
Matt
commented
ditto
-
DPriya
commented
I need to rename a Security group in intune. Can someone help?
-
Mayank
commented
Same issue.
-
raihan
commented
I need to rename NSG but I can't. Microsoft, please allow us to rename NSG
-
Anonymous
commented
Yes, this please.
-
Saeed Sheikh
commented
Same problem.
-
Anonymous
commented
I would like to rename mine. I created a prototype NSG with all of my rules in it, and now that I have it defined, my original name doesn't make as much sense. Would be ideal to rename it instead of creating a new one (and re-adding all the rules) and dropping my old one.