On May 5, 2026, Microsoft released Copilot Cowork for iOS and Android, a move that turns the AI assistant from a desktop-bound chatbot into a phone-accessible task-delegation service. The update—available exclusively to Frontier early-access program members—introduces Cowork Skills, reusable patterns for how work should be done, and new connectors that let the AI reach into business systems like Dynamics 365 and soon Miro, monday.com, and financial data platforms. The headline isn’t that Copilot is on mobile; it’s that you can now hand off multi-step work from your phone and let the AI execute it in the cloud while you’re commuting, in a meeting, or away from your desk.

What Microsoft Actually Shipped

The mobile apps are the most visible change. Copilot Cowork is now available for download on iOS and Android, but only if you’re part of the Frontier program. Once installed, you can delegate a task—say, “draft a project status slides and include data from the latest sales report”—and the AI takes over. It operates in the cloud, not on your phone, assembling materials, crafting documents, and leaving the final product ready for your review the next time you open a laptop. The phone becomes an input terminal, not a workstation.

But the real muscle lies in two features: Cowork Skills and connectors. A Skill is a saved set of instructions that defines tone, structure, preferred data sources, output formats, and other recurring choices. For example, a finance team might build a “monthly variance report” Skill that always pulls from a specific Power BI dataset, follows a consistent layout, and highlights deviations over 5%. Skills can be shared within teams, so the institutional knowledge of how to do a task doesn’t vanish when a clever employee leaves.

Connectors extend Cowork’s reach. Out of the box, it already understands your Microsoft 365 graph—files, emails, meetings, contacts—so it can act with context. The May 5 update deepens integration with Dynamics 365 and Fabric-related data experiences, while third-party connectors for Miro, monday.com, LSEG, and S&P Global Energy are imminent. This means Cowork won’t just draft a document; it can pull live project timelines, visualize data, or incorporate market intelligence, turning a simple request into a coordinated, cross-app output.

All of this remains behind the Frontier curtain. Microsoft uses Frontier to test experimental Copilot features with a controlled group, so broad availability across every Microsoft 365 subscriber is not yet confirmed. But the direction is clear: Copilot is shedding its “assistant” label and becoming an agent that completes work, not just answers questions.

How Cowork’s New Skills Change Your Workday

If you’re an everyday Microsoft 365 user, the mobile apps and Skills could reshape how you handle routine work. The most immediate change is time-shifting: you no longer need to be at your desk to start a complex document. Dictate a task while waiting for coffee, and by the time you sit down, a draft is waiting. That’s not just convenience; it changes the rhythm of knowledge work. Instead of composing email follow-ups during a layover, you can instruct Cowork to gather the context, draft replies, and schedule the next meeting, then review and tweak the results later.

For power users and team leads, Skills are a standardization weapon. If your department spends hours each week formatting reports, aligning language, or hunting for the right template, a single Skill can encode that process once. A sales manager might create a “client briefing pack” Skill that always pulls account notes from CRM, embeds the latest proposal, and follows house style. Because Skills are saved and shareable, they reduce the risk of junior staff forgetting steps or producing inconsistent work. In essence, Microsoft is letting you bottle your team’s best-practice workflow into a reusable AI routine.

But that power comes with new responsibilities. A Skill is only as good as the data it accesses and the instructions it follows. If your CRM is a mess of stale entries, Cowork will faithfully produce polished outputs from bad inputs. And because Skills can be created by anyone in a team, they risk becoming a new form of shadow IT—critical processes running on undocumented, self-built automations that no one audits until something breaks. We’ve seen this pattern with Excel macros and Power Automate flows; Cowork puts natural language on top of that same citizen-developer dynamic, which makes it easier to adopt and harder to govern.

The Hidden Work: What IT Needs to Know Before Turning Cowork Loose

For IT administrators, the mobile release and connector expansion aren’t just feature drops; they’re a governance alarm bell. Cowork can now reach from a user’s phone into line-of-business systems, pulling customer records, financial data, and project plans into deliverables that may be shared externally. The convenience is enormous, but so are the risks.

Microsoft says Cowork inherits the permissions and compliance controls already configured in your tenant. If a user has access to a file or data source, Cowork acting on that user’s behalf can access it too. That sounds safe until you realize many organizations have over-permissioned environments. A marketing manager who can see confidential financial models because of legacy group memberships could inadvertently ask Cowork to pull that data into a slide deck shared with a partner. The AI won’t know it shouldn’t; it will just fulfill the request.

Auditability is another open question. When a human creates a document, you know who did it, when, and which files were consulted. With an agent, you need to know: Which version of the data did it use? Did it send an email on the user’s behalf? Can the decision path be retraced for a compliance review? Microsoft’s existing audit logs and compliance tools may capture some of this, but as of May 5, the company hasn’t detailed exactly how all Cowork actions will appear in those logs. For now, IT teams are right to treat Cowork as a pilot they monitor closely.

