This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(300.8, 68%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
We got a recommendation to migrate our function apps to isolated worker model. We already have them on .net 9.0 version and now we are looking to upgrade to .net 10 version.
Can I know when will the .net 10 version be available on Visual Studio to start our migration process? I have updated the VS, yet I see 9 as latest for which support ends this November
Below are the versions I see for your reference
Here is the VS version I'm using
A family of Microsoft suites of integrated development tools for building applications for Windows, the web, mobile devices and many other platforms. Miscellaneous topics that do not fit into specific categories.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 11%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGP%3C/text%3E%3C/svg%3E)
.NET 10 support for Azure Functions in Visual Studio is not generally available yet. The Azure Functions project templates currently support up to .NET 9 Isolated, which is why you don't see .NET 10 as an option.
Microsoft typically adds support for new .NET versions after the corresponding Azure Functions runtime and Visual Studio tooling are updated. Until then, the recommended approach is to continue using .NET 9 Isolated for development and migration.
Once .NET 10 support is released, you'll need:
Visual Studio 2022 updated to the version that includes .NET 10 tooling.
.NET 10 SDK installed.
Azure Functions Core Tools and Azure Functions templates updated to versions that support .NET 10.
Since you're already using Visual Studio 2022 version 17.14.36, the absence of the .NET 10 option indicates that Azure Functions tooling has not yet added support for it. Continue with your migration to the Isolated Worker model on .NET 9, then upgrade to .NET 10 when Microsoft announces official support.
I see the .NET 9 support ends by Nov 10, 2026, if version 10 is not released by then can we continue using .NET 9? and would azure services support the same?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 41%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVH%3C/text%3E%3C/svg%3E)
Agree!!! This should be suported by now!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
you can continue to use .net 9, it just unsupported, so you can not open tickets and it may have security issues over time. azure support of .net 10 has been out for a long time.
the issue is that vs2022 does not support .net 10 and unlikely to be updated to support .net 10. you need to upgrade to vs2026 or use VSCode to build a .net 10 version
while azure functions supports .net 10 in isolated mode (released in February), Visual Studio 2022 does not support .net 10. VS 2022 supports only up .net 8.
you will need to upgrade to Visual Studio 2026 or visual studio code. your vs 2022 license will allow the visual studio code .net 10 support (though be sure the license is tied to your Microsoft account).
note: some developers have had luck manually editing the project files to .net 10., but its not supported.