What Project Solara Is and Why It Matters
Project Solara is Microsoft’s chip-to-cloud AI agent platform that reimagines enterprise devices as always-on, identity-aware endpoints where users interact with multiple AI agents instead of traditional applications. By centering the experience on agents, Solara treats each device as a window into workplace workflows, data and services, rather than as a self-contained computing hub. Unveiled at Build 2026, the platform currently exists as an early preview rather than a product IT teams can buy and deploy. Microsoft positions it as a way to move AI agents off laptops and browsers and into dedicated workplace hardware with microphones, cameras, and cloud connectivity built in from the start. That shift hints at a new enterprise model: instead of users launching apps on PCs, they engage task-focused devices that coordinate with cloud-scale intelligence, authenticated identities and managed access policies in the background.
From Smart Badges and Desk Devices to Multi-Agent Workflows
Microsoft’s Solara vision is grounded in two reference designs: a desk device and a wearable smart badge. The desk concept resembles an Echo Show-style display tied into Microsoft 365, able to surface Outlook calendars, Excel data and other workplace information while supporting face authentication, mic mute controls, USB-C connectivity and optional Windows 365 client support. The mobile badge concept adds a touchscreen, fingerprint sensor, privacy switch, side-facing camera and 5G, turning ID cards into portable AI agent platforms for frontline staff. According to TechRepublic, Microsoft is “designing Solara for a multiple-agent world,” where organizations can mix Microsoft’s own agents with ones they build or source. These devices act less like personal computers and more like persistent terminals into longer-running agent processes in Azure, potentially reshaping frontline roles in healthcare, retail, logistics and field operations.
Built on MDEP: Android Roots with Enterprise Controls
Under the hood, Project Solara runs on Microsoft Device Ecosystem Platform (MDEP), an Android Open Source Project-based system tuned for enterprise devices. That gives Solara a different foundation from Windows-focused AI experiences while keeping compatibility with diverse hardware form factors. Microsoft describes Solara as “specifically designed for the new era of agent-first devices,” pairing hardware and software requirements with manageability, security and privacy baselines. Reference designs already integrate Entra ID sign-in, Intune device management, Windows Hello for Business, approved chipsets, and strict privacy controls like hardware switches for cameras and microphones. Qualcomm and MediaTek are first in line as silicon partners, while private pilots with organizations such as Target, CVS Health, Best Buy, Levi’s and AccuWeather will test Solara’s flexibility. Microsoft’s “just-in-time UI” concept further lets interfaces adapt on the fly to different screen sizes, supporting a future of heterogeneous but managed AI agent endpoints.
Identity, Privacy and Device Management in an Agent-First World
Solara raises familiar IT concerns in a new form, because agent-first enterprise devices demand access to identity, data and sensing capabilities by design. A Solara-style smart badge or desk display might continuously handle microphones, cameras, recordings, transcripts and cloud-based AI agent services, all tied to workplace identities. That makes device management, authentication, consent, data retention and compliance central rather than optional. Enterprise controls such as Intune, Entra ID and Windows Hello for Business are not add-ons; they are prerequisites for treating Solara hardware as managed endpoints on par with laptops or phones. Healthcare pilots, including Microsoft’s Dragon Copilot work for clinicians, underline the stakes: agent-first workflows may streamline documentation and follow-up tasks, but they must also respect patient privacy and regulatory requirements. IT teams will need clear policies on who owns agent outputs, how long they are stored, and how access is audited across multiple agents on a single device.
