You are here:   Blog
Register   |  Login

Blog Archive:

* Can be used in order to search for older blogs Entries

Search in blogs

Blog Categories:

* Can be used in order to search for blogs Entries by Categories

Blog Tags:

* Can be used in order to search for blogs by keywords


Awared MVP


Microsoft® Community Contributor 

Microsoft® Community Contributor

 Read this before you use the blog! Maximize

Recent Entries


Written by: ronen ariely
22/04/2020 09:42 RssIcon

Hi guys,

Do you like the Azure Portal?

I bet that even if you prefer to use PowerShell to control your Azure Account, your clients probably prefer to open the browser and manage their needs using few clicks in the Azure Portal.

Well... if you do use the portal and you are going to create a new Azure SQL Managed Instance service then you should keep reading since I found a small bug, and more interesting a simple workaround. 

Let's start from the beginning...

Issue: fail to change the custom name of a new vNet

On the second step of creating new Azure Managed Instance you will see the following screen:

You can notice that the Azure Portal filled for you a default name for a new vNet, but what if we want to change this name?

according to the Portal we can create new subnet using a prefix "(new)".

Well... it sound great, so I tried to use the following name for example: (new) my-vnet/ManagedInstance

Unfortunately, this does not work and I only get a message saying that no result were found

Each time I try to fill a name like this the browser change it back to the default name which the Azure filled for us originally.

So, can we change the name of the new vNet?!?


Before we start! Let me remind you that this is NOT a recommendation to use it and it is not documented which mean officially you should not use it for production and anything that you do is on your own responsibility!

Since I was wondering why this is not working and I notice no communication between the browser and the Portal at this time, it seems like this limitation is guarded in the client side.

I decided to test this theory: (1) Click f12 to open the developer mode in the browser. (2) Edit the content of the field in the HTML code. (3) continue with the portal to create the managed Instance.

And what do you know... This seems to work OK 😀


With a small hacking using simple HTML knowledge we enable to change the default new name of the vNet while creating new Azure SQL Managed Instance

Note! This test was done on Chrome Version 80.0.3987.122. Since this is related to the client side, there is a big option that in other versions or applications this issue will not happen in the first place and you will be able to change the name in the browser. If you do have new information on this I will be happy to add it to the post. You can find me on Facebook as always or add comment here.

Have a great day and keep safe
- Ronen Ariely