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

Post a Comment

Popular posts from this blog

Azure Devops Bypass policy when code push - Glimpse Devops is a culture most of the organizations embrace it. In this article let's see what is branch policy in Azure Devops (ADO). Before that, we need to know what is policy (aka) Branch policy in ADO Branch policy has set of policies to be applied on the branch typically main. By that we avoid accidental activity. Few are as Reviewers required to view the code change before move to main/master branch work item - ADO's user story / task / bug etc., any of the item number should be linked Consider a scenario that your organization's existing project has some policies like most recent code pusher can not push code again. Very rare case may happen or not, a senior developer needs a exclusion to fix an urgent pre-prod/production incident. So He/She does not want to be in that case. They want to push their code often when discussing with client manager or customer So, how can we override the bran
Post a Comment
Read more
Find your azure service/resource tab easily in chrome using an extension Irrespective of role like Azure devops, developer, network engineer, architect etc., we typically use azure portal primarily While working on issues and/or in presentation, we may require to have multiple azure tabs with different services Here consider a scenario that I am analysing an issue from logic app which uses azure function. So I need to visit logic app, function app and application insights if enabled. If we use single tab, it will take more time. So, we can have multiple tabs. Here logic app, azure function and application insights in each tab I would have. yes. It will save our time but consider that sometimes we would have more than 10 tabs at that time we may not know which tab has which resource because all browsers have A icon. So, while navigating, we may get annoyed. So, What's the solution when we use more tabs? Here we've a nice feature in chrome browser which provid
Post a Comment
Read more
Azure storage account new access tier - Glimpse Azure has introduced a new access tier for storage account called 𝐂𝐨𝐥𝐝. What is the use of it where we already have 3 access tiers as 𝐇𝐨𝐭, 𝐂𝐨𝐨𝐥 𝐚𝐧𝐝 𝐀𝐫𝐜𝐡𝐢𝐯𝐞? Let us take scenarios as below. When our document will get frequently accessed - 𝐇𝐨𝐭 When my document will be infrequently accessed (i.e Within 30 days, it can be accessed. - 𝐂𝐨𝐨𝐥 If my document will be accessed after 30 days, 𝐞𝐚𝐫𝐥𝐢𝐞𝐫 𝐰𝐞 𝐠𝐨 𝐟𝐨𝐫 𝐀𝐫𝐜𝐡𝐢𝐯𝐞 access tier but now When my document needs to be accessed within 90 days at any time - 𝐂𝐨𝐥𝐝 Data retrieval from Archive needs some process like rehydrating (i.e converting from Archive tier to (Hot or Cool) aka offline tier to online tier). To save some cost, we can go for cold tier which allows us to keep our data for 90 days instead of archive tier. Limitations and known issues. The change feed is not yet compatible with the cold tier. Object rep
Post a Comment
Read more