Microsoft Elevates Rust to Tier-1 Status Alongside C++ and C#

Victor Ciura dropped the news in a guest post on the Rust Foundation site last week. Rust now holds tier-1 language status inside Microsoft. It stands equal with C++, C# and TypeScript as one of the company’s most supported options for internal development. The designation signals far more than a label. Teams gain a complete, supported route from a developer’s laptop straight into production systems.

That path includes secure toolchains. It covers productive editors and debuggers. Quality gates, platform integrations and full compliance with Microsoft’s Security Development Lifecycle requirements all come standard. The Rust Foundation guest post lays it out plainly. “Today, Rust sits among C++, C#, and TypeScript as one of the best-supported languages for internal development at Microsoft,” Ciura wrote. He leads the Rust tooling team as a principal engineer.

The move didn’t arrive overnight. Microsoft has poured resources into Rust for years. Azure CTO Mark Russinovich once declared it time to stop starting new projects in C or C++. Distinguished Engineer Galen Hunt set an ambitious target to eliminate every line of C and C++ from Microsoft codebases by 2030. Rust forms a central piece of that plan. And the company has already shipped it in production components across Windows, Azure services and security-critical firmware.

But full tier-1 backing changes the equation for everyday engineering teams. No longer an experiment or side project. Rust receives the same engineering investment that decades of C++ development enjoyed. The payoff appears clearest in memory safety. Industry reports consistently show that memory-related bugs cause 70 percent or more of serious security vulnerabilities. Rust’s ownership model and borrow checker catch those classes of errors at compile time. Microsoft has documented the difference in its own Windows kernel work.

Earlier Rust adoption inside the company focused on high-risk areas. The Windows kernel now contains Rust code for graphics and font parsing routines that historically generated many vulnerabilities. Surface device firmware uses Rust. Parts of the Microsoft 365 stack rely on Oxidizer, a collection of Rust crates built to scale services for Outlook, Word, Excel and SharePoint. Even the Copilot technology stack draws on Rust components. The Register reported on these existing deployments days after the announcement.

The technical centerpiece enabling this elevation is a new compiler backend called rustc_codegen_utc. Microsoft engineers wired the Rust frontend directly to the UTC code generator that powers MSVC, the company’s long-standing C and C++ compiler for Windows. The result is a single unified code generation platform for both languages on the Windows platform. Cross-language inlining becomes possible. Profile-guided optimizations, hotpatching, advanced security hardening and crash analysis tools all work for Rust code without duplication.

Before this backend, Rust on Windows relied on LLVM. That delivered good performance but required parallel implementations for every Windows-specific capability. Now Rust inherits the full investment Microsoft has made in its native toolchain over decades. Compatibility is exact. Debugging matches C++ experiences. Production workflows line up perfectly. Ciura described the advantage in his post. Connecting to the existing backend avoids rebuilding every Windows feature from scratch.

The new code generator reached production readiness in early 2026. More than 100 Microsoft project repositories already build with it. Adoption grows weekly. Starting with Rust 1.90, the compiler itself can be built using rustc_codegen_utc. That self-hosting milestone matters. It proves the toolchain’s maturity for the most demanding internal use cases. A dedicated DevDiv team drove the investment. Their work forms part of a broader platform that covers supply-chain security, quality enforcement and long-term support.

Industry observers wasted little time connecting the dots. GIGAZINE covered the announcement on the same day Slashdot highlighted the original story. Japanese technology site 窓の杜 emphasized the deep integration with MSVC and what tier-1 status means for local development through to operations. The timing aligns with Rust’s growing presence elsewhere. The Linux kernel made Rust support permanent last year after estimating that up to 80 percent of its CVEs stemmed from memory safety issues that Rust prevents. Ubuntu 26.10 recently completed a full switch of core utilities to Rust implementations.

Yet Microsoft stands apart in its aggressive posture. The company contributes heavily to the Rust project itself. It funds development, maintains Windows targets at the highest tier and ships production Rust code across cloud and client. This latest step removes any remaining friction for teams that want to choose Rust but hesitated over toolchain support or organizational buy-in. The paved path exists. The tools work. The security and compliance checkboxes are checked.

Challenges remain. C++ still dominates vast portions of the Windows codebase after decades of accumulation. Porting or rewriting those systems takes time and carries risk. Rust interop with existing C++ code, while improved, demands care. Performance in some driver scenarios still requires measurement. And unsafe Rust code, necessary for certain low-level interactions, reintroduces some of the risks the language otherwise eliminates. Microsoft engineers acknowledge these realities in their internal guidance.

Even so, the direction looks set. Memory safety has moved from nice-to-have to board-level priority after high-profile incidents exposed kernel vulnerabilities. Regulators and customers increasingly ask about secure development practices. Rust delivers measurable reductions in vulnerability classes without sacrificing the performance expected from systems code. For Microsoft, the tier-1 designation cements Rust as a strategic language for the next decade of Windows, Azure and beyond.

Developers inside the company now face a clearer choice. Start a new service or driver in Rust and receive first-class support. The compiler, the debugger, the build system and the security review process all treat it as equal to established languages. That shift will accelerate adoption. It will influence partner ecosystems and independent software vendors who target Windows. And it sends a signal to the broader industry about where systems programming heads next.

Watch the repositories. More than 100 already compile with the new backend. The number climbs each week. The Rust compiler builds itself with the Microsoft toolchain. Production services run on it today. This isn’t a pilot. It’s the new baseline for native code development at one of the world’s largest software companies. Rust has arrived. Microsoft just made the commitment official.