Microsoft makes Rust a tier-1 language with a new rustc backend for MSVC

Microsoft now treats Rust as a tier-1 language for internal development, putting it in the same support tier as C++, C# and TypeScript. According to a guest post from Microsoft published on the Rust Foundation's site on September 10, 2026, and currently on the front page of Hacker News, the status means internal Rust teams get a supported route from local development all the way to production: securely built toolchains, developer tooling, quality workflows, deep Windows platform integration, and compliance with the Security Development Lifecycle requirements that Microsoft software must meet.

A new backend connects rustc to MSVC

The technical centerpiece of the announcement is rustc_codegen_utc, an alternative code generation backend for rustc that belongs to the same architectural family as the existing LLVM, GCC and Cranelift backends. It plugs into the same backend interface and routes Rust compilation through the MSVC backend, which Microsoft refers to internally as UTC.

The motivation is that Windows and the MSVC compiler have co-evolved for decades, with C and C++ as the foundation of the platform. Capabilities accumulated in the MSVC stack over that time — Windows tooling and ABI compatibility, binary hardening and code security features, post-link compliance, analysis and servicing including Hotpatch, cross-language inlining and sample-profile-guided optimization, debugging and crash-dump analysis, and profiling and coverage — can now reach Rust code without a separate reimplementation of each Windows-specific feature. Microsoft describes the result as a unified code generation platform for Rust and C++ on Windows.

One codegen platform for two languages

Microsoft is careful to note that C++ still dominates its native code after decades of accumulation, and that many systems will combine Rust and C++ for years to come. On other platforms, a hybrid project can already share an LLVM backend by building its C++ with Clang; rustc_codegen_utc creates the equivalent shared-backend arrangement for Windows-native projects where MSVC is the platform compiler. Operationally, Microsoft says this reduces duplicated engineering, and strategically it means new MSVC and Windows innovations land on a common foundation for both languages.

Code generation is only half of the interop problem, however. The post acknowledges that FFI contracts, bindings, differences in language semantics and build-system integration remain unresolved, with work happening both inside Microsoft and across the industry, including through the Rust Foundation's Interoperability Initiative.

Rollout already underway

The backend was built by a dedicated team in Microsoft's Developer Division and, according to the post, has been production-ready since early 2026. It has been self-hosted since Rust 1.90, and more than 100 Microsoft project repositories currently build with it, with additional repositories adopting it each week.

rustc_codegen_utc is one piece of a broader internal Rust platform that includes secure supply-chain builds of rustc, the standard library and associated tools, plus integration with local development, production pipelines and common quality and compliance workflows. The announcement follows years of escalating commitment: Azure CTO Mark Russinovich previously laid out a strategy favoring Rust for native code, and Microsoft has since invested millions of dollars in supporting the Rust Project.

Why it matters

Elevating Rust to tier-1 status at one of the world's largest software vendors signals how native systems development is actually evolving in practice: not a wholesale rewrite of C++ estates, but a dual-language future where the two share infrastructure. The engineering approach is the interesting part. Rather than maintaining a parallel Windows toolchain for Rust, Microsoft wired rustc into the compiler backend it has spent decades investing in, so hardening, hotpatching, diagnostics and optimization apply uniformly to both languages. That lowers the practical cost of introducing Rust into existing Windows systems, which is typically where adoption stalls. For the broader ecosystem, it offers a template for how a platform vendor can embrace Rust without abandoning its incumbent toolchain, and it pushes Rust and C++ interoperability — long the blocking issue for incremental adoption — further toward the center of the agenda.