Surface IT Pro Blog articles

Microsoft Protection Plans now deliver more coverage

rawilson — Wed, 01 Apr 2026 18:33:46 GMT

Modern organizations rely on their Surface devices every day, across offices, job sites, classrooms, and hybrid work environments. Microsoft Protection Plans help reduce unexpected repair-related costs in accordance with the plan terms.

While every Microsoft Surface device comes with a minimum of 1-year Microsoft's Limited Hardware Warranty¹, you can protect your investment further with a Microsoft Protection Plan. Microsoft has recently updated its Protection Plans to provide broader coverage and reduce uncertainties in claim boundaries for customers. These enhancements are designed to better reflect how devices are used over time and to reduce uncertainty around repairs and long‑term ownership.

2026 Protection Plan Enhancements

Unlimited Mechanical Breakdown Coverage

Microsoft Protection Plans now include unlimited mechanical breakdown coverage²for the full duration of the plan. Previously, mechanical breakdowns and accidental damage claims were combined under a two‑claim limit. With this change, hardware failures caused by defects in materials or workmanship are no longer subject to a fixed claim count limit. Devices may be repaired or replaced as needed for mechanical issues throughout the coverage term.³

Accidental Damage Claims Are Now Separate

The existing two‑claim limit now applies only to Accidental Damagefrom Handling (ADH)⁴, such as drops, spills, or cracked screens.

By separating accidental damage from mechanical breakdown coverage, customers can more clearly understand how claims are applied and avoid using accidental damage claims for issues related to normal hardware failure.

New Battery Degradation Coverage

Microsoft Protection Plans⁵ now include battery degradation coverage.

Customers can file one dedicated battery claim⁶ if a device’s battery capacity drops below 70% of its original capacity during the plan term. This marks the first time Protection Plans address battery wear over time, not just battery failures caused by manufacturing defects.

Battery eligibility can be validated using tools such as the Surface Diagnostic Toolkit. Battery degradation claims are separate from accidental damage claims, so ADH limits remain unaffected.

Together, these updates help organizations extend device life, reduce unexpected repair costs, and plan more confidently for device ownership.

Customers can add a Microsoft Protection Plan when purchasing a new device, or within the eligible post-purchase window.⁷To purchase, contact your authorized partner or reseller, or engage the Microsoft Store virtual assistant.

[Consumer customers can purchase through the Surface app or your Microsoft account.]

These updates apply only to Microsoft Complete and Extended Hardware Service plans purchased on or after the applicable effective date (April 01, 2026) and are not retroactively modified. Coverage, whether for new or existing customers, is determined solely by the relevant Terms & Conditions for the specific plan purchased.

To learn more about Microsoft Protection Plans, visit Microsoft Surface Warranty & Protection Plans.

To see Warranty and Protection Plan Terms & Conditions, visit Support.microsoft.com.

Disclaimers

Without prejudice to any legal (statutory) rights to which you may be entitled under your local law, Microsoft Limited Hardware Warranty covers your device for one year from the date of original purchase from Microsoft or an authorized reseller. Restrictions apply. Please refer to Microsoft Limited Hardware Warranty & Agreement.
Additional extended coverage for mechanical breakdown and accidental damage from handling is available through the purchase of Microsoft protection plans. If the plan provides additional Mechanical Breakdown coverage, that coverage begins upon expiration of the manufacturer’s original warranty and continues for the remainder of the term shown on the Holder’s Proof of Purchase. Accidental damage from handling begins immediately upon purchase. Restrictions apply, for all Protection Plans, please reference the Terms and Conditions for the limit of liability and the applicable exclusions of the Protection Plan.
Subject to plan terms, conditions, and limit of liability.
Accidental damage from handling is included in the following plans: Commercial: Complete for Business, Complete for Business Plus, Accidental Damage Protection (EU), Accidental Damage Protection Plus (EU), and Consumer: Microsoft Complete. Extended Hardware Service (EHS) plans provide coverage for mechanical breakdown only and do not include Accidental Damage from Handling or battery degradation coverage.
Battery degradation is included in the following plans: Commercial: Complete for Business, Complete for Business Plus, Accidental Damage Protection (EU), Accidental Damage Protection Plus (EU), and Consumer: Microsoft Complete. Extended Hardware Service (EHS) plans provide coverage for mechanical breakdown only and do not include Accidental Damage from Handling or battery degradation coverage.
Customers with eligible plans are limited to one (1) battery degradation/replacement claim as set out in plan Terms and Conditions.
Availability and timing vary by market and plan type.

Vibe Coding for the NPU

FrankBuchholz — Wed, 04 Mar 2026 21:53:07 GMT

If you just bought a Copilot+ PC and want to know what that NPU can actually do, this is for you. If you manage a fleet of them and need workload placement guidance, this is for you too.

Cloud doesn’t have to be the default anymore. The NPU (Neural Processing Unit) is now a practical and accessible development target, making it possible to run advanced AI workloads directly on your device. This means you can take advantage of your PC’s local hardware to get faster results, lower latency, and even work offline or in airplane mode. Getting started with NPU development is easier than you might expect.

Foundry Local serves models through an OpenAI-compatible endpoint on localhost, so if you’ve used the OpenAI SDK, you already know how to build for the NPU. Combine that with AI-augmented coding and you don’t need to be a pro developer... you just need to be specific about what you want.

I’m in Surface Marketing. I haven’t done daily development work since the Petzold “Programming Windows” days... back when writing a hello world app meant 90 lines of C and a WndProc callback. Early in my career I quickly figured out I wasn’t the most talented dev in the room, but I was good at integrating hardware solutions and telling the story of what they could do. Now, with vibe coding, the thing that wasn’t my vibe has become a superpower... “wait, could I vibe code that?” And the answer keeps being yes.

I just built a working on-device AI application with four tabs and five AI tasks by describing features to an AI coding assistant. This post is everything I learned along the way: the platform, the tools, the workflow, and the real considerations that only surface when you’re actually building on the hardware.

Ready to skip to the good stuff? Jump ahead:

Want a working app fast? → Your First NPU App in Minutes
Validating model choices? → AI Toolkit Model Catalog
Deploying to mixed fleets? → Cross-Platform Development + Operationalizing
Need vision capabilities? → Phi Silica
Want to see what we built? → The Surface NPU Demo App

Why does this matter? Three words: availability, economics, and data sovereignty. Details below.

Why Build for the NPU?

For years, the cloud has been powering our most demanding AI workloads. That makes sense for frontier reasoning, complex agent chains, the hard stuff. But the models that run locally now are good enough for the majority of what your fleet actually does. And by “locally” I mean the device in your user’s bag... their Surface on the train, in a customer lobby, on a job site. Not a server. Not a VM. The actual endpoint, with its own dedicated AI silicon.

Availability. An NPU-powered workflow runs in airplane mode, in a clean room, on a factory floor, in a field inspection truck in a dead zone. No connectivity required. The AI is on the device, and the device is wherever your user is.

Economics. NPU inference comes at no additional per-inference cost after the hardware purchase. No per-token API fees, no egress charges, no metered compute. I think of it as an 80/20 planning model: the majority of routine AI tasks can run locally at no incremental cost, reserving premium cloud inference for the tasks that genuinely need frontier reasoning.

Data sovereignty. When operating without cloud escalation, data is processed locally on the NPU, reducing your reliance on cross-border data transfers. As with any deployment, customers should assess their specific regulatory, legal, and operational requirements, including endpoint management, device access controls, and applicable local laws. For regulated environments, on-device AI can be a powerful part of a broader compliance and data governance strategy, but it does not replace the need for appropriate legal, contractual, and security controls.

What Is Vibe Coding?

The industry calls it AI-augmented development. The internet calls it vibe coding. Same thing: you describe what you want, an AI coding assistant writes the code, you run it, you tell it what broke, it fixes it. Repeat. You’re the architect and the QA engineer. The AI handles the implementation.

Examples include GitHub Copilot CLI, Cursor, and similar AI coding assistants. The specific tool matters less than the workflow: describe a feature, the assistant writes code, you run it, you report what worked and what broke, the assistant fixes it. The AI handles the boilerplate... Flask routes, CSS layout, regex, JavaScript event handlers. You handle the architecture decisions, the hardware testing, and the product judgment.

Why does this matter for NPU development specifically? Because AI coding assistants already know the OpenAI SDK patterns inside and out, and Foundry Local speaks a compatible API. “Compatible” means the standard SDK works for chat completions and most common inference patterns, though you may encounter minor differences in model IDs or streaming behavior. Microsoft’s documentation frames this as compatibility with “OpenAI-compatible SDKs and HTTP clients.” In practice, for the workloads covered in this post, the SDK works as-is. The barrier is significantly lower than it used to be... if you can describe a workflow, you can start building for the NPU.

How It Started: From Playground Curiosity to Working App

This is where the IT pro lesson starts: validate the model first, then write code. This didn’t start with a plan. It started with a click.

I opened VS Code, installed the AI Toolkit extension, and browsed the Model Catalog. There was a model already on the device: Phi Silica. I loaded it in the Playground, typed a message, and... it responded. On-device. No API key. No cloud endpoint. Just the NPU doing inference right there in VS Code.

Wait. I remembered from using LM Studio that local models get served on a port. If Foundry Local works the same way... could I write a web app that talks to it?

So I opened GitHub Copilot CLI and just started describing what I wanted:

“I have a local AI model running through Foundry Local on my Surface. It exposes a compatible API on a local port. Build me a Flask web app that connects to it and serves a chat interface.”

And we were off.

Copilot generated a working Flask app. I ran it. It connected to the local model. I could chat with an AI running entirely on the NPU through a web browser. No cloud, no API key, no subscription. Wild.

From there, the vibe coding loop took over. Each session I’d just describe the next thing I wanted: a sidebar with tabs, a daily briefing from local calendar data, a two-brain router for local-vs-cloud workload decisions, and finally a full field inspection workflow with voice, camera, pen annotation, and translation.

The real acceleration came when I moved from copy-paste iteration to GitHub Copilot CLI, which reads and edits the full codebase directly on the device. That’s when it went from a cool demo to a genuine multi-tab application with real architecture. Kevin Roose and Casey Newton on the Hard Fork podcast recently compared the leap in AI coding tools to the original ChatGPT moment... and having lived it, that tracks. (If you’re not listening to Hard Fork, you should be.)

Python, HTML, CSS, and JavaScript. Built primarily through conversation with AI coding assistants. By a marketing person who hadn’t done daily dev work since writing WndProc callbacks in C.

The Starting Point: AI Toolkit Model Catalog

Before writing any code, start where I started: the AI Toolkit for VS Code. Two things matter here: the Model Catalog and the Playground.

Open the Model Catalog and filter for models optimized for local NPU execution:

Model	Parameters	Strengths	NPU Support
Phi-4 Mini	3.8B	General text: summarization, extraction, generation, translation	Intel (OpenVINO), Qualcomm (QNN)
Phi Silica	N/A	On-device language and multimodal scenarios on Copilot+ PCs	Intel & Qualcomm (Windows AI APIs)
Qwen 2.5	7B	General text: larger context, stronger reasoning	Qualcomm (QNN), GPU fallback
Additional models	Varies	The catalog is growing. Check for new NPU-optimized variants regularly.	Varies by silicon

For the full local model landscape, see Ready-to-use local LLMs in Microsoft Foundry on Windows and the Windows AI overview decision tree.

The Playground is your validation sandbox. Select a model, load it, chat with it directly in VS Code. Test your prompts. Feel the latency. Hit the context limits. All before writing a line of application code. It’s also the most reliable method we’ve found to trigger the initial model download and readying for Phi Silica.

Platform Requirements

Hardware

Any Copilot+ PC with an NPU. Surface consumer Copilot+ PCs are currently Snapdragon X. Surface commercial (for Business) Copilot+ PCs are available with both Snapdragon X and Intel Core Ultra.

Silicon	NPU	Example Surface Devices
Intel Core Ultra (Lunar Lake)	Intel AI Boost, OpenVINO runtime	Surface Laptop for Business, Surface Pro for Business (Commercial)
Qualcomm Snapdragon X (Elite/Plus)	Hexagon NPU, QNN runtime	Surface Laptop, Surface Pro (Consumer), Surface Laptop for Business, Surface Pro for Business (Commercial)

Software Stack

Scope: Everything in this post is Windows-only. Foundry Local, AI Toolkit, and the NPU runtimes covered here require Windows 11 on Copilot+ PC hardware (Intel Core Ultra or Qualcomm Snapdragon X).

A note on Foundry Local: Foundry Local is currently in public preview. There is no SLA and no backward compatibility guarantee. Expect changes between releases and validate in staged rings before broad deployment. For the latest, see the Foundry Local documentation hub.

Component	Install	Learn More
Windows 11 24H2+	Windows Update	Windows AI APIs
Foundry Local (preview)	`winget install Microsoft.FoundryLocal`	Get started
Python 3.10+	`winget install Python.Python.3.11`
foundry-local-sdk	`pip install foundry-local-sdk`	SDK reference
OpenAI Python SDK	`pip install openai`	SDK integration guide
Flask	`pip install flask`
VS Code + AI Toolkit	VS Code Marketplace	AI Toolkit overview

