"network connection with this name already exists" when creating network connection in brand new azure subscription

Question

"network connection with this name already exists" when creating network connection in brand new azure subscription

spiceyux 5

I'm experimenting with the Dev Box solution and have created a brand new Azure subscription to experiment.

I've create the Dev center, Resource group, and Virtual network.

When attempting to create a network connection, with any name (I've even tried a few auto-generated GUIDs), I receive the error: "A network connection with this name already exists in this resource group."

I've tried just about everything I can think of, including:

Verified the same Region for all services.
Tried multiple name variations.
Deleted and created entirely new resource groups.

I feel like there is something obvious I'm missing but can't find it so am hoping for some help here. Thanks in advance!

Screenshot 2024-01-09 at 4.36.56 PM

David Watson 20 Reputation points

2024-01-10T11:29:16.3266667+00:00

I had this as I was using the same RG for everything in my test. I created a new RG for the connection and it worked.
spiceyux 5 Reputation points

2024-01-10T16:27:15.15+00:00

Thanks, David. I had created a few dif RGs while experimenting, all with the same results.

However, your comment did provide some help. I ended up trying to create a new RG from the screen shown above. I was able to add and name the NC and "create" after making the new RG. It ultimately failed, but I got a better error message that pointed me to the fact that I had no Quota availability for NCs. So, I've submitted that Quota increase, and we'll see what happens.

I'll update when I know something, but thanks for the comment!

1 answer

Your answer

David Watson 20 Reputation points

2024-01-10T11:29:16.3266667+00:00

I had this as I was using the same RG for everything in my test. I created a new RG for the connection and it worked.
spiceyux 5 Reputation points

2024-01-10T16:27:15.15+00:00

Thanks, David. I had created a few dif RGs while experimenting, all with the same results.

However, your comment did provide some help. I ended up trying to create a new RG from the screen shown above. I was able to add and name the NC and "create" after making the new RG. It ultimately failed, but I got a better error message that pointed me to the fact that I had no Quota availability for NCs. So, I've submitted that Quota increase, and we'll see what happens.

I'll update when I know something, but thanks for the comment!

Answer 1

spiceyux 5

Yup, turns out that I had to request a quota increase for network connections specifically. So, just a really bad error message.

Share via

"network connection with this name already exists" when creating network connection in brand new azure subscription

1 answer

Your answer