Blog Post

Azure PaaS Blog
4 MIN READ

Instance level public ip address configuration in the cloud service.

Frank_Pan's avatar
Frank_Pan
Icon for Microsoft rankMicrosoft
Jan 09, 2023

An Instance-Level Public IP Address (PIP) unlike the Virtual IP Address (VIP) is not load balanced.  While the virtual ip is assigned to the cloud service and shared by all virtual machines and role instances in it, the public ip is associated only with a single instance’s NIC. The public ip is particularly useful in multi-instance deployments where each instance can be reachable independently from the Internet. The picture below illustrates the value of PIP and differentiates it from the VIP. The blog will help you understand how to configure the instance level public ip. 

 

 

For some background knowledge, please find the reference Instance-Level Public IP Address | Azure Blog and Updates | Microsoft Azure.

 

Classic cloud service:

  1. How to configurate instance level public ip by role:

<?xml version="1.0" encoding="utf-8"?>

<ServiceConfiguration serviceName="TestVirtualnetwork" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration" osFamily="6" osVersion="*" schemaVersion="2015-04.2.6">

                <Role name="WebRole1">

                                <Instances count="1" />   

                                <ConfigurationSettings>     

                                                <Setting name="APPINSIGHTS_INSTRUMENTATIONKEY" value="xxx" />

                                </ConfigurationSettings>

                </Role>

                <Role name="WebRole2">

                                <Instances count="1" />

                                <ConfigurationSettings>

                                                <Setting name="APPINSIGHTS_INSTRUMENTATIONKEY" value="xxx" />

                                </ConfigurationSettings>

                </Role>

                <Role name="WebRole3">

                                <Instances count="1" />

                                <ConfigurationSettings>

                                <Setting name="APPINSIGHTS_INSTRUMENTATIONKEY" value="xxx" />

                                </ConfigurationSettings>

                </Role>

                <Role name="WebRole4">

                                <Instances count="1" />

                                <ConfigurationSettings>

                                <Setting name="APPINSIGHTS_INSTRUMENTATIONKEY" value="xxx" />

                                </ConfigurationSettings>

                </Role>

                <NetworkConfiguration>

                                <VirtualNetworkSite name="Group <resource group> <virtual network name>" />

                                <AddressAssignments>

                                                <InstanceAddress roleName="WebRole1">

                                                                <Subnets><Subnet name="subnet001" /></Subnets>

                                                                <PublicIPs><PublicIP name="PubIP" domainNameLabel="pip" /></PublicIPs>    // with domain

                                                </InstanceAddress>

                                                <InstanceAddress roleName="WebRole2">

                                                                <Subnets><Subnet name="subnet003" /></Subnets>

                                                                <PublicIPs><PublicIP name="PubIP"/></PublicIPs> // without domain

                                                </InstanceAddress>

                                </AddressAssignments>

                </NetworkConfiguration>

</ServiceConfiguration>

 

2. How to know current public ip of role:

 

Get-AzureRole -ServiceName <Cloud Service Name> -Slot Production -RoleName WebRole2 -InstanceDetails 

 

Get-AzureRole -ServiceName <Cloud Service Name> -Slot Production -RoleName WebRole1 -InstanceDetails

 

 

Cloud Service Extended Support:

1. How to configurate instance level public ip by role:

<?xml version="1.0" encoding="utf-16"?>

<ServiceConfiguration xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" serviceName="Test_cloudservice" osFamily="6" osVersion="*" schemaVersion="2015-04.2.6" xmlns="http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceConfiguration">

  <Role name="TestWebRole">

    <ConfigurationSettings>

      <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="UseDevelopmentStorage=true" />

    </ConfigurationSettings>

    <Instances count="2" />

  </Role>

  <Role name="TestWorkerRole">

    <ConfigurationSettings>

      <Setting name="Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString" value="UseDevelopmentStorage=true" />

    </ConfigurationSettings>

    <Instances count="1" />

  </Role>

  <NetworkConfiguration>

    <VirtualNetworkSite name="test001VNet" />

    <AddressAssignments>

      <InstanceAddress roleName="TestWebRole">

        <Subnets>

          <Subnet name="default" />

        </Subnets>

        <PublicIPs>

          <PublicIP name="PubIP" domainNameLabel="pip" />

        </PublicIPs>

      </InstanceAddress>

      <InstanceAddress roleName="TestWorkerRole">

        <Subnets>

          <Subnet name="default" />

        </Subnets>

      </InstanceAddress>

      <ReservedIPs>

        <ReservedIP name="Group TESTCSES cses-prod" />

      </ReservedIPs>

    </AddressAssignments>

  </NetworkConfiguration>

</ServiceConfiguration>

 

2. Then, we can use the rest api PublicIPAddress In CloudService - List Cloud Service Public IP Addresses - REST API (Azure Virtual Networks) | Microsoft Learn to get the public ip of NIC.

 

 

 

Updated Jan 08, 2023
Version 1.0
  • saidu7059's avatar
    saidu7059
    Copper Contributor

    PIP's uniqueness lies in its direct association with a single instance's NIC, enabling independent reachability from the Internet. The blog's visual aid is helpful in illustrating this concept. If you're looking to configure instance-level public IPs, it's a valuable read. Also, don't forget to explore resources like 19216811.me for additional insights into IP configurations.