Unable to add new subnet in existing virtual network

Question

Unable to add new subnet in existing virtual network

Rishi Kesh Singh 175

Hello,

I am adding a new subnet to the existing virtual network but it is showing below error message.

Failed to save subnet 'Subnet Name'. Error: 'Cannot proceed with operation because resource "/subscriptions/07145b12-0ef3-4d56-bc32-d7f44addf/resourceGroups/xyz/providers/Microsoft.Network/virtualNetworkGateways/xyz" used by resource "/subscriptions/07145b12-0ef3-4d56-bc32-d7f44addf/resourceGroups/Virtual network name/providers/Microsoft.Network/virtualNetworks/abc/subnets/abc" is not in Succeeded state. Resource is in Failed state and the last operation that updated /is updating the resource is PutVirtualNetworkGatewayOperation.'

Virtual Network range is : 10.2.0.0/21 multiple subnets are created.

Subnet is already created

10.2.3.0/27

I have tried to add the new subnet mentioned (tried both) below but failed and showing above mentioned error.

10.2.3.32/27

10.2.3.32/28

Can anyone help us why getting this error?

Rishi Kesh Singh 175 Reputation points

2024-09-09T07:41:10.74+00:00

Any Impact on our production environment after running the mentioned command?

Can we perform this via the Azure portal?

Answer accepted by question author

0 additional answers

Your answer

Rishi Kesh Singh 175 Reputation points

2024-09-09T07:41:10.74+00:00

Any Impact on our production environment after running the mentioned command?

Can we perform this via the Azure portal?

Answer 1

KapilAnanth 49,876 Moderator

@Rishi Singh ,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you are unable to add a subnet to a VNET.

From your error message, it appears,

There is a VPN Gateway "xyz" deployed into the VNET
And this VPN Gateway is in a failed state

As next steps,

You have to first bring the VPN Gateway to a succeeded state
You can do this by doing a GET and SET Operation on the VPN Gateway, with some minor changes (which you can revert back)

$Gateway = Get-AzVirtualNetworkGateway -ResourceGroupName "<ResourceGroupName>" -Name "<VPNGatewayName>"
Set-AzVirtualNetworkGateway -VirtualNetworkGateway $Gateway -Tag @{ testtagKey="SomeTagKey"; testtagValue="SomeKeyValue" }

The above example adds a tag which you can later remove, once the VPN Gateway goes into a Succeeded state.

Post which, you should be able to add a subnet to the VNET

Kindly let us know how this goes and if you need further assistance on this issue.

Thanks,

Kapil

Rishi Kesh Singh 175 Reputation points

2024-09-09T07:41:35.8466667+00:00

Any Impact on our production environment after running the mentioned command?

Can we perform this via the Azure portal?
KapilAnanth 49,876 Reputation points Moderator

2024-09-09T11:01:05.04+00:00
@Rishi Singh ,

Can you check if the VPN Gateway is in failed state first?

You can check this from Portal, under VPN Gateway's Overview.

If it is indeed in a Failed State, you can then consider to run the above commands

Wrt, "Can we perform this via the Azure portal?"

I doubt it will work

But you can give it a try by adding Tags to the VPN Gateway via Portal

Wrt, "Any Impact on our production environment after running the mentioned command?"

Ideally, there shouldn't be any

However, it is recommended to have a scheduled maintenance window while you try to attempt this

Cheers,

Kapil
Rishi Kesh Singh 175 Reputation points

2024-09-09T14:32:32.8366667+00:00

I have added the TAG via the Azure portal, it's worked for me.

PS command also works for me, checked to run in the test environment.
KapilAnanth 49,876 Reputation points Moderator

2024-09-10T04:42:20.97+00:00

@Rishi Singh , Wonderful - glad the issue has been resolved now.

Please let us know if we can be of any further assistance here.

If not, kindly Accept the answer as original posters help the community find answers faster by identifying the correct answer.

Thanks,

Kapil