# F# Support Ok a few things here and as much as I've tried to keep up with the moving pieces I may have missed something but as far as I know it here's the state of things. About a year+ ago we merged in all the pre-compiled F# templates to our templates repo. This means you can install our templates and use them. Aaron has a good blog showing this today for templates using dotnet new: https://www.aaron-powell.com/posts/2020-01-13-creating-azure-functions-in-fsharp/ Weve also been doing work over the last few months to make sure all of our tools (VS / VS Code / Core Tools) pull from a central template "feed" to list templates. All do it, the last one was actually last month I think with the core tools. However it's also up to each tool to opt into what languages it shows. VS Code did some work a while ago to make it so when you create a project you can update the USER settings for functions language to "F#" and will render templates. I believe if you click "Show all" templates (instead of just 'verified') it shows on create too. Some details here and in linked issue https://github.com/microsoft/vscode-azurefunctions/commit/dbfa2fc5f572427aed7a4469969efc456b3af957/ As for the core tools, as I mentioned we JUST finished work so it uses the central feed for templates. We haven't yet added F# into the languages yet. I wonder if it may be as easy as adding it into this list now? https://github.com/Azure/azure-functions-core-tools/blob/3eb1c7240b0f31f419c3d223f9e2816ff6209770/src/Azure.Functions.Cli/Common/Constants.cs#L75 It's possible if that's added it will work - but don't know - I'm just poking around code. I'm also a little hesitant to make F# show up by default for everyone because we don't have things like trigger / binding samples for every F# template. The templates themselves were even contributed, so I think it likely makes sense to make it an "opt-in" language, with some basic docs on how to opt-in. At the very least should make it more discoverable. That said I'm not commiting to that work - but is a feature would be good to consider / prioritize. As for Visual Studio - I can't speak much for that directly. That's an ask better suited for the VS team directly on feasibility of adding F# project support for their addin. So for now there's a few ways to take advantage of those F# templates. There definitely are some docs that should be shored up once things land so at least people interested in F# don't have to rely only on blogs.