⚠️ Package name warning: Install foundry-local-sdk (the official Microsoft SDK). Don’t confuse it with similarly named packages on PyPI. At time of writing, foundry-local (v0.0.1) is not the official SDK and may fail (or behave unexpectedly). Verify against Microsoft’s SDK documentation and PyPI.

Your First NPU App in Minutes

For the official quickstart, see Get started with Foundry Local. What follows adds the vibe coding workflow on top.

Step 1: Install the Runtime

winget install Microsoft.FoundryLocal
pip install foundry-local-sdk openai flask

Step 2: Prompt Your AI Coding Assistant

“Build me a Flask app that serves a chat interface on localhost:5000. The backend should use the OpenAI Python SDK pointed at a local Foundry Local runtime. Use the foundry-local-sdk to get the endpoint URL dynamically (don’t hardcode the port). The model alias is ‘phi-4-mini’. Make it a single-file app with the HTML inline.”

The assistant will generate something close to this:

from flask import Flask, request, jsonify
from openai import OpenAI
from foundry_local import FoundryLocalManager

# Start Foundry Local and discover the endpoint dynamically
manager = FoundryLocalManager("phi-4-mini")
client = OpenAI(base_url=manager.endpoint, api_key=manager.api_key)
model_id = manager.get_model_info("phi-4-mini").id

app = Flask(__name__)

@app.route("/chat", methods=["POST"])
def chat():
    user_msg = request.json["message"]
    response = client.chat.completions.create(
        model=model_id,
        messages=[
            {"role": "system", "content": "You are a helpful assistant."},
            {"role": "user", "content": user_msg}
        ],
        max_tokens=512
    )
    return jsonify({"reply": response.choices[0].message.content})

if __name__ == "__main__":
    app.run(host="127.0.0.1", port=5000, debug=True)

The key line is base_url=manager.endpoint. Don’t hardcode localhost:5272 or any other port. Foundry Local assigns a dynamic port each time the service starts. Always use the SDK’s endpoint discovery, or use foundry-local-sdk to resolve the active endpoint programmatically. For details, see the Foundry Local SDK reference.

Step 3: Run It

python app.py
# First run downloads the model (~3 GB). Subsequent starts are near-instant.
# Open http://localhost:5000

First model download requires network connectivity. After that, the model is cached locally and launches work fully offline. In practice, runtime or model updates and repair flows can occasionally re-trigger downloads. For cache management details, see the Foundry Local CLI reference.

Step 4: Iterate

Keep describing features. The AI coding assistant handles the implementation. You handle the testing on the actual device and the “this doesn’t work on the NPU” feedback that no AI assistant can discover on its own. Hardware-in-the-loop is the key. Don’t write a full spec. Write one feature at a time, test it, then describe the next.

Cross-Platform Development: Intel and Qualcomm

Foundry Local handles model selection across silicon families automatically through its alias system. For most developers and single-device use, you write one codebase and it works. If you’re deploying to a mixed enterprise fleet, here are the platform-specific optimizations we’ve found.

Architecture Detection Under Emulation

On Windows-on-ARM, Python x64 reports AMD64 via platform.machine(). Both it and PROCESSOR_ARCHITECTURE are wrong under emulation. Use WMI:

result = subprocess.run(
    ["powershell", "-NoProfile", "-Command",
     "(Get-CimInstance Win32_Processor).Name"],
    capture_output=True, text=True, timeout=5,
)
cpu = result.stdout.strip().lower()
if "qualcomm" in cpu or "snapdragon" in cpu:
    return "qualcomm"

Run native ARM64 Python where possible on Snapdragon devices for better performance and fewer emulation quirks.

Rule: On Snapdragon, prefer ARM64 Python. Avoid x64 emulation when you can.

Model Compatibility Varies by Silicon

Observed behavior during testing on preview runtimes (February 2026). Results may change with future Foundry Local or driver updates.

Model	Intel (OpenVINO NPU)	Qualcomm (QNN NPU)	GPU Fallback
Phi-4 Mini 3.8B	✅ Stable	⏳ NPU variant in development	✅ Both
Phi-3.5 Mini	✅ Stable	✅ NPU (Foundry 0.8.119+)	✅ Both
Qwen 2.5 7B	✅ Stable	✅ Stable	✅ Both
Phi Silica (text + vision)	✅ NPU	✅ NPU	N/A (Windows AI)

Foundry Local handles variant selection by alias. You request phi-4-mini, it pulls the best available build for your hardware. Model availability across NPU execution providers is expanding with each Foundry Local release. For tool-calling workloads on Qualcomm today, Qwen 2.5 7B is fully NPU-accelerated and production-ready. Your AI coding assistant handles the detection and model routing automatically.

Runtime Lifecycle Differs

if SILICON == "qualcomm":
    # Skip warmup - QNN is unstable with rapid reconnection attempts
    print("Skipping warmup on Qualcomm (first request will load model)...")
else:
    # Intel: warmup + keepalive for consistent latency
    warmup_model()
    start_keepalive_thread(interval=180)

Intel benefits from warmup and keepalive pings every 3 minutes. Qualcomm is the opposite: warmup destabilizes the QNN runtime. Let the first real request trigger model load. Use aggressive auto-reconnection on both platforms. These are observations from preview runtimes and may evolve.

NPU-to-GPU Fallback Chain

try:
    manager = FoundryLocalManager("phi-4-mini")  # NPU first
except Exception:
    try:
        from foundry_local.api import DeviceType
        manager = FoundryLocalManager("phi-4-mini", device=DeviceType.GPU)
    except Exception:
        # ⚠️ NOT RECOMMENDED FOR PRODUCTION - last resort only.
        # The port is dynamic; this may break if the service restarts.
        client = OpenAI(
            base_url="http://localhost:5272/v1",
            api_key="not-needed"
        )

For additional troubleshooting, see Foundry Local best practices.

Designing for the Token Budget

This is the constraint that shapes everything. Context limits vary by model. Phi Silica has a ~4K window; Phi-4 Mini supports much larger contexts, but practical token budgets still matter for latency and cost. Observed ranges: structured field extraction ~1,884 tokens, document classification ~500 tokens, morning briefing ~2,200 tokens.

Design principle: build single-shot endpoints that do one thing well. Instead of “one chatbot that does everything,” build endpoints like /extract-fields, /classify-doc, /summarize. One call, one job, one clean response.

And honestly? This constraint produces better architecture. Not every AI task needs a frontier model. Most of them are casual... summarization, extraction, classification, one-shot and done. It maps directly to the 80/20 planning model: the NPU handles the 80% that doesn’t need GPT-4.

Phi Silica: On-Device Vision

If you don’t need vision capabilities for your first app, skip this section. Start with Foundry Local + Phi-4 Mini. Come back when you need on-device image classification.

Phi Silica requires a few more setup steps than Foundry Local, but it unlocks on-device vision capabilities that no cloud-dependent workflow can match. Phi Silica is Microsoft’s on-device model accessed through the Windows AI APIs, supporting on-device language and multimodal scenarios available on Copilot+ PCs. For the full walkthrough, see Get started with Phi Silica and the Phi Silica tutorial.

Unlike Foundry Local (standard REST API), Phi Silica is a Windows API requiring: MSIX (Microsoft’s modern app packaging format) packaging with the systemAIModels restricted capability, a LAF (Limited Access Feature) token tied to your Package Family Name, and model provisioning on-device. Development builds may relax LAF enforcement; production deployments should always assume a valid token is required. See Windows AI API troubleshooting for LAF details.

Minimum Viable Checklist

☐ MSIX-packaged app with systemAIModels capability
☐ Phi Silica model readied on-device (AI Toolkit Playground or AI Dev Gallery)
☐ App checks GetReadyState() before calling vision APIs
☐ LAF token from Microsoft
☐ Health endpoint for fallback detection

The Sidecar Pattern

Encapsulate the Windows API complexity in a small C# ASP.NET Core service rather than MSIX-packaging your entire app:

Flask app (localhost:5000)  →  Vision Service (localhost:5100)  →  Phi Silica on NPU
                                      ↑
                               MSIX packaged, LAF token

The Vision Service exposes /health, /classify, /describe, /extract-text. Your primary app stays a standard Python web application.

The Three-Tier Fallback Pattern

If there’s one architecture principle to take from this entire post, it’s this: never let the app fail silently. Models will hang. Drivers will update. The NPU will occasionally just... not cooperate.

Tier	Strategy	Example: Photo Classification
Tier 1	Full AI pipeline (preferred)	Phi Silica Vision analyzes the actual image
Tier 2	Simpler AI approach (degraded but functional)	Phi-4 Mini infers from the filename
Tier 3	Hardcoded safe default (always works)	Pre-baked classification for known scenarios

Build these tiers from the start. They cost almost nothing to implement and they save everything when it matters.

Operationalizing NPU Apps in Enterprise

Foundry Local is in preview, so treat everything here as a framework that will evolve. That said, if you’re thinking about fleet deployment, these are the things that will bite you if you don’t plan for them.

Model acquisition and offline readiness. Models download on first use and cache locally (typically %LOCALAPPDATA%\.foundry\cache\models). Cache is per-user context, so plan pre-provisioning accordingly.

Update cadence. No SLA, no backward compatibility guarantee. Test in rings (dev → pilot → broad). Pin runtime versions. Revalidate after every Foundry Local or Windows update.

Logging. Track inference latency, token counts, fallback tier used, model load times. Do not log raw prompts or responses containing user data or PII (personally identifiable information).

Cloud escalation policy. Make cloud routing an explicit, auditable decision: local-by-default, cloud-only-when-invoked, with a log entry every time data leaves the device. Provide an admin toggle to disable cloud escalation entirely for sensitive environments.

Security. Foundry Local binds to localhost. Only local processes can reach the model endpoint. Don’t proxy to external interfaces without explicit security controls.

Packaging. Runtime installs via winget install Microsoft.FoundryLocal (Intune-compatible). (use --scope machine for machine-wide deployment; Intune-compatible). Stage three components: runtime, pre-cached model(s), and your application. The demo repo’s setup.ps1 validates each.

Fleet heterogeneity. If your fleet spans Intel and Qualcomm, the WMI detection pattern and three-tier fallback architecture are required, not optional. Test on both silicon families before broad deployment.

What We Built: The Surface NPU Demo App

Four tabs. Five AI tasks. Zero cloud calls in our demo. This is what a vibe-coded application looks like when it grows up.

I’ve demoed this to partner sellers, enterprise customers, and internal leadership. The moment that changes the conversation every time? Turning on airplane mode and watching it keep running. (That, and showing the tokenomics dashboard: $0.00 in cloud costs.)

Feature Details

AI Agent: governed local chat assistant powered by Phi-4 Mini through Foundry Local. Natural language queries, tool-calling, structured responses. This is where most people start.

My Day: takes local calendar, email, and task data and generates a structured morning briefing entirely on-device.

Two-Brain Router: evaluates each request and decides whether the local NPU can handle it or if it needs to escalate to a frontier cloud model. Shows the decision logic in real time, asks for explicit user consent before any data leaves the device.

Field Inspection Copilot: the multimodal showcase. Five NPU capabilities in a single workflow:

Voice: speak inspection findings, NPU transcribes and extracts structured fields (location, issue type, severity)
Camera: photograph the issue, Phi Silica classifies it on-device (water damage, structural crack, mold, equipment fault)
Pen: annotate photos with the Surface Pen, with local handwriting recognition
Report generation: NPU synthesizes voice, photos, and annotations into a formatted inspection report
Translation: one tap to translate the full report into Spanish entirely on-device

Target industries: construction, insurance claims, utilities, manufacturing QA, property management, OSHA compliance. The offline capability is load-bearing because these environments often have poor or zero connectivity.

The dashboard closes every session with the demo numbers: 5 local AI tasks, 0 cloud calls, ~520 tokens consumed, $0.00 in cloud inference costs, 0 bytes transmitted off-device.

The Code: Fork It, Build On It

github.com/frankcx1/surface-npu-demo

Clone it. Run setup.ps1. Open http://localhost:5000. It auto-detects your silicon, selects the right model, and you’re running.

Fork it and build your own use case on top of it. Add a tab for your industry workflow. Swap in a different model from the catalog. If you build something cool, submit a PR... I’ll merge it. This is a living project.

Lessons Learned

After building this across both Intel and Qualcomm devices over several months, here’s what I wish someone had told me on day one.

For IT Pros

The NPU is a production-capable inference target for supported workloads. Sustained low-watt inference for tasks that can cost pennies per call in the cloud (based on published Azure OpenAI pricing). Think about what that means for your fleet at scale.
Start with the AI Toolkit Model Catalog. Browse, test in the Playground, understand limits before committing.
Model constraints shape your architecture. Phi Silica is ~4K; Phi-4 Mini supports much larger contexts but token budget still matters for latency and cost. Design focused, single-task endpoints, not chatbots.
Cross-platform isn’t free. Intel and Qualcomm NPUs behave differently. Test on both. Use WMI. Build fallback chains.
Foundry Local is preview. No SLA. Stage updates through rings.
Airplane mode is the proof point. Turn off Wi-Fi. Kill the 5G. Run the app. That’s the demo that changes the conversation every single time.

