Instance-level Public IP Address (PIP)
Updated: January 13, 2015
An instance-level public IP (PIP) is an IP address that you can assign directly to your VM, rather than to the cloud service that your VM resides within. This doesn’t take the place of the VIP that is assigned to your cloud service. Rather, it’s additional IP address that you can use to connect to your VM. You can assign one PIP for each VM. You can use up to 5 PIPs per subscription. At this time, PIP is not supported for multi-NIC VMs.
If you want to be able to connect to your VM or role instance by an IP address assigned directly to it, rather than using the cloud service VIP:<portnumber>, request a PIP for your VM or your role instance.
Passive FTP - By having a PIP on your VM, you can receive traffic on just about any port, you will not have to open up an endpoint to receive traffic. This enables scenarios like passive FTP where the ports are chose dynamically.
Outbound IP - Outbound traffic originating from the VM goes out with PIP as the source and this uniquely identifies the VM to external entities.
Yes. For pricing details, see Instance-level public IP pricing.
<NetworkConfiguration> <VirtualNetworkSite name="VNet"/> <AddressAssignments> <InstanceAddress roleName="VMRolePersisted"> <Subnets> <Subnet name="Subnet1"/> <Subnet name="Subnet2"/> </Subnets> <PublicIPs> <PublicIP name="public-ip-name"/> </PublicIPs> </InstanceAddress> </AddressAssignments> </NetworkConfiguration>
You can use either Windows PowerShell or Rest APIs to create an instance-level PIP. Use the Windows PowerShell cmdlet samples below to work with PIPs.
New-AzureVMConfig -Name "FTPInstance" -InstanceSize Small -ImageName $images.ImageName | Add-AzureProvisioningConfig -Windows -AdminUsername narayan -Password abcd123 | Set-AzurePublicIP -PublicIPName "ftpip" | New-AzureVM -ServiceName "FTPinAzure" -Location "North Central US"