I haven't done .Net for a couple years but Microsoft never really supported F#. It wasn't a full-fledged citizen in their web frameworks; you could include compiled modules that you made with F# but couldn't use it the way you use VB or C#. And you'd think a functional language would be great for data transformations in SSIS, but same deal there, just VB or C#.

Microsoft always positioned it as "use F# for the hard stuff and C# for the rest." The trouble is that C# isn't that bad for the hard stuff, and if you're spending most of your time with C#, then for you it's probably better than F#.

Microsoft's management cannot make their mind what it is good for, mainly because FP is not really something that 99% of typical enterprise developers care about.

When they made it officially part of .NET, it was the black swan of .NET languages with tooling only for libraries and command line applications.

Afterwards they attempted to position it as a language for ASP.NET MVC applications.

Then they largely left it for the community as F# was one of their very first FOSS projects.

Meanwhile the new MDIL compiler came out for Windows 8.x, followed by .NET Native, none of them support MSIL features required by F#.

Likewise .NET Core only accounted for C# and VB.NET, and they are still reimplementing type providers and the REPL for it.

Finally after all these years F# still lacks tooling for Forms, WPF and EF.

Meanwhile C# keeps getting some F# features.

Currently F# is being positioned as a language for data science with its type providers and Azure Netbooks.