The practical advice: before rolling out Cowork to any team, audit the data sources it could touch. Tighten permissions so agents can’t wander into sensitive areas. Define which connectors are allowed and block the rest until you’ve vetted them. And most importantly, educate users that delegating is not the same as approving—everything Cowork produces should be treated as a draft that needs human review, especially when it involves data from multiple systems.

From Chatbot to Do-Bot: The Road to Agentic AI

Copilot Cowork didn’t appear overnight. Microsoft has been layering AI into Office since early 2023, starting with simple text generation in Word and PowerPoint. Each iteration added more context: email threads in Outlook, meeting transcripts in Teams, data ranges in Excel. But the underlying model remained “assistant”—you asked, it answered. The heavy lifting of assembling the final deliverable still fell on the human.

The industry push toward “agentic” AI changed that. Competitors like Anthropic with Claude and OpenAI with its operators have shown that the big prize isn’t the best answer; it’s the completed task. Microsoft’s unique advantage is that it owns the productivity suite where most business work already lives. That means Cowork can act inside the real documents, calendars, and databases that drive an organization, not just generate text in a separate window.

The May 5 update is Microsoft’s clear statement that it intends to win on execution, not conversation. By making Cowork mobile, it also addresses a long-standing gap: knowledge work leaks outside office hours and office chairs. Managers triage email at 10 p.m., salespeople respond from parking lots, IT leaders make decisions from a phone while commuting. By putting delegation into an app, Microsoft is trying to capture those liminal moments when work gets remembered but can’t be done.

That ambition, however, raises the stakes. A failed standalone AI agent can be abandoned. A flawed copilot embedded into the tools where you write, present, budget, and communicate becomes part of the operating environment. The transition from feature to infrastructure is exactly what Microsoft wants, but it also means failures carry broader consequences.

Your Next Steps: Getting Started with Cowork Today

If you’re already part of the Frontier program, here’s how to approach the update practically:

  • Download and test basic delegation. Install the Cowork app on your phone and try a few simple tasks—draft an email summarizing a meeting, create a presentation outline with data from a shared spreadsheet. Compare the output to what you’d produce manually. Note where the AI needs more precise instructions.
  • Explore built-in Skills. Microsoft includes pre-built Skills for common workflows: document creation, meeting coordination, research, email drafting, spreadsheet analysis, and PDF handling. Use those first to understand the format and reliability before building your own.
  • Build one custom Skill with clear guardrails. Pick a repetitive, low-risk task—a weekly status update, for example. Define exactly which data sources to use, the required structure, and a review step. Share it with a trusted colleague and iterate based on their feedback.
  • Inspect the connectors list. In the Cowork settings, see which Microsoft 365 services and third-party connectors are active. If your admin allows, test pulling data from a safe source like a sandbox SharePoint list before connecting a live CRM.

If you’re an IT administrator, your priority is preparing the environment:

  • Conduct a pilot with a small, tech-savvy group. Monitor their usage, collect feedback on reliability, and watch audit logs for unexpected access patterns.
  • Review data permissions immediately. An agent can only access what its user can access. Now is the time to clean up stale permissions, enforce least privilege, and tag sensitive files with appropriate sensitivity labels.
  • Establish a Skill review process. Decide who can approve and publish team-wide Skills. Treat Skills like informal applications—they should be tested, documented, and periodically audited.
  • Block or restrict third-party connectors by default until you’ve evaluated each one’s data handling and compliance posture. Microsoft provides controls to manage connector availability at the tenant level.

For everyone else not in Frontier, the update is still a signal worth heeding. You can’t use Cowork yet, but you can prepare your workflows. Identify the tasks you’d happily delegate tomorrow: routine reports, meeting recaps, research briefs, data lookups. Start cleaning your file structures and permissions now, so that when Cowork arrives broadly, your environment is ready rather than messy.

What Comes After Cowork?

Microsoft’s May 5 move makes one thing clear: the company believes the future of productivity software isn’t a suite of apps, but a queue of intentions. You describe what needs to happen, and an AI layer assembles the right tools, data, and people to make it happen. Cowork is the first incarnation of that vision, and its success will depend on two things: reliability at scale and governance that earns IT’s trust.

We can expect Microsoft to expand Cowork beyond Frontier over the next twelve months, likely first to select large enterprises and then to broader Microsoft 365 licensing tiers. The skills library will grow, both from Microsoft and from third-party partners who see an opportunity to embed their services. At the same time, the agentic AI race will intensify—OpenAI, Anthropic, and others aren’t standing still—and the winning system may not be the smartest but the one that best understands the messy, interconnected graph of real workplace data.

For Windows and Microsoft 365 users, the shift from “assist me” to “do it for me” will redefine what it means to be productive. Typing, formatting, and coordinating may fade into the background. In their place will rise the skills of defining tasks clearly, auditing automated outputs, and knowing when a machine should step aside. Cowork isn’t yet that future, but it’s the most tangible step Microsoft has taken toward it.