Skip to main content

Different ways to access Azure instances using Public IP

Let's talk about IP Addressing in Microsoft Azure. In this post we will talk about ILPIP (Instance-Level Public IP, used to be known as PIP - Public IP) and Reserved  Public IP (that is a new feature of offered by Microsoft Azure).

Virtual IP (VIP)
Before jumping into this subject, we need to understand what is a Virtual IP (VIP).
A Virtual IP is a public IP that is assigned to a resource like Web Role, Worker Role or Virtual Machine in the moment when we create a cloud service. This VIP is allocated automatically and allow our resource to communicate with external resource. Using VIP, a request from internet can access our Azure Resource.
This VIP will never change as long as the cloud contains at least one instance of that resources. For example we can have 10 instances of Web Roles with a specific deployment. As long as we have at least one, we will not lose the IP. Only when we deprovision the resource we will lose the VIP.
A "fix" for this issue, before having Reserved Public IP was to have all the time a small instance of resources allocated all the time - a small and cheap hack.

Using VIP you could connect directly to an instance of your resource only if you would allocate use the VIP and a Port Number. For each instance of your resource you can assign a specific port. As showed below.

Instance-Level Public IP (ILPIP)
This IP can be assigned directly to your instance of your resource (like VM). In this way you can target directly your instance and not the cloud services. Basically it allow us to connect and communicate directly to a specific instance of our resource (directly to a Web Role, Worker Role or Virtual Machine instance).
For example we can connect directly from internet to a VM instance, like in the diagram below.

Even if we can access an instance of our resource directly from internet using a 'Public IP', we still cannot have a fixed and dedicated IP if you recreate your resource. The story is similar with the one from Virtual IP (VIP).

Reserved IP
This feature allows us to reserve a fixed IP to our cloud resource. This means that we can have in front of our Azure resources a public IP that will not change in time, even if we stop or reallocate this resources.

This solution is more similar with Virtual IP because the Reserved IP is in front of our cloud services. There is no public IP reserved for each instance of your cloud services. Only one public IP will be reserved for all cloud services.
This means that if you want to access a specific instance, you will need a similar solution with Virtual IP, where you map a port to a specific instance.

Based on our needs we can reserved a public IP for our cloud services or not. We should be aware that we can control at IP level only for Web Roles, Worker Roles and VMs. For Azure Services like Azure Storage, Service Bus of Event Hub we don't have any kind of control.


Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified