Skip to main content
Azure Public IP(s) are zone redundant free of cost natively - Generally Available

Availability zone gives high availability to an application as well as information by forestalling the physical datacenter disappointments by involving replication of the asset in extra datacenter.
Azure typically has 3 zones per region (and not all regions support zone). Thus, while setting up the environment we really want to pick the right region based on our usecase.

Public IP helps to access a resource or an application publicly.

Azure offers 2 types of SKU for public IP as below

  1. Basic
  2. Standard

Only Standard SKU gives zone facility. Basic SKU is always non-zonal and this SKU also will be retired 09/2025.

Standard public IP can be fell into any of the below category

  1. No Zone / Non-Zonal - No availability zone at all
  2. Zonal - Our services can be replicated in any one of selected zones from three zones.
  3. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of "No Zone"

Unless you specifically choose or pin zone, public IP is zone redundant (i.e., single public IP is replicated in 3 zones).

I guess, as of now azure allows to select only one zone as zonal whereas you can choose more than one different zone while crating VMs

Comments

Popular posts from this blog

Azure Static Web Apps - Plan Comparison #cloud #azure Hi All! Azure Static web app is a good service when we have static web apps like javacript frameworks and libraries applictions (Ex: Angular, React, Svelte, Vue, Blazor). It also supports Python 3.10 based static web app as well as per the latest azure news. Other advantage of it is coupled with your Azure AD. so that your code can be directly pushed to azure static web app via either Azure DevOps or Github whenever code push occurs. At the time of azure static web app creation, it asks for deployment source as any one of the below. Based on the selection, it allows you to select the organization, project and repositories from the source. Azure DevOps - Azure AD connected Devops organizations will be listed out Github Other - For ex: If you want to deploy code from other organization. Below table will be helpful to choose the best pricing plan for your workload. Plan/Feature Free Standard ...
Azure Blob - Convert blob access tier on Page and append blobs Hi All Azure storage account is one of the mostly used service by many people and it has page, append and block blob types on storage blob. To have blobs in "Hot" tier incur some more cost but it is prffered for frequently accessed. so if our blob is required but less access then we can change its access tier to keep it with low cost then at the time of need we can change it back to original type. we can set access tier only for block blobs. For remaining blob types, there is no direct way to set access tiers. so how can we achieve it? we need to change blob type to block blob and apply access tier for it then when we need original blob with appropriate, we need to typecast from the recent one we converted. In the below image, Initially I have an append blob called "1.JPG". when you see it, you could not see its access tier whereas bloc blob shows as "Hot" Now, Let's...
What IP address I can not get it from Azure subnet CIDR to azure resource(s)? What? Will I not be able to get some IP(s) from subnet? How many IP(s) I am not able to get and what are they and why? Azure Virtual Network is one of the main service from azure to create private network in cloud. subnet is the main part of Vnet for segregation. while creating a subnet we have to define CIDR. If I create /24 mask subnet, I should get 256 IP(s) but why am I not getting 256 fully for my resources. I can get only 251 IP(s) because azure reserves 5 IPs from every subnet. consider I'm creating a subnet called DMZ with subnet/cidr range as 10.1.2.0/24 and I'm going to get IP(s) from 10.1.2.4, 10.1.2.5, 10.1.2.6.......10.1.2.254 and please look into the below table for the reason and IP why they are not able to assign to user created azure resources. IP Purpose 10.1.2.0 Network address 10.1.2.1 Reserved by Azure for the defau...