For Vibe Coders

Start with Foundry Local + the OpenAI SDK. Fastest path to NPU inference.
Always use SDK endpoint discovery. base_url=manager.endpoint, not a hardcoded port.
Test on hardware early and often. Model hangs, context overflows, and driver quirks only surface on the actual device.
Hardcode fallbacks for everything. Not laziness. Professionalism.

What On-Device NPU Apps Are Not For

Just as important as knowing what to build... knowing what not to build. I learned some of these the hard way.

Not for model training. NPUs are inference accelerators.
Not for long-running agent loops. Small models lose coherence. Design for single-shot endpoints.
Not for unbounded conversation history. Manage state explicitly within the ~4K context window.
Not a cloud replacement. On-device handles the routine majority so your cloud budget goes to the tasks that need it.

Get Started Today

# 1. Install the runtime
winget install Microsoft.FoundryLocal

# 2. Install Python dependencies
pip install foundry-local-sdk openai flask

# 3. Clone the demo
git clone https://github.com/frankcx1/surface-npu-demo.git
cd surface-npu-demo
.\setup.ps1

# 4. Run it
python npu_demo_flask.py
# Open http://localhost:5000

# 5. Or start from scratch with your AI coding assistant:
# "Build me a Flask app that uses Foundry Local to serve
#  Phi-4 Mini on the NPU with an OpenAI-compatible API.
#  Use the SDK for endpoint discovery. Single file, HTML inline,
#  chat interface on localhost:5000."

Pro tip for vibe coders: Copy this entire post into your AI coding assistant as context. It knows the SDK patterns, the gotchas, the fallback chains. That’s the whole point.

Pick one workload this week. PII scanning. Document classification. Intake form extraction. Contract triage. Run it on the NPU, in airplane mode. Measure latency. Measure what you’d have paid in cloud inference. Build the business case from real numbers on your hardware.

I started at Silicon Graphics (SGI) and watched the introduction of the GPU up close... from rendering wireframes to reshaping entire industries. It’s wild to see how far that arc has come. Hardware has its own rise and fall and rise again, and dedicated AI silicon feels like the next big chapter. I’ve had the privilege of shipping things like Surface Hub along the way. The tools change. The builder instinct doesn’t. The difference now is that the tools meet you where you are... you don’t need to be an engineer to build something real.

Start building. Good luck out there.

Microsoft Learn References

