Skip to main content

List of IPs used by each Azure Resource (service)

It is not uncommon to configure the firewall and other security and control mechanism like User Defined Routes (UDR) and NGA (Network Security Groups) to restrict access to your Azure Resources. In the moment when we want to do such a thing we need to know the IPs that are used by Azure Infrastructure.

Let’s take as example a web application that is hosted inside App Service (using VNETs, Traffic Manager, Azure Storage, Azure SQL and many more). To be able to properly configure the access rules, we need to know what are the IPs used by Azure Storage and Azure SQL in that region, Traffic Manager IPs used for probing and so on.

Azure Region IP Range
Most of this information can be found in a XML provided by Microsoft (https://www.microsoft.com/en-us/download/details.aspx?id=41653), but I expect that this will not enought. You’ll find inside the document the IP ranges that are used by each Azure Region, but without a tag that specify what IP ranges are used by each Azure Resource it is to generic. This might not be acceptable.

Granularity 
Our clients will not allow us to accept traffic from any IP that it is used by Azure in that specific region. We need a more granular approach and allow incoming/outgoing traffic only to the IP ranges used by services that we are using.
The next step that you will do would be to search inside Azure documentation to get the IP ranges for each Azure Service that you are using. For a part of the services, you might find a clear IP range. A good example is Traffic Manager that published the IPs that are used for probing (https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-control-what-is).
Unfortunately, for other Azure Services this information is not available and you will need to use domain names to control access. This might not be all the time acceptable from client site and you will need to mitigate it.

IP Change Notifications
Let us assume that you manage to get the IP ranges of all Azure Resources that are involved in your system. Even if it is not per instance, but per Azure Resource type for each Azure Region is already good. Next thing that you want to do is to ensure that when the IP ranges are changed you can update the configuration.
Of course this can be a manual step for Maintenance and Support team that is done every month, week or day, but why not to do automate it. In theory this should be an easy step using Azure Automation as long as we would have a central location with all IPs used by each Azure Resource.
Unfortunately, this is not available yet and we need to find a workaround.

Workaround
The first thing that we need to do is to identify all locations where the list of IPs is published. Once you done this, you need to be ready to parse the page content and extract the IPs. This is not complicated and it shall be done easy.
Now, there are two ways on how you can monitor all this location. The simplest one is to check at a specific time interval if something was changed. A runbook would be trigger in the case of any changes.

Another approach is to register to page updates. This can be done easily using GitHub. Keep in mind that each page from Azure documentation is kept in GitHub. Nothings stop us to register to file changes to that specific page or project.

Conclusion
Try to be creative and find ways how you can collect data that we need. In this case I think that the most complex task is to find the pages where the list of IP range is publish and not to implement the solution itself.

Comments

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(

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

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP