Azure / Azure/azure-powershell

[Feature]: update the subnet properties directly without using "Get-AzVirtualNetwork/Set-AzVirtualNetwork"

Open
#19,585 3 comments 0 reactions 0 assignees View on GitHub
act-quality-productivity-squad customer-reported feature-request Network - Virtual Network Service Attention
Dominant language
C#
Stars
4.8k
Forks
4.3k
Avg merge
2d 17h
Merged PRs (30d)
51

Description

### Description of the new feature

when we delete the subnet via the PowerShell command, we have to execute the “Get/Set- AzVirtualNetwork ” command. it will trigger the put operation to the ARM on the “VIRTUALNETWORKS” level.

$vnet=Get-AzVirtualNetwork -Name XXX -ResourceGroupName XXX
Remove-AzVirtualNetworkSubnetConfig -Name XXX -VirtualNetwork $vnet
$vnet| Set-AzVirtualNetwork

Operation name: PUT/SUBSCRIPTIONS/RESOURCEGROUPS/PROVIDERS/MICROSOFT.NETWORK/VIRTUALNETWORKS/

Additional permission is required for the VNET operation if the DDOS plan is enabled. e.g “Microsoft.Network/ddosProtectionPlans/join/action permission"

can we have the feature to perform the “VIRTUALNETWORKS/SUBNETS” level operation directly via PowerShell?
when we change the subnet configuration from the portal or CLI, only the subnet properties will be sent to the ARM.
operation name will be "PUT/SUBSCRIPTIONS/RESOURCEGROUPS/PROVIDERS/MICROSOFT.NETWORK**/VIRTUALNETWORKS/SUBNETS/"

### Proposed implementation details (optional)

when we change the subnet configuration from the portal or CLI, only the subnet properties will be sent to the ARM.
operation name will be "PUT/SUBSCRIPTIONS/RESOURCEGROUPS/PROVIDERS/MICROSOFT.NETWORK**/VIRTUALNETWORKS/SUBNETS/"

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.