Topic	Link
Foundry Local overview	What is Foundry Local?
Foundry Local quickstart	Get started with Foundry Local
SDK integration (Python, C#, JS)	Integrate with inference SDKs
Foundry Local architecture	Architecture and components
SDK reference	Foundry Local SDK reference
CLI reference	Foundry Local CLI reference
Windows AI APIs	What are Windows AI APIs?
Phi Silica	Get started with Phi Silica
Phi Silica tutorial	Phi Silica walkthrough
Windows AI troubleshooting	API troubleshooting
AI Toolkit for VS Code	AI Toolkit overview
Windows AI decision tree	Use local AI on Windows
Ready-to-use local LLMs	Local LLMs on Windows
Foundry Local GitHub	microsoft/Foundry-Local

Built on Surface Copilot+ PCs. Repo: github.com/frankcx1/surface-npu-demo

Beautifully invisible: The engineering intelligence behind Surface for Business displays

Jussi_Ropo — Mon, 02 Mar 2026 20:03:51 GMT

Open a Surface Copilot+ PC, and the display just feels right. Whites look clean, text is sharp, and colors stay true and consistent in varied lighting conditions. Move from a bright office to a dim café and the screen keeps pace, adjusting as the light around you changes. That sense of ease is deliberate. It comes from years of engineering designed to make the display feel natural in any setting, with work that is meant to be invisible rather than attention-grabbing. In this blog post, we’ll look at some of the innovations behind the scenes that go into delivering a visual experience that just works.

Calibrated for consistency

Every Surface display goes through individual factory calibration before it leaves production. This is not a batch process. Each panel is measured and corrected on its own. Manufacturing introduces measurable differences between panels, and those differences—if left uncorrected—show up as variations in color, gamma, or luminance. Over the lifetime of a product, those variations erode consistency.

Figure 1. Distribution of display white points before and after factory calibration, shown in CIE 1931 xy color coordinates. Blue dots represent uncorrected panels; green dots show values after calibration, and the red point marks the target. Calibration reduces wide variation into a tight cluster centered on the reference point.

Figure 2. Visualization of white point consistency across panels. Before calibration (left), color shifts appear across different panels. After calibration (right), those variations are reduced, producing a uniform gray appearance.

Figure 3. Luminance error before (blue) and after (green) calibration shows how calibration lowers the variation and makes luminance difference between the units non-noticeable.

Surface calibration configures each panel to a defined target so that all units of the same model render content identically. A spreadsheet viewed in one conference room looks the same on another device halfway across the globe. Designers, video editors, and anyone working in color-critical applications rely on that assurance. For everyone else, the value is more subtle but no less critical. Photos display with reliable skin tones. Presentations render the same across the Surface product portfolio.

The calibration data is stored directly in the hardware, so it is present from the first boot. Users never have to set up or tune the display themselves. What feels natural reflects hundreds of hours of engineering and testing, with the goal of making accuracy something people never need to notice.

Responsive to its environment

Lighting conditions vary constantly. A user may start the day in a brightly lit office, move to a client site with warm incandescent light, and finish a call from a café with mixed natural light. In each of those settings, the display must maintain visual balance.

Figure 4. Comparison of Adaptive Color (left screen in images) versus fixed D65 white point (right screen in images). In warm ambient light (left image) and daylight (right image), Adaptive Color adjusts the display white point to better match the viewing environment, while the fixed white point remains constant.

Surface devices include Adaptive Display features that utilize ambient light sensors to track the environment's light intensity and color. If lighting in a room shifts from cool LED to warm halogen, the display adapts white balance (Adaptive Color), contrast (Adaptive Contrast), and brightness (Adaptive Brightness) accordingly. These adjustments are tuned to occur gradually, so there is no visible flicker or sudden change. Transitions are invisible, but the result is a screen that always feels immersive and natural.

This responsiveness requires the entire system to be tuned to work in harmony. Sensors capture data, firmware interprets it, and Windows algorithms apply adjustments in real time. Each layer must act with precision. If the response is too slow, the user notices lag; if it is too aggressive, the shift feels distracting. Because the display is calibrated to a known standard on Surface devices, the system can deliver adjustments that remain accurate across environments. The result is a screen that feels consistent, natural, and reliable no matter where it is used.

Figure 5. Anti-reflective technology comparison. The left display demonstrates how anti-reflective coating maintains visibility and readability even under glare. The right display shows distracting reflections and reduced clarity.

Anti-reflective coating technology further supports readability in dynamic ambient light conditions. It reduces reflections from overhead lights, windows, outdoor glare, and other variables that can interfere with visibility.

Context-aware experiences

Displays also need to respond to how people work. A static chart on a slide requires different behavior than fast scrolling in a lengthy document. A video clip requires different rendering than a CAD model or a digital painting.

Surface devices offer the option of using Auto Color Management (ACM) to detect the type of content and apply proper color management automatically. With support for high bit depth—more than a billion (10-bit) colors instead of 16.7 million (8-bit) colors—ACM provides greater range and accuracy across scenarios. High Dynamic Range (HDR) extends beyond video playback to include gaming, still images, and apps using Windows Advanced Color, with results that can deliver higher color saturation and expanded luminance range. Graphics built for the sRGB pipeline are displayed faithfully without oversaturation, and mixed workflows that include images with embedded profiles are interpreted correctly. Users do not need to switch modes or adjust settings—the system applies the proper treatment under the hood.

Motion designed to match the moment

When objects move across a screen, your eyes follow them smoothly. If the pixels that represent those objects don’t update at the same pace, your brain perceives that mismatch as motion blur—a faint smear that makes edges look soft and movement feel less immediate.

Two technical factors determine how a display handles motion: refresh rate (how often the image is updated) and response time (how quickly each pixel changes from one state to another). Higher refresh rates reduce positional lag between your eyes and the screen; faster response times minimize trailing or ghosting during transitions. Both are essential for clarity in motion, but both also consume more power.

Surface devices use Dynamic Refresh Rate to balance those parameters automatically. The display can run at up to 120 Hz for inking, scrolling, or animation—keeping motion sharp and continuous—then step down to lower rates when the image is still. Combined with tuned pixel response times, this adaptive system maintains precision without unnecessary energy use.

The result is motion that feels lifelike and immediate, whether you’re sketching with a pen, moving between slides, or gaming after hours. It’s a small part of the engineering work that makes the Surface display feel effortlessly responsive.

Figure 6. Motion Blur matrix for varying refresh rates (X axis) and response times (Y axis).

Building these systems requires deep integration across hardware, software, and display panel technology. The work involves years of alignment between design teams, Windows engineers, and manufacturing partners. The foundation comes from color science and human vision research, which guides how features are designed to match the way people perceive light and color. For the user, it simply feels seamless. The complexity stays hidden, and the display feels like it is paying attention to both context and activity.

Designed for the long run

Devices live through years of use, and sometimes through repair. A display may need to be replaced after damage or failure. For many products, a repair can mean differences in color or brightness that don’t match the original. Surface engineering avoids this by storing calibration data directly in the display hardware.

When a panel is replaced, the system retrieves the embedded profile and applies it automatically. The new panel inherits the same calibration standard as the original, and the experience remains consistent. Users do not need to recalibrate or adjust. Repairs become part of the lifecycle without breaking the quality of the display.

This attention to repair reflects a philosophy of long-term value. Devices are expected to stay reliable over years of service, and the display is central to that experience. Ensuring that a repaired device feels the same as a new one is part of treating quality as a continuous commitment rather than a one-time achievement.

Innovation that extends across Windows

Surface frequently pioneers new display technologies that later become available across the Windows ecosystem. Features such as Adaptive Brightness, Adaptive Color, HDR pipelines, Auto Color Management, and dynamic refresh rates have been refined on Surface before extending to other devices.

Partnerships with display manufacturers and technology providers make this scaling possible. For example, when Dolby Vision IQ support was introduced, Surface engineers worked with Dolby to tune the entire Windows pipeline so the experience could adapt to ambient light. That work benefited all Windows devices capable of supporting the feature, not just Surface models.

Because Surface devices often include a superset of display capabilities, engineering effort goes into making sure these features work seamlessly together rather than only in isolation. By solving complex problems once and sharing the solutions, the broader ecosystem improves.

This role as a reference platform means that innovation on Surface often shapes the standard for how displays behave across Windows. The work that begins as precision engineering for one device ends up defining expectations for many.

Engineering that gets out of the way

The Surface display team sees itself in the reproduction business. Every design choice—from panel selection to firmware algorithms—is guided by one principle: content should appear as its creator intended, no matter where it is viewed. The goal isn’t to make images look “better,” but to make them true—faithful to the artistic or functional intent behind them.

Most Surface display technologies, including factory calibration, adaptive color, contrast, and brightness, are built to maintain that fidelity across environments. Whether you’re in bright daylight or under warm indoor lighting, the display adapts so what you see remains accurate to the source. Only a few deliberate exceptions, such as the optional Enhanced and Vivid color profiles, are designed to offer a more interpretive, saturated aesthetic when desired.

This philosophy defines Surface display engineering. Every layer—from optics and electronics to software integration—is tuned to make the experience predictable, trustworthy, and human-centric. For the user, all that complexity disappears. The screen simply looks right. It adapts when the environment changes, responds when tasks shift, and stays consistent over time.

That is the measure of success for the engineers who build it: technology that works so well it disappears into the background. The Surface display is designed to be a window to the real world—a transparent, accurate medium through which people see work, ideas, and creativity exactly as they were meant to be seen.

Discover it for yourself. Explore more at www.microsoft.com/surface/business.

If you’re interested in learning how to set up a Surface display for evaluation, see Set up Surface devices for SDR & HDR display measurements on Microsoft Learn.

Enhance AI Productivity with Designed for Surface Accessories

Jenn_Marescalco — Tue, 27 Jan 2026 22:29:20 GMT

In today’s workplaces, productivity thrives when technology helps people work smarter and with less friction. AI tools designed to support the way people think, create, and solve problems can help users move through tasks with greater confidence and clarity. But productivity and great AI experiences often benefit from more than compute power.

Designed for Surface (DfS) accessories provide meaningful extensibility to the Surface portfolio, enhancing work in real-world applications and quietly elevating the day‑to‑day experience in environments where devices need protection while remaining accessible and comfortable to use.

Below are a few scenarios that highlight some of the ways DfS accessories can achieve this.

Education

Pictured, left to right: JCPal Verskin Silicone Keyboard Protector (Spanish EU), STM Dux Rugged case for Surface Laptop 7th Edition (13.8"), JCPal Verskin Inclusive Keyboard Protector

Scenario:

A teacher walks between desks as Copilot summarizes next week’s lesson plan.
Students join a hybrid class, relying on inking, real‑time captions in Teams, and translation to keep up.
A principal catches a moment before dismissal to summarize a full day of meetings using AI.

All of this can happen when the devices in the room are charged and ready. Shared Surface Pros stay charged and organized in an AVerCharge C36i+ cart, so no one loses valuable class time hunting for power.

When backpacks get tossed in lockers or onto floors, STM’s Dux Rugged cases available for both the Surface Laptop 13” and Surface Laptop 13.8” absorb the impact and keep learning on track. And when students type in multiple languages, or need clearer visibility, JCPal’s VerSkin multi-lingual and accessibility‑focused keyboard covers help them participate more fully in class through AI‑supported writing and reading.

Teachers can easily attach and detach Kensington MagPro privacy screens to promote confidential testing environments.

These represent just a few of the intentionally designed DfS accessories to support learning, minimize interruptions, and increase inclusivity.

Frontline Retail

Pictured, left to right: MobileDemand Rugged xCase for Surface Pro with Magtek iDynamo, The Joy Factory Elevate II Countertop Kiosk for Surface Pro (White)

Scenario:

A manager uses Copilot to analyze weekly sales, prioritize restocking, and plan future orders based on seasonal shopping trends.
An associate uses a Surface Pro to pull up product details and show customers side‑by‑side options, helping them make quick decisions during busy moments.

Retail spaces are fast-paced and dynamic. Store employees can improve customer experience and reduce the time needed to address customer questions by tapping into Copilot to find the right product details, inventory availability, and more—within seconds.

During a rush, a retail associate can direct customers to self-checkout kiosks on a Surface Pro, securely mounted in The Joy Factory Elevate II enclosures, which can be placed anywhere with a variety of mounting options.

A manager can use Copilot to quickly identify inventory trends on their Surface Pro before moving to provide floor support, answering customer questions and taking payments to clear a long queue with their MobileDemand Rugged xCase in hand.

On a busy day, a Copilot+ PC—driven by powerful processors and all-day battery life and supported by DfS accessories—can help provide dependability in an ecosystem built for motion.

Information Workers & Power Users

Pictured, left to right: PanzerGlass Screen Protector for Surface Pro (Privacy), UAG Plyo Series Case for Surface Laptop (13")

Scenario:

A knowledge worker spends the morning reviewing documents with AI-generated summaries, then heads to a client site and continues refining content on the go.
Another teammate catches up on Copilot-summarized action items from a meeting, then jumps into a deep focus sprint.

Workflows feel natural when the setup supports them. A Kensington Elevated Stand raises the screen to a comfortable height for long hours of work. Sensitive content stays private in open offices or airport lounges thanks to PanzerGlass privacy screens. When work spans multiple locations, the UAG Plyo cases available for both Surface Pro 12” and Surface Laptop 13” keep devices protected without adding bulk, making it easy to carry Surface-powered productivity anywhere.

When the physical experience is comfortable, secure, and uninterrupted, AI becomes something people lean on effortlessly — not a feature they have to think about.

Your Everyday Support

Today’s workflow is becoming more streamlined and efficient. AI can accelerate work, sharpen focus, and free people from repetitive tasks, but only when the devices they depend on stay powered, protected, and ready for action.

The right Designed for Surface accessories make Surface more accessible and reliable in the real world, unlocking new functionalities. Together, they help people get more done, wherever and however their work happens.

Explore the full catalog of 200+ Designed for Surface accessories and see how they transform productivity by visiting DesignedforSurface.com.

Elevate teaching and learning with AI-powered experiences on Surface Copilot+ PCs

Jeanine_Park — Wed, 21 Jan 2026 19:25:55 GMT

Surface is a premium endpoint, designed and built by Microsoft to run Microsoft technology. When it comes to the classroom, Surface Copilot+ PCs bring the best of Microsoft—hardware, Windows, Microsoft 365¹, and Microsoft 365 Copilot¹—into one teaching device, delivering intelligent experiences more securely on‑device and in the cloud. For educators, this means every lesson and interaction is powered by a device purpose-built for teaching and learning in the digital era.

Why Surface for Education?

Surface Copilot+ PCs, combined with Windows 11, give teachers a powerful platform designed to simplify teaching and elevate learning. With lightning-fast performance, educators can create engaging lessons, generate content, and personalize instruction. Windows 11 features like Snap Layouts, Click to Do², and Copilot Voice streamline multitasking and lesson prep, while intuitive touch, pen³, and voice input make teaching feel natural. Together, Surface and Windows 11 help deliver a more secure, AI-supported solution that can save time, support creativity, and help teachers focus on what matters most—students.

Engage students with AI-enhanced learning

Picture a classroom where every student is actively engaged, their curiosity sparked by lesson plans and quizzes thoughtfully designed by teachers with the help of AI. Microsoft Learning Zone, included with all Microsoft Education licenses at no extra cost⁴, is an AI-powered learning app for Windows 11 designed to help educators create engaging lessons. The app’s AI powered lesson creation feature is designed specifically for Copilot+ PCs. Thanks to the Copilot+ PC’s built-in Neural Processing Unit (NPU), these devices offer fast, reliable performance by running AI models directly on the device and combining them with cloud-based capabilities when needed. This hybrid approach helps Microsoft Learning Zone generate lessons quickly and keeps the experience smooth, secure, and ready for classroom use. It also helps educators streamline lesson planning with interactive activities, instant feedback, and personalized learning pathways. For example, teachers can use Microsoft Learning Zone to develop Kahoot! quizzes for a whole class or to prepare individualized learning experiences like personalized practice questions based on recent student performance, while keeping student data more secure and private.

Surface Copilot+ PCs can also help teachers use AI in context to streamline lesson prep and administrative tasks, so they can spend less time on administration and more time inspiring students. For example, teachers can engage with Copilot in a single click using the Copilot key⁵ on a Surface keyboard or by saying “Hey Copilot” out loud. And using pen, touch, and voice commands in conjunction with Teach in Microsoft 365 Copilot⁶ running on Surface, teachers have a central hub for generating lesson plans, quizzes, rubrics, flashcards, feedback, and more. They can transform ideas and research into engaging lectures in moments, tailor instruction to meet the needs of every learner, and connect with colleagues to share best practices.

Recently, we also announced the Microsoft Elevate for Educators skilling program along with more AI-powered experiences purpose-built for education, including the Study and Learn agents in Microsoft 365 Copilot, and Study Guide. Microsoft Elevate helps equip educators with the AI skills they need for the classroom of the future. Delivered through platforms like Microsoft Learn and Minecraft Education, these flexible learning paths ensure that educators can build AI fluency at their own pace, whether they're just beginning their journey or advancing to specialized applications. Read more about Microsoft Elevate and other AI tools for education here.

In classrooms where both teachers and students are using Surface Copilot+ PCs, Live Captions⁷ with on-device automatic translation can help make spoken content accessible to all students, including students with hearing impairments. The NPU transcribes and translates audio in real time, supporting 40+ languages into English, all processed on-device versus the cloud.

Ideally with Surface Copilot+ PCs and Microsoft’s AI-powered tools, technology fades into the background in the classroom, helping teacher creativity and connection take center stage and enabling student learning to be more dynamic, inclusive, and impactful.

Empower the classroom of the future, today

Surface Copilot+ PCs, purpose-built by Microsoft, are designed to be the foundation for today’s classrooms and the launchpad for tomorrow’s AI innovations. With Windows evolving as the canvas for intelligent AI and agents, Surface devices and Windows together form an essential, AI-assisted platform for educators.

Now, every teacher can activate Copilot agents⁸ directly on their Surface device to act as a digital teaching partner. These agents can adapt to each teacher’s unique style, streamline daily routines, and unlock new possibilities for student learning. Building agents is simple: teachers or IT can use ready-made templates or create custom agents using natural language, all within the familiar Surface and Windows environment.

Surface’s intuitive hardware—touchscreen, pen, voice, and the dedicated Copilot key—makes accessing AI support effortless. Teachers can get immediate answers to classroom questions, troubleshoot tech issues, or navigate school resources using natural input methods. By combining Copilot’s intelligent capabilities with Surface’s secure hardware, educators can gain a more personalized, efficient, and protected teaching experience ready for the future of learning.

In addition, Surface Copilot+ PCs help support the full range of learning needs by delivering the performance and experience required for the education tools students and educators depend on every day. Surface devices are designed to work with common education apps like TestNav for assessments, Minecraft Education for STEM, Adobe Express for creativity, and assistive technologies such as JAWS.

And, going forward, the built-in NPU on Copilot+ PCs like Surface enables Microsoft and other educational software providers to develop innovative new AI experiences that can run on the device, in the cloud, or both.

Boost productivity and collaboration

In the classroom, Surface Copilot+ PCs can become the teaching command center: always ready, always responsive. With a simple voice command, Copilot Voice and improved Windows Search⁹ instantly pull up lesson plans, student materials, or answers to unexpected questions, freeing instructors from frantic searches and giving back precious prep time.

Collaborating on Surface is intuitive and efficient. Teachers can quickly save lesson materials in Teams or OneDrive¹ and share them with students for interactive feedback. Whether teachers are leading a lively discussion in person, connecting with students remotely, or conferencing with colleagues via video, Windows Studio Effects on Copilot+ PCs ensure they’re always seen and heard clearly. Subtle features like background blur, eye contact, and automatic framing help maintain a professional presence, so the focus stays on interacting with students or other teachers—not on the tech.

And Surface Copilot+ PCs are designed to empower mobility in and outside the classroom. With extended battery life and lightweight devices, teachers are no longer tethered to a desk or a charger. They can move about freely, interact with students, project and present seamlessly, and focus on teaching. For example, on a Surface Pro with Surface Pen inking, Dual Studio Mics, and natural language prompts in Copilot, teachers can annotate readings, capture ideas by voice, and generate lesson materials on the fly—without breaking the flow of instruction.

Throughout the day, Surface Copilot+ PCs can also help teachers anticipate what’s next. Context-aware Windows Search doesn’t just find files—it suggests smart next steps, like opening a document in Word or sharing it with a colleague, streamlining workflows. When inspiration for a lesson strikes, Click to Do lets teachers quickly summarize, explain, or create new content on the fly, helping them build engaging lectures and materials in real time. Surface’s vibrant touchscreen and Snap Layouts can help keep resources organized and visible, supporting a productive work experience.

And, most importantly, Surface devices help safeguard faculty, staff, students, and sensitive school data with advanced security and remote management features¹. As innovations advance in AI, Microsoft and Surface provide built-in protection at every layer—hardware, firmware, operating system, cloud, software applications, and identity.

Surface Copilot+ PCs are more than just devices—they’re partners in teaching, learning, and innovation. By combining Microsoft’s advanced hardware, intuitive software, and powerful AI, Surface empowers educators to engage students, boost productivity, and modernize their classrooms, all while keeping data more secure and private.

Visit Surface.com/Business to learn more.

Students, parents and educators can save up to 10% on select Surface devices and more at the Microsoft Store.¹⁰

Disclaimers:

Sold separately. Software license required for some features.
Click to Do. Copilot+ PC feature. Image actions now available across devices; other actions vary by device, region, language, and character sets. Subscription required for some actions. Learn more.
Surface Pen sold separately. Surface Slim Pen (2nd Edition) experiences and compatibility vary by which Surface device you are using it with. Visit Surface Slim Pen Compatibility to learn more.
Microsoft Learning Zone requires a Microsoft 365 Education Essentials, Core (A3), or Advanced (A5) license. Microsoft Education licenses.
Copilot key feature availability varies by market, see aka.ms/keysupport.
This feature is only available to Faculty/Staff with a Microsoft 365 for Education license. Teach in the Microsoft 365 Copilot App.
Copilot+ PC feature. Live Captions translates video and audio subtitles into English from 40+ languages and from 25+ languages into Chinese (Simplified). See Copilot+ PC FAQs.
Copilot with commercial data protection is available at no additional cost for users with an Entra ID with an enabled, eligible Microsoft 365 license. Copilot for Microsoft 365 sold separately and requires a qualifying volume license or subscription - Microsoft Copilot for Microsoft 365 | Microsoft 365. Minimum age limits apply to use of Copilot and certain AI features. Details.
Copilot+ PC feature. Improved Windows search works with specific text, image, and document formats only; optimized for select languages (English, Chinese (Simplified), French, German, Japanese, and Spanish). See Copilot+ PC FAQs .
Microsoft Store Education discount is available to K-12 and higher education students, faculty and parents. Education discount only valid on select products, and may not be combinable with other offers. See terms and conditions at Education & Student Discounts on Laptops, Microsoft 365, Windows, Surface | Microsoft Store

ICYMI: Enabling AI Fluency in 2026 with Surface Copilot+ PCs

Chauncey_Larsen — Wed, 14 Jan 2026 01:06:02 GMT

Welcome to 2026.

In case you missed it, Sandra Andrews, Global GM of Surface Marketing, recently posted an article detailing ways businesses and Frontier Firms can enable AI fluency using Surface Copilot+ PCs. Head over to LinkedIn to read the full post:

Enabling AI Fluency in 2026: How Surface helps organizations become Frontier Firms

Also, be sure to follow Microsoft Surface on LinkedIn for more updates: Microsoft Surface | LinkedIn

Stay tuned and keep exploring what's possible!

Meeting Control, Now Within Reach: Surface Hub 3 + MAXHUB Universal Console

FrankBuchholz — Tue, 13 Jan 2026 21:09:08 GMT

Modern meeting spaces require flexibility, simplicity, and consistency for IT teams managing collaboration environments. Announced at Microsoft Ignite 2024, center-of-table console support for Surface Hub 3 extends Microsoft Teams Rooms on Windows by enabling certified third-party touch consoles for in-room meeting control.

Center-of-Table Console Support

Surface Hub 3 now supports Teams Rooms Certified Universal Consoles, introducing an additional option to control meetings beyond the interactive display. This includes the MAXHUB TCP33T Universal Console, a certified hardware solution in this ecosystem. By connecting a touch console directly to Surface Hub 3, users can join meetings, manage controls, and share wired content from their PCs while seated at the table.

Benefits of Certified Universal Consoles

Teams Rooms Certified Universal Consoles can help provide IT admins with:

Microsoft Teams Rooms integration through certified accessories
Flexible room design options including front-of-room deployments
Consistent user experience across meeting spaces
Simplified meeting controls for table-based interaction

MAXHUB TCP33T Universal Console Overview

The MAXHUB TCP33T is a Teams Rooms Certified Universal Console designed to work with Windows-based touch board devices such as Surface Hub 3. It delivers touchscreen control for Microsoft Teams Rooms meetings and serves as a dedicated entry point for wired content sharing.

Common Deployment Scenarios

Large conference rooms requiring table-based control
Standardized Teams Rooms deployments across buildings
Collaborative meetings requiring easy content sharing

Requirements

Deployments require Surface Hub 3 running Microsoft Teams Rooms on Windows and a Teams Rooms Certified Universal Console such as the MAXHUB TCP33T.

Looking Ahead

This new Universal Console ecosystem reflects Microsoft's commitment to flexible, scalable collaboration experiences. By pairing Surface Hub 3 with certified accessories like the MAXHUB TCP33T, organizations can design meeting spaces that meet modern collaboration needs.

Live Webinar Wednesday the 14th of January... Sign up now!

Join us for an exclusive webinar with Microsoft and MAXHUB as we explore how the MAXHUB Universal Console enhances the Microsoft Surface Hub experience.

Hear from industry experts and learn how to:
✔ Reduce friction in the room
✔ Streamline collaboration workflows
✔ Centralize meeting controls — without leaving your seat!

Featured Speakers:
• Frank Buchholz, Director, Product Marketing — Microsoft
• Jean Barrett, Technology Solutions Professional — Microsoft
• Alan Nicholls, Microsoft Teams Professional — MAXHUB

Register for a session and secure your spot👇

January 14 @9AM PST session: Register here
January 14 @5PM PST session: Register here

Resources

Close the Year Strong with Surface for Business Deals

Jeanine_Park — Mon, 15 Dec 2025 18:40:16 GMT

As organizations look to maximize their remaining budget and prepare for 2026, now is the moment to modernize device fleets with Surface for Business. These limited-time Surface promotions make it easier to accelerate refresh cycles, strengthen endpoint security, and equip employees with devices that are AI-ready from day one.

Surface for Business devices combine productivity-forward design, leading AI capabilities, and Microsoft security at multiple layers. Whether refreshing a subset of users or upgrading entire departments, organizations can close the year with hardware that helps reduce risk, assists in lowering management overhead, and positions teams for the next wave of AI-driven productivity.

Secure by Design

Surface for Business devices deliver hardware-based protections aligned with Secured-core PC standards. Hardware-based security, advanced firmware protections, and a growing number of memory-safe drivers help reduce exposure across the stack, providing peace of mind that clears the way for AI innovation.

AI-Ready

With advanced processors including powerful AI chips on supported models, Surface for Business devices are ready to help employees maximize their skills using AI to drive business forward. From a dedicated Copilot key¹ to Foundry on Windows² for developing local agents, these devices provide the foundation for people to achieve their best. Learn more about unlocking AI innovation in our new eBook.

Ready to Deploy

Surface for Business devices support Windows Autopilot³, enabling IT teams to deploy devices directly to employees, preconfigured with corporate profiles and security baselines, without imaging or desk-side setup. Combined with centralized management through Microsoft Intune⁴, organizations can reduce deployment time and help keep endpoints consistent from day one.

Make the Most of Year-End Purchasing Opportunities

Maximize remaining 2025 budget by exploring end-of-year savings on select Surface for Business devices. Work with your preferred reseller to capitalize on year-end spend, or purchase directly through Microsoft Store in the US⁵ to take advantage of available offers that make modernizing your device fleet easier as you prepare for 2026.

Resellers can help organizations align device selection, deployment plans, and support needs while optimizing budget utilization. Businesses purchasing through Microsoft Store benefit from fast, free shipping and a 60-day return window on most physical products.⁶

Across both channels, Surface for Business offers provide a cost-effective path to refresh devices now rather than deferring upgrades—helping IT leaders complete their roadmap, meet procurement targets, and deliver new value to end users before the new year.

Find a reseller [https://www.microsoft.com/surface/business/where-to-buy-microsoft-surface

Buy from Microsoft Store US [https://www.microsoft.com/en-us/store/collections/surface-deals-bundles]

References

Feature availability varies by device and market. See Key Support for details.
Some capabilities may require additional subscriptions not included with Windows or Surface devices.
Windows Autopilot device preparation depends on specific capabilities available in Windows client and Microsoft Entra ID. It also requires a mobile device management (MDM) service such as Microsoft Intune. These capabilities can be obtained through various editions and subscription programs.
Additional licenses required, not included with Surface.
Offers and promotions vary by market.
Terms apply. Microsoft Store only ships to certain countries; see Shipping options, costs, and delivery times - Microsoft Support for details.

Improved address management in service orders on Surface Portals

shivangisahu — Mon, 08 Dec 2025 21:42:59 GMT

We’ve introduced an important usability improvement to the address selection experience in the service order workflow on both Surface Management Portal and Surface Support Portal.

When raising a service order, users can add both the billing and shipping addresses and save them for future use. Previously, all saved addresses were stored together and appeared in both dropdown menus. This caused confusion and made it difficult for users to select the correct one.

To improve this experience, we’ve separated saved addresses by type. Shipping addresses now appear only in the Shipping Address dropdown, and billing addresses appear only in the Billing Address dropdown.

As part of this update, all previously saved addresses have been moved to the Shipping Address section. Users can now save billing addresses separately as they create new orders.

This change makes the selection process simpler, clearer, and more intuitive, allowing users to easily select the right address.

To learn more about the Surface Management Portal and Surface Support Portal, see the following Microsoft Learn articles:

Making the everyday easier: Behind the scenes with the Surface Pro 12-Inch Keyboard

Chauncey_Larsen — Tue, 02 Dec 2025 17:25:24 GMT

Everyday barriers in plain sight

Most people don’t spend much time thinking about their keyboard. That’s part of what makes it work. You open your device, start typing, and the keyboard fades into the background—until it doesn’t. Until the lighting changes, or your eyes are tired, or you can’t quite tell which key your finger is on. For millions of users, that slight friction isn’t just annoying—it’s a daily barrier.

A more visible experience

The new Surface Pro 12-inch keyboard features thoughtful changes designed to make typing easier for more people. It started with a simple observation: the key legends were hard to see. That insight led to exploration of overlays used in education, typefaces developed for low vision and dyslexia, and the effects of lighting, spacing, and iconography on legibility.

Through rounds of prototypes and refinements, the design team shaped characters, adjusted stroke weights, and tuned backlighting to avoid visual washout—all while keeping the familiar Surface feel.

The result is the optional Bold keyset: a high-contrast, larger-font version of the standard keyboard. Letters are clearer, spacing more deliberate, and labels that once faded into the keycaps now stand out with clarity. These changes quietly reduce effort, one keystroke at a time.

Top-down view of the Surface Pro 12-inch Bold keyset

Designed for wayfinding

We also looked at how people navigate the keyboard by touch. For users who are blind or who rely on tactile orientation, the standard F and J bumps are helpful—but limited. The raised indicators on the F4 and F8 keys that became standard with Surface Laptop 3 and Surface Pro 8 keyboards are also used on the Surface Pro 12-inch keyboard. These positions are intentionally chosen: many common keyboard accessories leave these keys uncovered, making them valuable landmarks.

We also included a tactile bump on the down arrow key. For users who navigate interfaces using screen readers, distinguishing up from down by feel is critical. This subtle addition reduces error, speeds up interaction, and supports confidence in every movement.

Adapting to different inputs

Another shift is adaptive touch mode, built directly into the Surface touchpad and easily toggled on through the Surface app. For many people with limb differences, Cerebral Palsy, or mobility conditions such as arthritis, standard touchpads can be difficult or impossible to use. Adaptive touch mode changes that.

Adaptive touch mode customizable settings

When active, it allows users to adjust how the touchpad responds to their input—whether from a fingertip, palm, edge of the hand, foot, or residual limb. Users can also fine-tune settings such as touch sensitivity, the time between clicks for a double-click to register, and the size or location of the right-click region.

The result is a touch surface that adapts to the person, not the other way around. For people with limited mobility or a wide range of dexterity capabilities, that flexibility turns the touchpad into a customizable, comfortable, and precise tool for daily computing.

Faster access to AI assistance

The keyboard also includes a dedicated Copilot key. One press brings up Microsoft Copilot in Windows 11, giving users immediate access to AI-powered assistance. That could mean summarizing a document, rewriting an email, answering a question, or navigating the system itself. For users with cognitive load limitations, memory challenges, or motor delays, this shortcut eliminates several steps—replacing multi-step workflows with a single action.

Close-up view of the Copilot Key on the Surface Pro 12-inch keyboard

No extra cost, no added steps

We made a deliberate decision not to make accessibility a premium option, so these updates don’t come with an added cost. The Bold keyset version is priced the same as the standard Surface Pro 12-inch Keyboard and is available in English only, in select markets, including the US, Canada, and China.

The built-in features mean that technology decision makers don’t have to choose between cost and comfort. Users don’t have to identify as needing something different. And no one has to explain why they want a keyboard that’s easier to read or more comfortable to touch.

The value of quiet inclusion

This is the kind of work we value most. Not chasing a trend or shipping something flashy—but solving a real problem that someone flagged because their experience didn’t feel as seamless as it should. The Surface Pro 12-inch keyboard with Bold keyset isn’t a new category. It’s a better version of something you already know.

It shows up quietly. It gets out of the way. It supports more people without asking anyone to justify their needs.

That’s what inclusive design can be. Thoughtful. Uncomplicated. Built into the core of the product from the start.

And when it works, most people won’t even notice. They’ll just keep typing.

Try our latest Surface Keyboards with the Bold keyset and discover how thoughtful design can make your everyday work easier. Visit the Microsoft Store to explore the difference in visibility, comfort, and accessibility for yourself. Enterprise customers can visit the Enterprise customers can get accessibility support here.

Surface Highlights at Microsoft Ignite 2025

Andrea_Director — Tue, 11 Nov 2025 14:00:00 GMT

Microsoft Ignite is a premier event designed to help attendees grow their skills, build connections, and discover emerging technologies. It offers a variety of learning experiences, including keynotes, breakout sessions, labs, and community activities. This year, Microsoft Ignite will be hosted at the Moscone Center in San Francisco from November 18–21, 2025.

Join us to explore how Surface supports AI-powered workflows through immersive experiences, hands-on labs, and meaningful community engagement.

Must-See Experiences

Great photo opportunity with a GIANT Surface!

Giant Surface Photo Opportunity

Capture a memorable moment with the Giant Surface installation, featuring custom backgrounds designed for attendees. This visual centerpiece offers a fun and engaging photo experience.

Get hands-on with the latest hybrid AI and Copilot+ PC experiences from Microsoft and our partners!

Microsoft Company Store and Surface Device Bar

Interact with the latest Surface devices and accessories. Attendees can explore Copilot+ PC capabilities, preview new hardware, and speak with Surface experts during live demos and Q&A sessions. All featured products will be available for hands-on exploration.

Be sure to gear up at the Microsoft Company Store. Stop by to find exclusive Microsoft apparel and accessories, plus save 15% on select Surface Copilot+ PCs during the event.

Discover key highlights of our Surface Lab Tour brought to you by engineers and experts

Surface Lab Tour

Take a guided walkthrough of a mobile version of our Surface Lab Tour, located adjacent to the Giant Surface activation. This attendee-friendly experience highlights key Surface engineering processes and quality testing. Learn how Surface devices are designed with reliability and performance in mind. The Lab Tour is part of the Surface Device Bar, which also features Copilot+ PC demos and the newest Surface hardware – presented by Surface engineering and marketing team members.

Learning and hands-on skilling opportunities

Community Space & MVP Engagement

Join open-table discussions on topics such as Hybrid AI and connect with Surface MVPs who are contributing to breakout session visibility and community engagement.

COM1052: Hybrid AI with Surface, Copilot+ PCs & Windows AI Foundry – Nov 19 | 10:00 AM - 10:45 AM PST
COM1131: Path to MVP: Insights from the Windows & Devices and Intune teams – Nov 18 | 4:00 PM - 4:30 PM PST

Explore Surface topics like design, security and input innovation in our Breakout Sessions

Breakout Sessions & Labs

Surface-led Breakouts

BRK301: Making AI easier with Surface Copilot+ PCs and natural input – Nov 20 | 3:30 PM - 4:15 PM PST

BRK337: Innovating Surface: Designing for product excellence – Nov 18 | 2:30 PM - 3:15 PM PST

BRK338: Advancing Windows device security through Surface innovation – Nov 19 | 11:30 AM - 12:15 PM PST

Hands-on Labs with Surface Copilot+ PCs (in-person only)

LAB584: Integrating Local AI with Windows ML – Offered multiple times

LAB585: Supercharge your WPF Apps with Local AI – Offered multiple times

Join us at Microsoft Ignite – online or in person – and share your experiences by tagging #SurfaceforBusiness. We can’t wait to see your highlights.

Back to College Essentials – DfS Accessories That Power Productivity

Carly_Hamilton — Thu, 30 Oct 2025 16:54:01 GMT

For more than 11 years, the Designed for Surface (DfS) team has worked with strategic partners to offer solutions that can extend the Surface experience for diverse scenarios.

As the next school year begins, new Designed for Surface accessories have launched alongside the latest Surface Pro 12-inch and the Surface Laptop 13-inch. These accessories have been designed with a variety of solutions in mind, in part to support student and educator workflow from anywhere. Developed intentionally to extend the usability of Copilot+ PCs into specialized environments, Designed for Surface accessories empower AI-driven learning experiences, whether you’re at a desk or on the go. Designed for Surface accessories are tested with Surface devices and certified to ensure customers have peace of mind that their accessories meet the real demands of education and hybrid work environments. Learn more about the latest Designed for Surface accessories below!

STM Dux Rugged Case for Surface Laptop

The STM Dux Laptop case is great for students who prioritize reliable protection with style. The Dux case combines rugged durability with a slim, ergonomic profile that’s easy to carry between classes and around campus. It features a transparent back panel, which allows the Surface laptop to shine through (and simplifies viewing asset tags) while its textured rubber feet prevent slipping on smooth surfaces. With its open hinge design and optimal airflow, your laptop stays cool even during long lectures.

Lightweight, tough, and great for campus life

UAG Scout for Surface Pro, 12-inch

The UAG Scout case for Surface Pro 12-inch is lightweight, tough, and great for campus life. Built with military-grade drop protection, it features a durable shell, impact-resistant bumpers, and a secure hand strap for easy one-handed use on the go. The non-slip grip keeps your device safe, while the open design supports full kickstand functionality and keyboard. A recessed holder for your Surface Slim Pen keeps your Pen secure and charging, and the case can withstand anti-microbial wipe down.

dbrand skins offer a personalized look

dbrand Skins for Surface Laptop and Surface Pro

College students and educators heading into the new school year need gear that works hard and looks professional. dbrands skins for Surface Pro and Surface Laptop deliver both. These skins are ultra-slim wraps that conform to the device’s shape and offer scratch protection with minimal bulk. When it’s time to swap styles, the skin peels off cleanly without any residue. Available in a variety of designs, colors and textures, dbrand skins offer a personalized look for any style.

Crystal clear, shock-resistant, and made with recycled glass

PanzerGlass® Screen Protector for Microsoft Surface Pro and Surface Laptop

Students and educators are always on the move with their Surface devices, making them susceptible to bumps, drops and scratches. With the PanzerGlass Screen Protector, you can move confidently knowing that your Surface screen is safe. The PanzerGlass screen protector, designed specifically for your Surface device, is made with recycled glass and offers crystal clear, shock-resistant tempered glass that preserves your device’s full functionality. For added privacy, PanzerGlass offers privacy screen protectors to ensure that the content on your screen is virtually invisible to anyone except you.

For students and educators who spend hours on Teams

Kensington H3005 Bluetooth® Over-Ear Headset

The Kensington H3005 Bluetooth® headset is made with students and educators in mind, perfect for Teams calls or Zoom classes. The wireless Kensington headset provides an immersive and focused experience and offers ergonomic over-ear swivel earcups for all-day comfort. To simplify transitions, users have access to music controls with call detection, and LED indicators confirm call status, allowing students and educators to stay in their productivity flow with minimal interruptions. The Kensington H3005 headset also includes AI-powered environmental noise-canceling microphones that suppress distracting sounds making it easier for students to work even in the busiest environment.

A webcam to ensure you’re seen and heard clearly

Kensington W2005 Auto Focus Webcam DFS

For students and educators who spend hours on Microsoft Teams, the Kensington W2005 webcam is designed to deliver sharp visuals, clear audio, and a seamless plug-and-play experience. Optimized for Surface devices, the W2005 webcam offers 1080p auto-focus resolution at 30 fps, 2x zoom, and low-light support. Whether you're teaching, presenting or dialing in for classes, the W2005 webcam makes sure you’re seen and heard clearly.

As students and educators settle into the rhythm of the new school year, having the right accessories can make all the difference. The Designed for Surface accessories highlighted offer practical, well-built solutions that support learning and teaching. Whether it’s protecting your Surface devices with rugged cases, adding a personal touch to your device with skins, or improving virtual collaboration with headsets and webcams, these accessories are available and ready to extend the value of your Surface device.

Explore the full lineup of accessories to support your Surface on the Designed for Surface website.

Endpoints and AI strategy: Lessons of the Microsoft Work Trend Index 2025

Chauncey_Larsen — Fri, 24 Oct 2025 00:09:43 GMT

Each year, the Microsoft Work Trend Index brings together one of the most comprehensive views of how work is changing. The 2025 report draws on survey data from 31,000 people across 31 countries, LinkedIn labor market insights, and trillions of Microsoft 365 productivity signals, combined with interviews with business leaders, economists, and AI experts. Its findings shape how organizations think about talent, technology, and operations, and illuminate the central role of Windows 11 and modern endpoints in enabling this shift.

This year’s report makes it clear that when it comes to AI, many companies are moving from experimentation to broader adoption. Results show that 82 percent of leaders expect AI agents to expand workforce capacity within the next 18 months, and organizations are already redesigning workflows to take advantage of them. Much of this innovation will be powered by the cloud, but the PC has a critical role in ensuring those AI experiences are fast, seamless, and secure. AI-native devices, such as Surface Copilot+ PCs, extend the value of cloud platforms by providing local AI processing, various connectivity options, and enterprise-grade security at the point of work.

Why AI-enabled endpoints matter to Frontier Firms

The Index describes the Frontier Firm as blending machine intelligence with human judgment to operate with agility, scale rapidly, and generate value faster. These organizations are moving beyond adding AI to existing processes and are rethinking workflows from the ground up. That shift creates new demands on endpoints. Devices are now where cloud intelligence, local processing, and user context converge, enabling the hybrid AI experiences the Index points to as the future of work.

Three aspects of AI adoption where the endpoint really matters

Responsiveness: The Index notes that employees are interrupted an average of 275 times a day, and that context switching undermines productivity. If an AI workflow slows due to latency or poor connectivity, or if interacting with AI feels unnatural, adoption suffers. Hybrid AI execution—running models locally, in the cloud, or in combination—helps avoid these pitfalls. Local inference allows AI to operate smoothly even in low-connectivity and offline environments and enables sensitive data to be processed without leaving the device. Developers can also take advantage of tools like Windows AI Foundry to build and optimize on-device AI experiences tailored for Surface Copilot+ PCs.

Options such as high-quality 5G connectivity, available on devices like Surface Laptop 5G for Business, increase the ability of employees to rely on cloud-based tools. The cloud provides scale, access to shared context, and continuous model improvement. Together, cloud and on-device AI create a single, seamless experience that can keep pace with the fragmented reality of modern work.

Ease of interaction: The Index emphasizes that employees want AI to fit into the rhythm of their work, not disrupt it. Device design directly influences that fit. High-quality microphones and cameras improve multimodal interactions like voice input and transcription.

Adaptive displays make visual AI tools easier to use across environments, with finely tuned color calibration and high-contrast technology that keep information accurate and legible in any setting. High-resolution PixelSense™ displays enable visual fidelity for design, data, and multimedia work, while features like adaptive color and contrast automatically adjust to ambient light.

Combined with input methods such as touch and pen, these design choices reduce friction when working with spatial or visual information. These capabilities, built into Surface Copilot+ PCs, support the type of thought-partner relationship with AI that the Index identifies as key to getting the highest-quality results.

Trust: As AI agents take on system-level tasks and handle sensitive business data, the endpoint becomes an integral part of the organization’s security perimeter. The Index projects that AI will increasingly run core processes, from customer service to product development, which raises the stakes for device-level protections.

Hardware-based identity protection, safeguards against firmware-level attacks, and continuous monitoring help enforce a Zero Trust approach. Surface Copilot+ PCs meet Secured-core PC standards, with protection that reaches down to the firmware layer, and run Windows 11. Windows Hello ensures that only an authorized user can access the device, while memory-safe drivers built with Rust improve resilience at the software level.

This security foundation extends to management. IT teams can use the Surface Management Portal—now with integrated access to Microsoft Security Copilot—for unified visibility into their device fleet. With natural language prompts, admins can act on live insights, resolve issues faster, and strengthen endpoint protection within the same trusted environment they already use. Together, these measures maintain the informed trust the Index identifies as the foundation of effective human–agent collaboration.

Now is the moment to leap ahead

The Index’s Frontier Firms are already benefiting from this approach. They are deploying AI organization-wide, using agents across functions, and seeing measurable gains in capacity and innovation. Planning now for AI-native endpoints—devices that support hybrid AI workloads, enable intuitive interaction, and are designed for modern security needs—positions organizations to perform at that level.

Surface Copilot+ PCs combine local AI acceleration, modern connectivity, and enterprise-grade security, helping deliver AI capabilities in a way that is responsive, reliable, and trusted across the workforce.

In today’s AI-enabled workplace, the PC’s role is expanding. It is not only a tool for accessing cloud services, but also an active participant in delivering them—processing workloads locally, securing sensitive interactions, and shaping how employees experience AI in the moment. Aligning endpoint strategy with AI strategy is one potential way to capture the opportunities the Work Trend Index describes. Learn more at Surface.com/business

Helping to enable secure, connected work: Surface with built-in 5G on the Verizon network

Jeanine_Park — Tue, 21 Oct 2025 19:34:46 GMT

This blog is cowritten with the Verizon Business team. Visit Connected Laptops: LTE & 5G Business Laptops | Verizon to learn more.

Consistent connectivity is foundational for accessing cloud insights and collaboration. For organizations operating in hybrid, field-based, or distributed environments, it is a prerequisite for productivity. Laptops without consistent broadband access limit the effectiveness of modern tools and the flow of work. Surface for Business devices with 5G support address this challenge directly. They provide security, manageability, and performance designed to support how work happens now. When combined with the Verizon 5G network, employees can enjoy broad coverage to keep work flowing.

Surface Copilot+ PCs represent the next evolution of the enterprise endpoint. These devices are optimized for AI workloads with neural processing units (NPUs) delivering 40+ TOPS for on-device AI processing and contributing to extended battery life.¹ With the addition of 5G on devices like Surface Laptop 5G for Business, supported by Verizon’s network and enterprise mobility services, users have responsive access to apps and data, whether they are working in transit, off-site, or in locations where Wi-Fi is unavailable or unreliable. Verizon’s 5G infrastructure with built-in security features helps mobile professionals maintain business continuity with high-performance connectivity across environments.

This blog outlines how Surface and Verizon 5G work together to help meet the demands of today’s mobile work, support AI-assisted productivity, and deliver a scalable approach to secure device management.

Connectivity designed for mobility, not dependency

Tethering to phones, relying on shared hotspots, and searching for open networks introduce friction. They also increase risk. Public Wi-Fi remains vulnerable to common attack methods, including man-in-the-middle interceptions, packet sniffing, and rogue access points. Even well-configured networks present challenges when users move between environments or require low-latency access to cloud services.

Once provisioned, the connection on the Verizon 5G network with built-in security features is persistent and controlled through enterprise policies. Employees stay connected to Microsoft 365, line-of-business apps, and cloud resources without depending on user-managed solutions. Connectivity becomes a built-in function of the endpoint, not an external variable.

Verizon’s 5G network supports this model with coverage, bandwidth, and enterprise-grade protections. Based on RootMetrics 1H 2025 RootScore® Report, Verizon is ranked as the most reliable 5G network in United States . Ookla Speedtest Intelligence® confirms Verizon provides the best mobile coverage across the country as of 1H 2025.² Experiences vary by region and device, but the infrastructure is in place to support business use at scale.

5G support enables real-time productivity with Copilot+ PCs

Surface Copilot+ PCs combine two essential elements for AI-enabled productivity: dedicated 40+ TOPS NPUs for local inference and persistent connectivity for access to cloud-based models. This supports a work experience that is responsive, reliable, and adaptable to real-world work conditions.

At the same time, many AI scenarios—such as summarizing documents in Word, generating responses in Outlook, or retrieving meeting insights—depend on large-scale cloud models. These use cases require a fast, stable connection to the Microsoft 365 cloud to deliver contextually relevant, up-to-date results.

5G makes this possible virtually anywhere. With support for 5G built in, Surface devices can stay connected to cloud AI services without requiring Wi-Fi or tethering. Users benefit from low-latency access to Copilot features, the ability to sync with company resources when away from Wi-Fi and in range of a compatible 5G network, and a consistent experience across locations. The result is an AI-powered workflow that feels continuous and dependable.

Security from chip to cloud

The multilayered security model of Microsoft Surface helps protect your business at every level—and 5G assures a carrier-provided connection. With features such as TPM 2.0, secured-core protections, BitLocker encryption, and Windows Hello biometric authentication, Surface devices deliver security at every layer of the stack.

Verizon’s mobile network architecture complements these device-level protections. It provides secure SIM and eSIM provisioning, encrypted data transmission, and support for private network slicing, secure tunneling, and VPN passthrough. Enterprises can implement split tunneling, web filtering, and endpoint protection through Verizon’s hosted mobile private network services. These protections extend from the physical layer through the application layer, supporting a zero-trust posture across environments.

Surface devices with 5G can be deployed and managed through Microsoft Intune,³ giving IT administrators full control over connectivity settings, data usage, roaming policies, and device health. This single-pane approach to policy enforcement reduces the burden of mobile device management while increasing visibility across distributed teams.

Connectivity you can rely on

With traditional Wi-Fi-first devices, the burden of securing and managing connectivity often falls to the end user. They decide when to connect, where to connect, and how to troubleshoot. When connections fail, productivity stalls. When networks are misconfigured or untrustworthy, data may be at risk of exposure.

Surface with 5G extends the management model IT already uses for Wi-Fi. Connectivity can be provisioned, monitored, and governed just like device configuration, updates, and security. eSIM profiles can be deployed without physical cards, roaming can be restricted by location or usage tier, and data caps can be enforced at the organizational level. Employees stay focused on work instead of managing connectivity. This shift moves connectivity from a point of friction to a managed enterprise capability. It also aligns with the broader shift toward policy-based management of endpoints, where settings and behaviors are defined by role and risk, not user behavior.

Surface and Verizon support a future-ready device strategy

Surface devices with 5G are practical investments for organizations aligning their endpoint strategy with hybrid work, AI integration, and mobile productivity. These devices support core IT requirements for manageability, security, and lifecycle value. They also support user expectations for immediacy, performance, and flexibility. The devices are optimized for Windows 11, can managed through Microsoft Intune, and supported by Microsoft 365.

Verizon adds a layer of infrastructure that makes these features viable beyond the office. It helps enable secure access to the network edge. It removes the limitations of location. It supports the pace and pressure of real-world work. 5G is rapidly becoming a core enabler of modern work. Surface for Business with Verizon connectivity delivers on the promise of working from virtually anywhere— intelligently and without delay on the Verizon 5G network with built-in security.

References

Battery life varies significantly based on usage, network and feature configuration, signal strength, settings, and other factors. See Surface Battery Performance for details.
Based on RootMetrics® United States RootScore® Report: 1H 2025. Tested with best commercially available smartphones on three national mobile networks across all available network types. Your experiences may vary. RootMetrics rankings are not an endorsement of Verizon.
Separate subscription required.

Surface Joins the Open Device Partnership (ODP)

kdhillon — Thu, 09 Oct 2025 15:00:00 GMT

At Surface, our commitment to delivering exceptional devices means continuously investing in leading-edge technology that ensures security, reliability, and innovation at every level. That’s why we’re excited to announce that Surface is joining and taking a leadership position in the Open Device Partnership (ODP). 

What is ODP?

ODP is an industry-wide, open-source initiative focused on advancing security, fundamentals, and standardization in device software. The partnership's work addresses long-standing challenges in firmware and system design by leveraging memory-safe programming languages like Rust and hardware-rooted security features and doing so based on standards that will work across a partner's entire device product line. This approach reduces exposure to common vulnerabilities while providing manufacturers with a sustainable, consistent foundation that lowers engineering costs across product lines. As part of Open Device Partnership (ODP), Surface is investing in several foundational technologies that are shaping the future of secure and reliable devices including:

Patina, Rust-based, UEFI-compatible firmware designed for memory safety and to address long standing challenges in the PC firmware ecosystem.
Secure Embedded Controller (EC) firmware, providing a modern, security-focused embedded controller implementation designed to eliminate classes of bugs prevalent in legacy EC codebases.
Unified OS-EC service interface, ensuring that operating systems can interact with embedded controllers in a consistent, well-defined way across devices.

What This Means for Surface Customers and Partners 

Stronger Security: ODP is built with modern tools, including Rust — a programming language known for safety and reliability. This reduces vulnerabilities and helps protect your device from emerging threats. 
Consistent Quality: Shared, tested firmware components mean fewer bugs and better performance across device lines. 
Faster Innovation: ODP’s modular design lets Surface engineers integrate new features and hardware more quickly, so you get access to the latest advancements sooner. 
Supply Chain Transparency: Using an open platform improves supply chain visibility and compliance, helping maintain product integrity and trust. 
Future Ready: ODP supports both current and emerging hardware standards, positioning Surface devices to adapt to new capabilities as they develop.

A Partnership That Benefits Everyone 

Adopting ODP is not just about Surface improving its own devices — it’s about joining a growing ecosystem of hardware makers, silicon vendors, and software engineers collaborating to create a more secure and innovative computing future. 

This collaboration accelerates Surface’s ability to deliver transformative, reliable devices while contributing valuable real-world experience back into the open-source community. Together, we’re advancing firmware technology to benefit all users — from individual consumers to enterprise customers and resellers. 

We are excited to be contributing to this partnership and look forward to sharing more information in the future.

References

Surface Highlights at Microsoft AI Tour: Chicago & Toronto

Andrea_Director — Thu, 25 Sep 2025 14:32:27 GMT

The Microsoft AI Tour is starting in Chicago on September 25 and then heading to Toronto on October 1. Join Microsoft Surface in the Connection Hub and our Lightning Talk to see how Surface is enabling AI transformation.

For the full agenda and speakers, visit the Microsoft AI Tour site.

Experience Surface in the Connection Hub

Attendees will have the opportunity to experience the Surface product lineup firsthand, including the new Surface Laptop 5G for Business and the latest Copilot+ PCs. These devices are designed to empower IT teams and end users with performance, security, and seamless integration of AI capabilities.

Capture Your #MicrosoftAITour Moment

In Chicago and Toronto, be sure to snap a personalized photo with the Giant Surface. Share your moments with us using #MicrosoftAITour and #SurfaceforBusiness.

Don’t miss our Lightning Talk: Accelerate your AI transformation with Surface Copilot+ PCs

Learn how Copilot+ PCs bring AI directly to the device with performance, security, and deployment.

Chicago – Sept 25, 3:20–3:35 PM CDT
Toronto – Oct 1, 2:40–2:55 PM EDT

The Tour Continues

Chicago and Toronto are just the beginning. The Microsoft AI Tour is coming to cities worldwide. Find us in a city near you!

Surface Hub: Windows 10 Team Support Ends Oct 14, 2025 - Act now! Updated

FrankBuchholz — Tue, 14 Oct 2025 15:26:23 GMT

On October 14, 2025, support for Windows 10 Team Edition will end. On the same date, the Microsoft Teams App on Windows 10 Team will also stop functioning, devices will no longer be able to log into Microsoft Teams.

This means any Surface Hub 2S devices that remain on Windows 10 Team after that date will lose the ability to join Teams meetings and will no longer receive critical security updates. In short: your meeting spaces will be at risk of disruption and may be left offline.

If your organization is still running Surface Hub 2S devices on Windows 10 Team, now is the time to act.

Migration is paramount to ensure your teams continue to deliver the modern Microsoft Teams Rooms on Windows (MTR-W) experience on Surface Hub.

Updates to this blog (Oct 14, 2025)

Migration App extended: The Surface Hub Migration App remains available through mid-December 2025 to help complete transitions. (Note: Teams on Windows 10 Team still retired Oct 14, 2025; only the app’s availability is extended.)

Microsoft Edge on MTR-W: available now on Surface Hub running MTR-W.

Miracast: On track and committed before end of CY2025.

Parity note: Microsoft Edge features are currently only MTR-W features, offering a consistent user experience across certified Windows All-in-One boards (e.g., Yealink, MAXHUB, Logitech) in addition to Surface Hub. (Not available on MTR-A.)

Migration Options for Surface Hub 2S

There are three supported paths to migrate Surface Hub 2S devices from Windows 10 Team to Windows 11 with MTR-W. Use the guide below to choose the right option for your organization:

Migration Path	Best For	Key Benefits	Availability	Notes
Surface Hub 3 Compute Cartridge	Organizations seeking the longest lifecycle and enhanced performance	- Faster CPU and more memory - Driver/Firmware and Windows/MTR updates through Dec 2030 - Enables rotation on 50" Hubs	Available now	Recommended path for most customers. Learn more.
Migration App	Customers needing a short-term bridge	- No new hardware required - Quick path to Windows 11 MTR-W	Extended to Dec 14th, 2025	Teams support still ended Oct 14, use remaining window to finalize upgrades Learn more at this article.
USB Migration	Environments with network restrictions or where offline setup is required	- Direct path to Windows 11 MTR-W via USB - Flexible deployment	Available now	New option for customers with deployment constraints. Learn more.

What About Surface Hub v1?

Surface Hub v1 devices cannot be migrated to Windows 11.

However, they don’t need to become “paperweights.” Many customers have successfully repurposed them as interactive external displays for whiteboarding or digital signage.

See this guide from Ryan Wold of the Surface Engineering team: How to use Surface Hub v1 as an external interactive display
Explore additional insights on Ryan Wold’s blog.

Why Upgrade to Microsoft Teams Rooms for Windows (MTR-W)

Migrating isn’t just about avoiding end of support—it unlocks a modern, AI-enhanced meeting experience and enterprise-grade operations:

Long-term servicing, security & lifecycle — With the Surface Hub 3 Compute Cartridge, devices receive driver and firmware support through December 2030.
Consistent, proven experience — MTR-W brings feature parity with other Teams Rooms on Windows endpoints across your estate (layouts, device behaviors, admin controls), so users get a familiar experience in every room.
AI-enhanced hybrid meetings — Unlock IntelliFrame (smart, participant-focused video feeds) and related intelligent camera capabilities that make in-room participants clearer and more engaging to remote attendees.
Inclusive layouts built for collaboration — Use Front Row to keep people, content, and chat visible at once, improving engagement and co-creation in hybrid meetings.
Pro-grade management & reliability — Enroll rooms in the Teams Rooms Pro Management service for proactive monitoring, inventory, remote configuration, alerting, and update orchestration; manage devices centrally alongside the Teams Admin Center.
Enterprise readiness at scale — Follow Microsoft’s plan-deploy-operate guidance to standardize configurations, enforce policies, and streamline site-by-site rollouts for large deployments.
Feature parity note: Edge and similar in-room functions are MTR-W capabilities, not Surface-Hub-only, ensuring consistent UX across OEMs.

Upgrading ensures Surface Hub becomes a purpose-built MTR-W endpoint—secure, manageable, and continuously improved with Microsoft’s Teams Rooms roadmap.

Next step: Once migrated, enroll your Surface Hubs into the Teams Rooms Pro Management portal to ensure proactive monitoring, health insights, and reliable operations at scale.

What’s Next for Microsoft Teams Rooms on Surface Hub

Migrating to Windows 11 with MTR-W not only keeps your devices supported — it ensures they stay aligned with Microsoft’s innovation roadmap:

Microsoft Edge Browser is available now for all Surface Hubs running Microsoft Teams Rooms - Windows. Edge browser on Teams Rooms touch boards - Microsoft Teams | Microsoft Learn
Miracast support is on track to release by the end of December 2025
Regular Teams Rooms updates will continue to bring parity with other certified Teams Rooms devices, keeping your collaboration spaces modern and consistent

Video Guidance & Learning Resources

To support your migration journey:

Watch Surface Hub migration overview videos on Microsoft Helps (YouTube)
Review the previous Surface IT Pro Blog: Updated: Surface Hub support ends for Windows 10 — start your transition
Explore Microsoft’s official documentation: Surface Hub Windows 10 End of Support and Migration Options

For organizations with larger deployments, engage your Microsoft account team or partner. Microsoft FastTrack and authorized Surface partners can also assist with planning and execution.

Call to Action

Upgrade your existing Surface Hub 2S devices today!

Teams will stop working on Windows 10 Team devices on Oct 14th, 2025.
Devices will no longer receive security updates, leaving them exposed.

Begin testing your chosen migration path today to ensure a smooth transition. Work with your IT team and Microsoft partners now to avoid last-minute disruption.

Act now to keep your Surface Hubs secure, supported, and meeting-ready.

From mission to impact: Why Surface is the trusted choice for nonprofits

Brandon_Dorfman — Sun, 17 Aug 2025 12:00:00 GMT

In the heart of a bustling city center, a mobile outreach team from a nonprofit sets up a pop-up care station. Within minutes, they’re checking in community members, recording case notes, and coordinating services with their central office—all from a single device. A thousand miles away, a social worker in a rural town conducts a telehealth intake session with a family who otherwise wouldn’t have access to care.

Across continents and causes, nonprofits are redefining what it means to serve—and technology is quietly powering this transformation behind the scenes.

Meeting the moment: The evolving needs of nonprofit work

Nonprofits have always been on the front lines of change, but their work today is more dynamic—and more digital—than ever. Teams must stay responsive in fast-changing environments, often with limited staff, tight budgets, and rising community needs. Whether it’s youth support, healthcare delivery, disaster relief, or advocacy, they are doing more with less—and doing it everywhere.

Mobility, security, and real-time collaboration have shifted from "nice-to-have" to "must-have." Yet many organizations still rely on outdated hardware that hinders more than it helps.

That’s where the shift begins.

Technology that travels with the mission

The most effective nonprofit technology solutions don’t sit in an office—they move with the mission. Devices must be easy to carry, quick to deploy, and secure enough to handle sensitive data in the field. They must also adapt to a wide range of roles—from volunteers checking in at an event to case workers logging site visits or responding to emergencies.

The Salvation Army New Zealand understood this challenge well. Their teams needed to reach people in rural communities while maintaining centralized coordination. By equipping field workers with mobile-first devices and secure cloud access, they extended their care beyond urban centers—without adding IT complexity.

“Surface gives us the flexibility we need to be where our community needs us most.”
— The Salvation Army, New Zealand

This story isn’t unique. It's part of a larger shift: nonprofits designing strategies that put people—and portability—first.

Read how Salvation Army New Zealand transformed mobile outreach with Surface.

Empowering volunteers and staff through simplicity

Volunteers are the lifeblood of many organizations. Yet onboarding and equipping them can be time-consuming if the technology isn’t intuitive. Devices that support instant sign-in, cloud-based access, and familiar tools like Microsoft 365 allow volunteers to contribute quickly and confidently.

Imagine a community health event where volunteers rotate across check-in, data entry, and follow-up roles. With multi-mode devices that can switch from tablet to laptop and back, one device can serve many roles—maximizing both impact and investment.

Vitalant used Windows Autopilot to streamline device deployment across donation centers, allowing teams to stay focused on donors—not on tech.

Read how Vitalant streamlined deployment across mobile teams with Windows Autopilot and Surface

Turning real-time data into real-life outcomes

Today’s nonprofit leaders want more than anecdotal stories—they want data-driven insights to demonstrate impact, secure funding, and shape strategy. That means frontline teams must be able to capture data as it happens: during home visits, outreach drives, or counseling sessions.

Devices with integrated transcription, e-signature support, and even AI-generated summaries are transforming how case workers and clinicians document their work. These tools help staff spend less time on paperwork and more time delivering care and services where they’re needed most.

Whether it's a donor update or an urgent case referral, speed matters—and so does trust in the device that gets you there.

Security, sustainability, and scale: Behind-the-scenes priorities

While visibility often focuses on programs, IT leaders at nonprofits must also balance security, sustainability, and long-term affordability. Devices that support end-to-end encryption, zero-touch deployment, and modular repair options offer both peace of mind and fiscal responsibility.

Surface devices, particularly the latest Copilot+ PCs, are built with these principles in mind. Their AI capabilities—like summarizing reports or drafting emails—can help small teams scale their communications and reduce manual work, all while staying within nonprofit budgets and sustainability goals.

It’s not about the device. It’s about the mission.

The right device doesn’t just support the mission—it extends it.

For nonprofits, Surface is more than hardware. It’s a strategic partner that helps organizations stay agile, empower staff, and meet communities where they are. With trusted security, mobility built in, and powerful AI at the ready, nonprofits can focus on what they do best: creating lasting change.

Ready to empower your mission?

Nonprofits can access exclusive pricing, licensing, and deployment support through the Microsoft Nonprofit Program.

Equip your teams with the tools to serve, respond, and lead—anytime, anywhere—with Surface and Copilot+ PC.

Learn More

Discover how Surface and Microsoft 365 can help your nonprofit:

Partner showcase: Developing for on-device AI with Surface Copilot+ PCs with Teknikos

Chauncey_Larsen — Fri, 01 Aug 2025 15:00:00 GMT

Running local language models on Windows: a working example with RAG and Phi Silica

As developers integrate AI into their applications, they benefit from increased flexibility about where AI computation runs. With the introduction of Phi Silica which is integrated directly into the Windows App SDK as part of the Windows AI Foundry platform, Microsoft has created an integrated environment for building on-device AI experiences that are performant, private, and portable.

One recent effort—the Teknikos PDF Explorer demo—shows what’s now feasible. Built by Teknikos in collaboration with Microsoft Surface and running on Copilot+ PCs, the application leverages the dedicated Neural Processing Unit (NPU) to deliver local language understanding without relying on external infrastructure. This post examines the technical architecture, design process, and development implications of the project.

Teknikos PDF Explorer menu view

A Windows-native small language model

Phi Silica is a small language model optimized for NPU acceleration on

Windows 11. It integrates through the Windows App SDK and supports inference directly on compatible hardware. Unlike general-purpose models that require manual installation, Phi Silica deploys via Windows Update and runs with minimal code through C# bindings.

The Teknikos PDF Explorer project uses retrieval-augmented generation (RAG) to answer natural language questions about PDF documents. Input is parsed locally, and Phi Silica returns direct responses and suggested follow-ups—all computed on the NPU. The result is a self-contained document intelligence tool that does not require a network connection or cloud API.

Engineering context

Development began with earlier versions of the demo running inference on the GPU using Phi-3 Mini. This supported basic RAG workflows but lacked consistent performance. Once Phi Silica became accessible through the SDK, the team refactored the application to shift all inference to the NPU. The result was more predictable response quality and reduced latency, with an overall improvement in interaction flow and relevance. The updated app supports dynamic switching between GPU and NPU models. This flexibility enables comparative testing and adaptation across system configurations.

The Teknikos PDF Explorer RAG pipeline begins when a user selects a PDF file. The text is extracted and split by page, then further chunked and tokenized in preparation for vectorization. Using ONNX Runtime with the all-MiniLM-L6-v2 language model, an in-memory vector store is created to represent the PDF’s contents.

User question submission and interaction demo

When the user submits a question, the application performs a semantic search using cosine similarity over the vector store, returning a ranked list of relevant chunks. The corresponding PDF pages are displayed as interactive thumbnails that can be enlarged. The user’s question and the top-ranked chunks are then passed to a language model as part of the prompt.

The language model streams its response in real-time. In the case of Phi Silica—due to its improved reliability compared to Phi-3 Mini—the model is also instructed to generate three follow-up questions based on the retrieved context. A prompt-driven structured response format ensures consistency, making it easy to extract the follow-up questions and render them as clickable buttons for continued exploration.

The result is an intuitive question-answering experience that guides users through complex documents with contextual relevance and minimal effort—all running on the local device.

Use case design: privacy, portability, performance

The value of on-device inference lies in constraint-aware environments. Applications that operate under regulatory, physical, or network limitations benefit from local execution in several ways:

Data residency: Sensitive documents never leave the device.
Connectivity tolerance: Remote or mobile use cases remain functional without requiring internet access.
Cost stability: No per-call API charges.
Power efficiency: NPUs offer potentially higher performance per watt for inferencing workloads.

Field scenarios such as legal review, healthcare compliance, and mobile sales operations all map well to this architecture.

Hybrid AI: structured evaluation and routing

Jon Khoo, the developer behind the Teknikos PDF Explorer, also demonstrated a parallel approach in another demo application: evaluators. These are business rules that route inference between local and remote models based on conditions such as network status, privacy sensitivity, or battery constraints. The technique uses a common ONNX model format for both deployment targets, ensuring parity in response logic regardless of execution location. The local execution path combines ONNX Runtime with Phi Silica as the on-device language model, fully mirroring the cloud path, which pairs ONNX Runtime on Azure with an Azure OpenAI GPT-based LLM. This approach introduces a structured pathway for hybrid AI, where cloud and edge systems share a model backbone and switch based on runtime variables.

Route inference between local and remote models based on conditions

Developer impact

For enterprise teams exploring Copilot+ PCs, Phi Silica offers a focused toolchain for incorporating intelligent document processing into existing Windows applications. Developers do not need to manage model conversion, tokenization workflows, or runtime dependencies. Instead, they can focus on user experience and business logic.

The integration model is prescriptive: Microsoft defines the runtime environment, deployment mechanism, and interface contract. This limits variance but simplifies development and support. For many enterprise teams, this has the potential to accelerate delivery timelines and improve maintainability.

Creating the future of on-device AI together

The Teknikos PDF Explorer project illustrates a practical approach to embedding local AI inference in enterprise applications. Phi Silica and the Windows AI Foundry offer a stable foundation for delivering secure, responsive, cost-effective AI functionality at the device level.

As the hardware ecosystem matures and the Windows AI Foundry becomes generally available, these capabilities are poised to become part of the standard development environment for Windows. Teams that invest in building now gain early insight into the architecture and operational patterns that will define the next stage of distributed application design.

Interested in exploring on-device AI solutions or collaborating on your next innovation? Connect with Teknikos to learn more about their work and how they can support your development goals. And to discover more about our latest Copilot+ PCs and business-ready Surface devices, visit Surface.com/Business.

Resources

Safer Drivers, Stronger Devices

Melvin_Wang — Thu, 24 Jul 2025 16:56:16 GMT

When it comes to device security, the conversation often centers on software updates, antivirus tools, or cloud protections. But what about the code that talks directly to your hardware—the drivers? These low-level components are essential to performance and reliability, forming a critical foundation for device security.

At Surface, we are improving the security and reliability of Surface devices and drivers and raising the security bar for the entire Windows ecosystem by embracing Rust, a modern programming language designed with memory safety at its core.

Since our last update, the Surface team has contributed further to the open-source windows-drivers-rs for driver development and shipped Surface drivers written in Rust. This not only enhances the security posture of Surface devices—it also supports industry-wide and national initiatives to advance memory safety, as emphasized in a recent joint press release from the NSA and CISA.

The impact of the Rust Windows Drivers platform

What is windows-drivers-rs?

windows-drivers-rs is a Microsoft open-source project focused on enabling Windows driver development using the Rust programming language. Microsoft invites developers across the ecosystem to contribute, learn more about Rust, and help shape the future of Rust driver development on Windows. The Surface software team is a primary contributor to the platform.

The GitHub repository includes:

Rust Crates: A collection of crates that enables the development of Windows Drivers in Rust
Documentation, Samples, and Guides: Helps developers get started with exploring Windows drivers in Rust.
Community Collaboration: Invites contributions, feedback, and collaboration from the broader community interested in advancing Rust for systems and kernel development on Windows.

Access the open resource repository for windows-drivers-rs on GitHub

Why write Windows Drivers in Rust?

Driver development has long relied on C and C++, languages that offer performance but little protection against common pitfalls like buffer overflows, null pointer dereferences, or race conditions. Writing Windows Drivers in Rust changes that.

Here’s how:

Memory Safety: Rust’s ownership model and borrow checker can eliminate entire classes of bugs—like use-after-free or double-free—that often lead to security vulnerabilities.
Type and Concurrency Safety: By default, Rust enforces strict type checks and catches data races at compile time, making multi-threaded driver code safer and more predictable.
Compile-Time Abstractions and Guarantees: By leveraging zero-cost abstractions and Rust’s strong static analysis, many bugs are caught at compile time, before the code ever gets a chance to run.
Interoperability: Leveraging Rust’s Foreign Function Interface (FFI) features, developers can enable interoperability between Rust and existing C/C++ driver code, making it easier to adopt Rust incrementally in existing projects.

The result? Drivers that are not only more secure, but also easier to maintain and evolve.

Surface develops & delivers

By integrating Rust drivers into our shipping products, we’re reducing the attack surface with memory safety and improving reliability for our customers who depend on Surface every day. We’re proud to share that Surface has now shipped several Copilot+ PCs with drivers written in Rust using code built on top of the windows-drivers-rs platform:

What’s next?

Surface will continue to deepen its investment in Rust driver development through several focused initiatives:

Enhancing the platform for Windows Drivers in Rust to support a broader range of driver types, making it viable for more hardware scenarios
Advancing feature support to bring the Rust-based toolchain closer to parity with the existing Windows Driver Kit (WDK), helping developers transition more easily
Expanding the availability of safe, open-source abstractions. Today, all Rust drivers shipped on Surface devices rely on internally developed safe abstractions layered over the FFI capabilities provided by the windows-drivers-rs crate family - particularly the wdk-sys crate. Looking ahead, we’re collaborating with partners to generalize these abstractions and make them available in the public GitHub repository, enabling broader community use and contribution.
Partnering across Microsoft to accelerate internal adoption and improve tooling, documentation, and long-term maintainability.

Together, these efforts aim to make Surface drivers even more reliable and secure. In the long term, this work won’t just improve our own devices - it will help strengthen the Windows ecosystem for all hardware partners.

Join the movement

If you’re passionate about secure systems, modern tooling, or just curious about Rust on Windows, we’d love to connect.

The Surface team will be at RustConf 2025 this September in Seattle—come find us, share your ideas, and help us build a safer foundation for Windows.
Check out the Windows Driver Rust project on GitHub. Start a discussion, file an issue, contribute a pull request, or contact us about the project.

Together, we can make memory safety the default!