DEV Community

karleeov
karleeov

Posted on

Rust Is Tier-1 at Microsoft — 5 Azure-Ecosystem Picks for the Week of Sept 12, 2026

#rust #microsoft #ai #azure

This week's Microsoft-ecosystem signal was dominated by one announcement: Rust is now a tier-1 language at Microsoft. But it wasn't alone — open-weight models, agent frameworks, and model-gateway tooling all trended hard across Hacker News, GitHub, and dev.to. Here are the five picks that matter, each with a first step you can finish in under five minutes.

1. Rust — now tier-1 at Microsoft

What it is: Rust with first-class, officially supported tooling across Windows, Visual Studio/VS Code, and the Azure SDK. Tier-1 means supported, not experimental.

Why now: The rustfoundation.org guest post announcing tier-1 status hit 710 points / 481 comments on Hacker News this week — the highest-ranked Microsoft-ecosystem item in the entire signal. That's not idle curiosity; that's developers re-deciding what language their next Windows service goes in.

Tutorial angle: Zero-to-binary on Windows: install rustup via winget, wire up VS Code with rust-analyzer, cargo new, call a native Windows API with the windows crate, then tease the official Azure SDK for Rust (Blob Storage / Azure OpenAI). The full path from cargo new to an Azure call is maybe 20 minutes.

Difficulty: Beginner

  • Start today: Run winget install Rustlang.Rustup (the installer links you to the Visual Studio C++ workload if you're missing build tools), then open a fresh terminal and run rustc --version. If it prints, you're in.

2. routeVSCODE (9Router) — hot-swap models in Copilot Chat

What it is: A community-built local proxy that lets VS Code's Copilot Chat switch AI models mid-conversation with zero reloads.

Why now: The repo (yudaprasetya007/routeVSCODE) was created 2026-09-10 and already sits at 327 stars on GitHub's trending-new list — two days old and riding a very real frustration with the default model-picker workflow.

Tutorial angle: Install the proxy, point Copilot Chat at the local endpoint, then switch models live mid-thread and compare before/after against the default picker. One caveat worth repeating in any tutorial: this is unofficial tooling that routes Copilot traffic through a local proxy — check your org's policy before using it on work code.

Difficulty: Intermediate

  • Start today: Run git clone https://github.com/yudaprasetya007/routeVSCODE and read the README end to end, proxy setup included, before pointing any Copilot traffic at it.

3. Foundry Local — open-weight models on your own hardware

What it is: Microsoft's CLI-driven local runtime for serving open-weight LLMs on your own machine, behind an OpenAI-compatible endpoint.

Why now: Open-weight models are the week's biggest story — DeepSeek v4.1 Flash at 980 points / 558 comments on HN and Mistral's €3B open-weight raise at 844 points. Foundry Local is the Microsoft-native way to run that class of model without a cloud bill.

Tutorial angle: Install the foundry CLI, run foundry model list, download and serve a model, then hit the localhost OpenAI-compatible endpoint from a small .NET console app — or point Copilot Chat at it. Natural follow-up: promote the same model to Azure AI Foundry when you need scale.

Difficulty: Beginner

  • Start today: Run winget install Microsoft.FoundryLocal-CLI, then run foundry model list to see exactly which models your hardware can serve.

4. Microsoft Agent Framework — the Semantic Kernel + AutoGen successor

What it is: Microsoft's unified .NET/Python framework for building AI agents and workflows — the successor that merged Semantic Kernel and AutoGen.

Why now: Agents dominated the week: OpenAI's Agents API docs front-paged HN at 316 points, and dev.to's #ai feed is wall-to-wall agent pain ("My Agents Never Get Tired. I Do" — 20 reactions; "Did I Build a Worse LangGraph?" — 2). The .NET-native answer to that pain deserves a proper primer.

Tutorial angle: dotnet new console, add the Agent Framework packages, register one real tool (list your Azure Storage containers via the Azure SDK), and run the agent loop in a terminal backed by a GitHub Models endpoint. One real tool beats five fake ones for teaching the loop.

Difficulty: Intermediate

  • Start today: Run dotnet new console -o first-agent && cd first-agent && dotnet add package Microsoft.Agents.Core — from there you're one class away from a running agent loop.

5. GitHub Models — the free model gateway you already have

What it is: GitHub's built-in model gateway: a playground plus inference API for frontier and open models, free with your GitHub account and wired straight into Copilot Chat.

Why now: "So you want to use OpenRouter?" trended at 452 points on HN — multi-model single-endpoint access is the flavor of the month, and most developers already have the Microsoft equivalent sitting unused in their GitHub account.

Tutorial angle: Enable GitHub Models, switch models from inside VS Code's Copilot Chat model picker, then call the same model from a script using a personal access token against the GitHub Models inference endpoint. The "same model, playground to code" continuity is the hook.

Difficulty: Beginner

Start with this today

If you only do one thing from this list, do GitHub Models — it's the only pick with zero install and zero cost:

  1. Open https://github.com/marketplace/models
  2. Sign in with your existing GitHub account
  3. Pick any model and send it a prompt in the playground
  4. Open VS Code, start a Copilot Chat, and switch models from the model picker

That's the whole loop — playground to editor to (next) inference API — in under five minutes. Once you've felt the model-switching workflow, the Foundry Local install is the natural next step for when you want those same models on your own hardware.

Picks of the week

  • The HN thread on Rust tier-1 (rustfoundation.org guest post) — 481 comments, and the comment section is where you learn what "tier-1" actually commits Microsoft to.
  • DeepSeek v4.1 Flash — the release that made local runtimes like Foundry Local suddenly practical.
  • "So you want to use OpenRouter?" (HN, 452 pts) — required reading before you pay for a gateway you may already have.

Question for you: now that Rust is tier-1 at Microsoft, does that change what you'd reach for on your next Windows service — or is C# still the default until the ecosystem catches up? Tell me in the comments.

Connect

If this kind of post is useful, the easiest way to support the work is to:

Top comments (0)