Microsoft’s Copilot just took a decisive turn away from answering questions and toward actually getting things done. On May 5, 2026, the company pushed its Copilot Cowork system to iOS and Android, added reusable Skills that turn ad‑hoc prompts into repeatable organizational procedures, and opened the door to third‑party plugins for the first time. The expansion is limited to Frontier program customers using Microsoft 365 Copilot in early‑access environments, but the signal is unmistakable: the era of AI that only chats is over. Now it’s about delegation.
What Actually Changed: Cowork Leaves the Chat Box Behind
The biggest headline is mobile availability. Until now, Copilot Cowork lived exclusively on the desktop, leaving the impression that this agent‑style assistant was bound to the PC. The update puts it inside the Microsoft 365 Copilot app on iOS and Android. You can now kick off a complex, multi‑step task from your phone — while commuting, between meetings, or standing in line — and trust that it will keep running in the cloud even after you lock the screen.
That mobile launch is accompanied by two structural additions. First, Cowork Skills: pre‑packaged or custom‑built instruction sets that tell Copilot how to perform a routine. Instead of typing, “Write a status update in our standard format, pulling from the weekly project log and last leadership meeting notes, tone professional but concise,” every Monday morning, a Skill stores that pattern once and reuses it. Microsoft provides built‑in Skills for common Office 365 actions — document creation, meeting coordination, email management, research, and content handling — while organizations can craft custom Skills that embed their own practices.
Second, plugins expand Cowork’s reach beyond the Microsoft bubble. The service now integrates more deeply with Fabric IQ and Power BI, taps into Dynamics 365 for sales, customer service, and ERP, and is preparing connectors for LSEG, Miro, monday.com, S&P Global Energy, and custom internal systems. If a task requires data from a CRM or a project board, Cowork can now reach it.
The feature remains a Frontier exclusive, meaning it’s not available to all Microsoft 365 Copilot subscribers. Enrollment requires admin opt‑in, and the experience may vary by market, tenant configuration, and licensing. Microsoft’s preview label carries real weight here: capabilities could shift, and the rollout is deliberately uneven.
What It Means for You — Depending on Who “You” Are
For the Everyday Knowledge Worker
If your organization has access, Cowork changes the rhythm of a task‑heavy day. Instead of sitting at your desk, prompting Copilot in a chat pane, reviewing the output, and then manually taking the next step, you assign a job and walk away. The system breaks the instruction into steps, uses the appropriate apps, and surfaces results in a task dashboard. At most, you’ll be asked to approve a sensitive action — sending an external email, updating a record — before it proceeds.
That shift turns the phone into a control panel. On a train, you can tell Cowork: “Prepare a meeting brief for tomorrow’s client call. Pull the latest email thread, last quarter’s purchase data, and the proposal draft from SharePoint. Summarize open action items.” The work happens in the cloud; you check back later to review, tweak, and approve. For anyone who has ever tried to do genuine document assembly from a touchscreen, this is a quiet revolution.
But the real power isn’t in one‑off delegations. It’s in Skills. Once a team agrees on how a weekly report should be structured, a Skill freezes that agreement into an accessible routine. No more copy‑pasting a prompt from a pinned chat message or trying to remember which folders a colleague said to scrape. The consistency acts like an institutional SOP, and the time saved scales across the group.
For IT Administrators
Every line of new functionality for end users is a new governance surface for IT, and Cowork is no exception. Admins will immediately need to answer: who can create Skills, who can share them, and who approves a Skill that’s built by a department head but touches data owned by another team? The plugin expansion compounds this. If Cowork can connect to monday.com or a CRM, does that create a shadow data bridge? Does a plugin get the same DLP treatment as a direct app connection? Can a user silently enable a third‑party connector from their phone?
Microsoft says the system includes admin controls, but the specifics — policy granularity, deployment rings, audit trails for Skill creation and plugin consumption — are what will determine whether Cowork stays in a sandbox or scales to the wider organization. Early‑adopter IT teams should treat this less like a feature toggle and more like a pilot program. Map out which workflows could benefit from delegation, decide which roles need approval authority, and define which external services are safe to connect. The support desk will also need a new playbook: users won’t file tickets about “agentic workflow failures.” They’ll say “the AI didn’t find the right file” or “it sent the email in the wrong tone.” Training and triaging for AI‑assisted failures is now an operational requirement.
For Windows Users in Particular
Cowork isn’t a Windows feature — it runs in the cloud, spans mobile, and lives inside Microsoft 365 Copilot. But the Windows PC remains a vital node. Most users will review, edit, and approve Cowork’s output on a laptop or desktop. A task may start on a phone, but the final PowerPoint deck gets polished in Windows, the Excel model gets stress‑tested in a native app, and the Teams message gets sent after a quick desktop review. Microsoft’s larger play is to make Windows the richest workstation for supervising AI‑driven work. If Cowork succeeds, it strengthens the case that Windows PCs are essential in an AI‑first enterprise stack — not because the Start menu has a chatbot, but because the operating system provides the context‑rich environment where AI outputs become finished products.
How We Got Here: From Side Panel to Delegation Engine
Two years ago, Copilot was a writing assistant that lived in a Word sidebar. A year ago, it became a meeting summarizer and spreadsheet analyst that still required a human to copy‑paste its suggestions into action. That was always the flaw: the AI was smart enough to recommend, but too passive to execute. The industry call that followed — “agentic AI” — promised assistants that didn’t just suggest, but acted. Microsoft’s first deliberate step toward that was Copilot Cowork, which arrived earlier in 2026 exclusively on the desktop. It introduced the concept of a persistent, cloud‑based worker that could pause, ask for approval, and continue a task thread over minutes or hours.
That desktop version, however, limited the “assign and walk away” promise. True delegation requires the freedom to start a job and not watch it. Putting Cowork on mobile closes that loop. The move also reflects a pragmatic shift inside Microsoft’s AI architecture. Cowork’s development leans on a collaboration with Anthropic, signaling that Microsoft is willing to use the best model for the job rather than relying solely on its OpenAI partnership. For enterprise customers, that’s a feature, not a bug: they care about reliable task completion more than model label politics. It also adds complexity to the trust and compliance story — every new model provider introduces fresh questions about data handling, subprocessors, and regulatory alignment.
On the plugin front, the evolution mirrors what happened with Teams and Power Platform. Microsoft starts with native connectors, then opens to third parties, then allows custom development. The risk, as always, is fragmentation. If Cowork becomes an orchestrator that sits above dozens of SaaS tools, its value lives and dies on how seamlessly IT can manage those connections. Every security team remembers the moment OAuth integrations turned into permission sprawl. Cowork plugins could follow the same arc if governance isn’t baked into the admin experience from day one.
What to Do Now — If You Have Access, and If You Don’t
If your tenant is enrolled in the Frontier program:
- Start with a pilot group. Pick a department that already has well‑documented repetitive processes — sales operations, project management, or executive communications — and give them access first. Their feedback on Skill reliability and plugin utility will shape the rollout.
- Define a Skill approval process. Decide who can write, publish, and modify custom Skills. Treat Skills like policy artifacts: they enforce a way of working, and a bad Skill can propagate errors at scale.
- Audit existing SaaS connections. Before enabling the plugin store, map which third‑party services already have data‑sharing agreements with your organization. Prioritize connectors that align with approved apps.
- Train the help desk. Create a playbook for common Cowork failure modes: missing permissions, plugin authentication errors, Skills that produce the wrong formatting, approval‑loop blocks. Make sure front‑line staff know how to escalate model‑related issues.
- Engage with Microsoft’s feedback channels. Frontier is a two‑way street. The more granular the governance requests you submit, the more enterprise‑ready the final product will be.
If you’re not in Frontier:
Keep an eye on the admin center for announcements about broader availability. In the meantime, start the internal conversation about which workflows are worth delegating. Document those processes now — even without AI. When Cowork reaches your organization, having a library of well‑defined routines will let you build Skills immediately, rather than starting from zero. Also, review your vendor‑risk management for cloud‑connected AI. The compliance questions Cowork raises (data residency, auditability, access controls) will apply to any agentic tool, not just Microsoft’s.
Outlook: The Battle for the “Do” Layer
Cowork’s mobile launch is a tactical update with strategic implications. Every major productivity vendor is racing to build an AI layer that doesn’t just inform but acts — automating workflows, connecting systems, and reducing the coordination tax of knowledge work. Microsoft’s advantage is its installed base: when the agent can already reach your email, calendar, files, and collaboration hub, the path to value is shorter. The challenge is trust. Delegation requires a level of reliability that chat‑based AI hasn’t consistently demonstrated. If Cowork misreads a Skill, botches a connection, or approves the wrong draft, the fallout is immediate and business‑critical.
The Frontier program gives Microsoft a safe proving ground. The next six months will show whether the governance model scales, whether Skills genuinely reduce work rather than creating maintenance overhead, and whether plugins stay manageable. For Windows users, the story is bigger than a phone app. It’s about the operating system’s evolving role in an AI‑managed workplace — a shift from tool to supervisor’s console. The phone may start the task, but the desktop where it gets reviewed and signed off is almost certainly running Windows.
For now, the practical takeaway is simple: Copilot Cowork is not the finished article, but the scaffolding is now in place for delegated AI work. Mobile, Skills, plugins — together they form the minimum viable framework for an assistant that doesn’t just answer, but does. The organizations that spend 2026 learning how to supervise that work will be the ones that extract real value when the feature matures.