Skip to main content
Glimpse - Azure function migration from .net6 in-process to .net8 isolated

Microsoft/Azure periodically announces the end of support for some services and ask us to migrate to a new version/release when they come up with a robust solution than the deprecated.

In this post we are going to see a glimpse/UI configuration change of azure function 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗳𝗿𝗼𝗺 .𝗻𝗲𝘁𝟲 𝗶𝗻-𝗽𝗿𝗼𝗰𝗲𝘀𝘀 𝗺𝗼𝗱𝗲𝗹 𝘁𝗼 .𝗻𝗲𝘁𝟴 𝗶𝘀𝗼𝗹𝗮𝘁𝗲𝗱. Here, I'm not going to deep dive about the migration whereas going to see the illustration of changing .net version from UI. For learning, GUI is the best place to start. So, as a dev guy we would prefer azure portal mostly.

Consider a scenario that, you're requested to migrate your existing .net6 function app to be migrated .net8 isolated, you would go to settings panel and try to change the version in configuration, but the option would be disabled, it was disabled for me initially. Shocking and Afraid! After some point of time, I followed as below illustrated.

  1. Going to Configuration and verifying .𝗡𝗲𝘁 𝟴 𝗜𝘀𝗼𝗹𝗮𝘁𝗲𝗱 - it is disabled.
  2. Going to Environment Variables section under the same settings blade.
  3.   2.1 𝘊𝘩𝘢𝘯𝘨𝘦 𝘵𝘩𝘦 𝘷𝘢𝘭𝘶𝘦 𝘧𝘳𝘰𝘮 "𝘥𝘰𝘵𝘯𝘦𝘵" 𝘵𝘰 "𝘥𝘰𝘵𝘯𝘦𝘵-𝘪𝘴𝘰𝘭𝘢𝘵𝘦𝘥" for 𝙁𝙐𝙉𝘾𝙏𝙄𝙊𝙉𝙎_𝙒𝙊𝙍𝙆𝙀𝙍_𝙍𝙐𝙉𝙏𝙄𝙈𝙀 and save it.
  4. Now, you can see .Net 8 Isolated is enabled.

You may not face this scenario, but this post will help you if you come across it.
I welcome your thoughts always.

Comments

Popular posts from this blog

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...
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 ...