Allow for customizing new Entra ID DS Instance NSG resources (possibly others)

Scenario:  Onboarding a new AVD customer and leveraging a new instance of Entra Domain Services, there is an NSG that is created for each instance, and that is good.   However, the instance is -always- called the same thing ‘aadds-nsg’.   If I were to create the Entra Domain Services instance int he Azure Portal, I could control this name.

I'd love to have the ability to set that name during the Account Setup phase.   Seems like it shoudl be a simple request, maybe there is some complexity as to why not, but hoping to get the NSG to adhere to a naming convention that makes them unique. 

I'm not familiar with other associated resources being standardized, but would make sense there too.

 

In our use case with Azure Lighthouse, its possible to look at a view of NSG's in Azure and see multiple customer resources.  So if the resource has the same name, we then need to navigate/filter based on something else, such as resource group or subscription. 

0

Comments (2 comments)

0
Avatar
Dave Stephenson

I know I haven't seen too many requests for customizing the Entra DS creation, but I can see the use-case behind it. Especially if you have a naming scheme you need/want to follow.

Outside of the naming scheme, is there anything else in the current process you see as missing as well?

 

1
Avatar
John Tokash

I'll take another look, but I don't ‘believe' so. Maybe the intitial subnet name?  Typically that default is fine, since it makes sense, and is not visible across subscriptions like an NSG or VNET is when using delegated access across multiple subscriptions.

Not huge - but annoying when, for example, I'm looking for a particular customers NSG in the Azure portal and there are dozens of “aadds-nsg” NSG's :-)    We shy away from creating a seperate NSG under our normal naming convention because then it just gets more confusing to understand which NSG is protecting what subnets. 

Please sign in to leave a comment.