Skip to main content

Resolving IP SKU Requirements When Adding Azure VMs to Load Balancers

When it comes to configuring Azure Virtual Machines (VMs) within a Load Balancer (LB) environment, there are essential requirements that need to be addressed to ensure optimal performance and reliability. One common challenge faced by Azure users is the necessity of configuring IP SKUs correctly. In this blog post, we'll explore this requirement, its importance, and provide a solution to address it effectively.

Understanding the IP SKU Requirement 

The IP SKU (Service Key Update) requirement plays a pivotal role in the proper functioning of your Azure infrastructure, particularly within the context of Load Balancers. Here's what you need to know:

  • IP Should Be in Standard SKU

When adding Azure VMs to a Load Balancer, it's highly recommended to utilize public IP addresses configured with the Standard SKU. The Standard SKU offers an array of advanced capabilities, including enhanced traffic management and load balancing options. By using Standard SKU, you ensure a higher degree of performance and reliability for your VMs within the Load Balancer setup.

  • Upgrading from Basic Public IP SKU to Standard SKU

In some instances, you may have initially created your VMs with a basic public IP SKU. If this is the case, it becomes necessary to upgrade your public IP addresses to the Standard SKU to meet the requirements of your Load Balancer.

How to Change the IP SKU 

To make this transition from a basic to a Standard SKU, you can utilize Azure PowerShell. Below is the PowerShell command that facilitates this transformation:

$rg = 'Your-Resource-Group-Name'
$name = 'Your-Public-IP-Resource-Name'
$newsku = 'Standard'
$pubIP = Get-AzPublicIpAddress -Name $name -ResourceGroupName $rg
$pubIP.Sku.Name = $newsku
Set-AzPublicIpAddress -PublicIpAddress $pubIP

This PowerShell script allows you to effortlessly change the IP SKU of your public IP address. It's a powerful feature that was not available in the past but was introduced by Microsoft in response to valuable feedback from Azure users.


Ensuring that your Azure VMs function seamlessly within a Load Balancer environment hinges on meticulous attention to detail when it comes to IP SKUs. By configuring your public IP addresses with the Standard SKU, you unlock advanced features and achieve improved performance. The ability to upgrade from a basic to a Standard SKU ensures flexibility and scalability in your Azure setup.

Microsoft's responsiveness to user feedback has resulted in the introduction of essential features like the capability to change IP SKUs. This enhancement simplifies IP management and empowers users to efficiently manage their Azure resources.

By adhering to these best practices and leveraging the PowerShell script provided, you can optimize your Azure infrastructure and guarantee the smooth operation of your VMs within a Load Balancer environment.


Popular posts from this blog

Solution and Step to fix CVE-2019-5736 Vulnerability - Docker

Recently a new vulnerability has been discovered in the the internet market having target to Docker services. What is this Vulnerability: In short, Docker service uses another service called as runc which is container run time to spawn and run containers. which simply means if docker task is to create docker images then runc task would be running them and attaching a process to container. So as per the recent discovery by the maintainers of runc, the code of this service was having some bug which can be used by attackers to gain the root level of access of the host machine on which docker containers are running. How it can be Exploited: This vulnerability can be exploited in two ways (1) if the docker images are in use is vulnerable making the containers build from it vulnerable also (2) if somehow attacker got the access of containers and then trying to exploit using the bug present in runc and trying to get root privileges. Solution to Fix Vulnerability: Ce

How to Generate CSR using Openssl in Linux

Before Generating CSR ,let see what is Openssl. It is nothing but a core library ,which is used for general purpose in cryptography,it is an open source product which work towards the implementation of SSL and TLS protocols. Talking about openssl, some people called the certificates generated from openssl as "self signed certificate". lets go towards now,creating CSR and private key using openssl command, Just log in to any of your Linux box and run following command as  root user  replacing the required information as per your need . [root@SVR home]#   openssl req -new -newkey  rsa:2048 -nodes -sha256 -out domain_name.csr -keyout domain_name.key -subj "/C=US/ST=state/L=locality/O=organization/OU=organization unit Dept/"  You will get output like : Then check whether ,all the information we have entered ,while creating CSR is proper ,by decoding the CSR from some online tool. First do the cat to the csr file [root@SVR home]#  cat

Multiple instances of redis

In the last post I have covered how to install redis server on Centos/Rhel using rpm method and yum method and some troubleshooting skills. In this post i am going to cover how to install and configure redis to run with multiple ports.                                                                           But why we need more ports ? If you have read my earlier post , you already know that by default redis runs on single port 6379, which any one can use it for small website to cache the data. But for heavy website like magento we need to use additional ports along with 6379 to serve different cache from different ports. Like in Magento there is simple cache which is normally stored under /var/cache directory. Then there is Full Page Cache which is stored under /var/full_page_cache and session cache which is stored under /var/session_cache. Note : Discussion about cache/full page cache/session is not under the scope for this document.