Microsoft puts Rust on its top internal support tier alongside C++, C# and TypeScript

Inside Microsoft, production software moves through extensive security and quality workflows, according to the guest post ^[9]. That work costs engineering time. A team that picks an unsupported language pays for its own signed toolchain builds and for its own argument to the security reviewers. Microsoft has already put millions of dollars into supporting the Rust Project, and Azure CTO Mark Russinovich has set out the company's strategy for native code ^[13].

MSVC is the native platform compiler for Windows, and the two have co-evolved for decades ^[16]. The post calls rustc_codegen_utc one of Microsoft's most important investments toward Rust participating fully in that ecosystem ^[12]. Connecting rustc to the MSVC backend lets Rust build on the same platform investment, the post said, "with perfect compatibility out of the box, rather than requiring a parallel implementation of every Windows-specific capability" ^[10].

The post lists seven capability areas the shared backend is meant to support ^[14]. Each is something a Rust-only path on Windows would have to reproduce, and then keep reproducing as MSVC adds features. Microsoft's stated expectation is that a unified codegen platform will minimise both maintenance and evolution costs, giving what the post calls a unified code generation platform for Rust and C++ on Windows ^[18].

On deployment, the post said: "Rust has become a Tier-1 language at Microsoft, but C++ still dominates after decades of development" ^[8]. It stops short of requiring any team to use Rust or quantifying how much Microsoft code is written in it ^[19].

Two different decisions sit here: the one a team makes this quarter, and the one it makes for this decade. This quarter, a Windows-native shop weighing its first Rust component faces a narrower question, because the toolchain and compliance work it would have funded is being funded by the platform owner instead. The decade question sits with the work the post lists as unfinished: high-fidelity language-level interop, FFI contracts, bindings, language semantics differences and build systems. The post describes codegen, platform quirks, ABI, exception handling and post-link tooling as only half of the interop challenge, with those language-level items on the other side ^[6].