Skip to main content
Azure Generally Available(GA) missing 🧐 - Are you not able to see the latest release of an azure service?

#cloud #azure

Hi All!

When we come to know an update from azure, we may need to implement in the existing resource or creating a new azure resource.

For example, You have an azure app service running with Premium SKU which need to be upgraded to the latest released GA or need to create a new App service with latest release SKU.

Let's take one of the latest GA of the below premium V3 (PV3) SKU.

Premium SKU are good for web app / app services which are production based workloads.

  • P0V3 - Cost effective
  • P*mv3 - Memory optimized
    • P1mv3
    • P2mv3
    • P3mv3
    • P4mv3
    • P5mv3

Ok. Let's jump into the topic

Now you're trying to create an app service with either P0V3 or P1mv3 but you were not able to find that SKU even after multiple tries like changing resource groups or creating new resource groups, and changing some regions.

At one point of time, you could see those above SKU and got surprised and now you come to know the selected azure region has these SKU but how can you know which all regions have these SKU(s)?

Yes. what you think is correct. Most of the Latest release/GA will not be available in all regions mostly.

To know it, we can use azure CLI command as below and we can save some time.

az appservice list-locations --sku P0V3 --output table

The above command returns few regions/locations as North Europe, North Central US, West Central US, West US 2 only where the latest GA SKU(s) are available as of now. Other regions will not have the SKU(s) until further news from azure/Microsoft

Please look into the below image(s).

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 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 Basic 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 No Zone / Non-Zonal - No availability zone at all Zonal - Our services can be replicated in any one of selected zones from three zones. Zone redundant - Resource will be replicated in all 3 zones. It is opposite of...
Avoid YAML Validation error in azure devops pipeline Hi All! Consider a scenario that you committed a YML CI/CD file on the repository with some syntax, indentation and/or other error(s). so that pipeline failed. After you find some errors and rectified in the repository file and committed again but pipeline still gets failed because some errors are still there. Now you afraid that even if you fixed error in all the places, what happens if pipeline failed again because your project lead or manager set up build notification mail trigger for build success and fails. you need to answer them for build fail reason. Azure devops pipelines offers YAML validation feature after altered and before committed and before run pipeline. To utilize this feature, what we do is, Instead of modifying the file from repository, Do as below Go to the specific build click "Edit Pipeline" Modify/fix errors and click "validate" as shown in the picture below ...