Instance Level Public IP in Azure

Hello Folks,

Today I was in Calgary Alberta, delivering an Azure for IT professionals as part of a series of events we are delivering across the country.

One of the discussion we had was about IP addresses in Azure.  More to the point we were discussing “Instance Level Public IP” (ILPIP). An ILPIP formally known as a Public IP (PIP) is an address that you can assign directly to your VM, rather than to the cloud service that your VM or role instance reside in.  I wrote about this almost a year ago. Today will look at setting those up in the preview portal.

The ILPIP doesn’t take the place of the VIP (Virtual IP) that is assigned to your cloud service. It’s an additional IP address that can be used to connect directly to your VM. You would assign a ILPIP to a VM if for some reason you needed to connect directly to the VM, instead of using the cloud service VIP:<port number> or endpoints.

Difference between ILPIP and VIP

By having an ILPIP on your VM, the traffic on just about any port will reach your VM without the need for an endpoint to receive traffic.

Assign the ILPIP

Assigning the ILPIP at the creation of the VM is very simple.  You need to logon the preview portal create the virtual machine.

1- Click New
2- Compute
Select the OS you want to deploy


4- Ensure you change the deployment model to Resource Manager
5- Click Create.


6-Fill the info for the Basic Info (machine name administrator account and password….) and the machine size.
7- Click Settings
8- Click Public IP
9-Click Create New and give it a name.

Click OK in every blade of the UI and click create


After the machine is up and running you can navigate the portal Resource groups-> RG-PRtest-IP (that is what I name my resource group)

1- After that you select the NIC you created
2- Note your new ILPIP.


Here you go.  no need in the new portal to use PowerShell to assign Public IP addresses to a specific VM.  you still can if you want…  but the functionality is now in the Portal.

I hope this helped.



Pierre Roman

Comments (0)

Skip to main content