The employee badge has had one job for fifty years: prove you’re allowed to be here. Microsoft just announced it wants to give it a second one.

Project Solara, unveiled at Build 2026, is a chip-to-cloud platform for what Microsoft calls “agent-first devices” — hardware built from scratch around AI agents rather than applications. The badge is the most visible artefact. But the badge is almost beside the point.

For the rest of us: what is an agent-first device?

Every computing device you’ve used in the last forty years was built around the same assumption: you open an application, the application does something, you close it. The device is a container for apps. The interface is a menu of things you can do.

An agent-first device inverts this. There are no apps to open. Instead, there’s an agent — a piece of software that understands intent, routes tasks, and generates an interface only when one is needed. The interface isn’t permanent. It appears for the task and disappears afterwards.

Microsoft calls this “just-in-time UI.” The analogy to just-in-time manufacturing is intentional: you don’t stockpile interfaces any more than you stockpile inventory. You produce what you need, when you need it.

What Solara actually is

Project Solara has three structural pillars.

Enterprise-readiness first. This is not a gadget. The platform runs on Microsoft’s Device Ecosystem Platform, built on Android’s open-source foundation with Microsoft Intune for device management and Entra ID for identity. There are physical privacy switches. Biometric authentication via Windows Hello for Business. The enterprise infrastructure is the same as any managed device — which is the point.

Agent-driven interaction. When a user presses the badge’s fingerprint button, they’re not opening an app. They’re invoking the agent dispatcher — a routing layer that reads intent and hands the task to whichever specialist agent fits: Microsoft 365 Copilot for work tasks, Dragon Copilot for healthcare documentation, GitHub Copilot for developers, Facilitator for meeting transcription, Priority Agent for task management. The agents are modular and extensible. Third parties can build their own.

Just-in-time UI. The interface renders for the task — adapts across screen sizes, device types, and interaction modes — then disappears. The same agent stack runs on the badge, the desk hub, and theoretically any device running the Solara platform. You don’t rebuild your software for each form factor.

The badge hardware

The reference badge device is not a proof of concept. It clips onto clothing, packs a touchscreen, a Hello fingerprint sensor, a far-field microphone array, a side-facing camera for environmental awareness, a privacy switch, 5G, WiFi, and Bluetooth — all running on Qualcomm wearable silicon.

One press wakes an agent. One tap starts transcribing. The camera gives the agent situational context — what the wearer is looking at, what’s happening in the room — without requiring the user to describe it.

The desk hub is the stationary counterpart: face authentication via a front camera, UWB presence sensing, USB-C output for connecting external displays, and a Windows 365 client mode that surfaces a full cloud PC when needed.

Microsoft won’t sell these devices directly. The reference designs are for hardware partners to build on — each intended for a specific industry, company, or use case. Best Buy, CVS Health, Levi’s, and Target are running early pilots.

Why the architecture matters more than the badge

The badge is legible. It’s the thing that will appear in the press photograph. But the architectural claim is more significant.

Steven Bathiche, Microsoft’s CVP and Technical Fellow, put it directly: “Agents will reshape not only software, but the devices themselves.” What he’s describing is the end of device-specific application development as an organisational burden. If the agent layer runs uniformly across hardware, the question of “do we have an app for that device?” stops being a software question and becomes a hardware procurement question.

This connects directly to the LLM-as-OS thesis: if the language model is the new kernel, then Project Solara is what the hardware layer looks like when you build for that kernel instead of layering AI on top of an existing one. Windows wasn’t designed for this. Android wasn’t designed for this. Solara is.

The multi-agent model is also worth noting. There is no single dominant AI. The dispatcher routes between specialists — some from Microsoft, some from partners, some custom-built by the organisation. This is intentionally composable in a way that the current “one AI assistant per device” model is not.

What it means for enterprise architecture

For organisations thinking about their device estate, Project Solara raises a set of questions that don’t have answers yet but will matter within two to three years:

Device refresh cycles. If the value of a device shifts from running applications to running agents, does the upgrade calculus change? A badge that runs three agents well is more valuable than one that struggles to run six. The performance envelope is different.

Application estate. Every organisation has a long tail of purpose-built applications — shift management tools, inventory systems, compliance checklists. If just-in-time UI can render those functions on demand via an agent, the maintenance burden of the application layer changes materially.

Identity and access. Solara uses Entra ID, which means existing identity infrastructure applies. That’s the sensible approach, but it also means every agent interaction is an authentication event. The policy surface grows.

Vendor lock-in. This is Microsoft’s platform, built on Microsoft’s agent stack, with Microsoft’s management tools. The open-source Android base provides some escape valve, but the enterprise integrations are proprietary. That’s a familiar trade-off — it’s the same one organisations made with Microsoft 365.

Still early

The pilots are the test. Best Buy’s use case is different from CVS Health’s, which is different from a manufacturing floor or a legal firm. The reference designs need to become real devices. The agent SDK needs adoption. The just-in-time UI concept needs to work at the friction level that frontline workers will accept.

But the direction is clear. The employee badge was always a dumb credential. Making it the entry point to an agent network is the obvious next move — once you’ve decided that agents are the interface layer for everything else.

References

  • Microsoft Build 2026, Project Solara announcement — commandline.microsoft.com/project-solara-build-2026
  • Bloomberg, “Microsoft Unveils Project Solara to Bring AI Agents to Employee Badges” (June 2026)
  • Steven Bathiche, CVP & Technical Fellow, Microsoft — Build 2026 keynote
  • Pilot partners: Best Buy, CVS Health, Levi’s, Target, AccuWeather (confirmed at announcement)
  • Hardware partners: Qualcomm (portable), MediaTek (stationary)