Logic App Standard: The selected version ‘.NET 6 (LTS) In-process’ will deprecate on 11/12/2024. Please consider updating it soon

  • Sandro Pereira
  • Dec 18, 2024
  • 2 min read

When we create a brand new Logic App Standard inside the Azure Portal, there is no option, as far as I know, for us to specify what type of .NET Version we want to use. For example, if I select the Workflow Service Plan option on the Logic App creation wizard:

Creat a Logic App

The only options we can select/configure are the Logic App name, the region, and the Windows plan. In this case, I chose the Workflow Standard WS1.

Create a Logic App

Of course, we can configure the Storage Account settings, networking, and so on. But there is no option for us to configure the desired .NET version, or whether we will be using 64-bit or 32-bit.

So, after the creation of a brand new Logic App Standard service, I was surprised to see this warning message on the Settings > Configuration > General settings.

The selected version ‘.NET 6 (LTS) In-process’ will deprecate on 11/12/2024. Please consider updating it soon.

General settings

📝 One-Minute Brief

When creating a new Azure Logic Apps Standard resource, Microsoft still defaults to the deprecated .NET 6 LTS in‑process runtime. This article explains why this warning appears, what it means, and how to safely update the Logic App to .NET 8 to remove the alert and stay supported.

Cause

As the message describes, the reason is quite simple to understand: the .NET 6 (LTS) In-process is already deprecated (will deprecate on 11/12/2024).

The surprise here is that if I’m creating a new Logic App Standard by default, it uses a deprecated .Net version and not the most recent, as expected!

Solution

Luckily for us, the solution is quite simple to apply. To “solve” and remove this warning message, we just need to:

  • On the Logic App Standard service, access to Settings > Configuration > General settings.
  • And change the .NET version property to be: .NET 8 (LTS) In-process.
NET 8 (LTS) In-process
  • Click Save.
  • And just to make sure, access the Overview page and click Restart.
Refresh

I hope you find this helpful! If you liked the content or found it useful and want to help me write more, you can buy (or help me buy) my son a Star Wars Lego! 

Author: Sandro Pereira

Sandro Pereira lives in Portugal and works as a consultant at DevScope. In the past years, he has been working on implementing Integration scenarios both on-premises and cloud for various clients, each with different scenarios from a technical point of view, size, and criticality, using Microsoft Azure, Microsoft BizTalk Server and different technologies like AS2, EDI, RosettaNet, SAP, TIBCO etc. He is a regular blogger, international speaker, and technical reviewer of several BizTalk books all focused on Integration. He is also the author of the book “BizTalk Mapping Patterns & Best Practices”. He has been awarded MVP since 2011 for his contributions to the integration community.

Leave a Reply

Your email address will not be published. Required fields are marked *

The Ultimate Cloud
Management Platform for Azure

Supercharge your Azure Cost Saving

Learn More
Turbo360 Widget

Back to Top