Microsoft launches Copilot Studio /app commands and Copilot Cowork agent builder

On September 10, 2026, Microsoft announced natural-language app building in Copilot Cowork and Copilot Studio, authored by Ryan Cunningham, Corporate Vice President, Copilot Studio and Power Platform (Microsoft Copilot Blog, "Build business apps with Copilot Cowork and Copilot Studio," Sep 10, 2026). Two tracked pieces:

1. Copilot Cowork — /app skill (Frontier): A new built-in /app skill lets users describe an app in plain language inside Cowork chat and get a working, lightweight interactive app without writing code. Available to Microsoft 365 Copilot customers enrolled in the Microsoft Frontier program (Message Center MC1469329, Sep 8, 2026; Microsoft Learn "Use Copilot Cowork," updated Sep 14, 2026).
2. Copilot Studio — native app building (public preview): Copilot Studio's home screen gains an "App (Preview)" tile; makers pick it, describe business outcome/users/data/actions, and Copilot Studio uses agentic coding to scaffold a full-stack app. Access rolled out in public preview "over the next week" (i.e., during the research window Sep 10–17).

Supporting sequence (FACT, all primary): Microsoft 365 Message Center notice MC1469329 published Sep 8, 2026 ("Build apps in Microsoft Copilot Studio and Copilot Cowork"); independent analyst brief Constellation Research, Sep 8, 2026; Microsoft Tech Community "Managing apps built in Copilot Studio" (Sep 15, 2026) confirming the prior-week announcement and detailing admin governance; Microsoft Copilot Credits Guide (Sep 17, 2026) listing "Build apps in Microsoft Copilot Studio (Paid Public Preview)" and "Build apps in Copilot Cowork (Microsoft Frontier Program)" as billable services.

• Organizations get a new way to build applications: full-stack business apps created from conversational descriptions, in the same trusted environment where they already build agents and workflows (Copilot Studio) or from chat (Copilot Cowork /app).
• Apps, agents, and workflows converge in one studio. Copilot Studio previously hosted agents and agent flows; it now hosts apps as first-class artifacts, so a business process can combine an interactive app, a conversational agent, and a workflow in one solution (e.g., employee onboarding: app for tasks/due dates, agent for Q&A, workflow that updates the onboarding system).
• App creation is on by default in both paths; admins can turn each path on/off from the Microsoft 365 admin center (Tech Community, Sep 15).
• New billing surface: building and running apps meter separately through Copilot Credits (usage-based billing), with per-user credit caps (uniform or by group); a Power Apps Premium license absorbs runtime usage within existing request limits (Tech Community, Sep 15; Copilot Credits Guide, Sep 17).
• New governance surface: published apps appear in the Microsoft 365 admin center inventory (builder, lifecycle state, data sources/connectors, policies, usage metrics) with block/disable/share-control/retire actions.

Before (pre-Sep 2026):

• Copilot app creation existed as the App Builder agent (introduced Oct 2025 for Frontier customers): lightweight apps grounded in Microsoft Lists, canvas-style, shared by link.
• Copilot Studio was the agent/workflow platform: build agents with natural language or a low-code graphical canvas, connect 1,100+ connectors, publish to Teams/websites/M365 Copilot.
• Full-stack, production-grade apps generally required Power Apps or pro-code tooling; app lifecycle (source control, deployment stages) lived outside the assistant context.
• Cowork (GA June 16, 2026) executed long-running multi-step tasks across Microsoft 365 but did not build applications.

Change (Sep 10, 2026):

• /app skill in Cowork: chat-described apps, refined conversationally, previewed beside the chat.
• Copilot Studio native app building: App (Preview) tile, natural-language brief → agentic coding → scaffold → iterate → publish.

After:

• Non-programmers can produce governed, full-stack apps with Git-backed source control, deployment stages, and version isolation on Microsoft-hosted infrastructure — no pipeline setup.
• IT admins inventory, cap cost, and control both creation paths in the admin center; users discover shared apps at managedapps.cloud.microsoft (company claim per announcement; app runtime surface confirmed in blog).
• Microsoft 365 Copilot becomes an app-factory as well as an assistant and agent runtime; Copilot Credits becomes the metering layer for build + run.

Per the Sep 10 announcement and Sep 14 Learn documentation (FACT where described, COMPANY CLAIM where asserted as capability):

• Copilot Studio path: open Copilot Studio → choose App (Preview) → describe the business outcome, users, data, and actions. Copilot Studio applies agentic coding to turn the intent into a working app scaffold. Makers iterate in natural language, inspect the app in preview, and can review the underlying code (information workers stay at solution level; advanced makers/developers can go deeper).
• Copilot Cowork /app path: in Cowork chat, invoke the /app skill ("Build an app to run my daily scrum with my team"). Cowork references Microsoft 365 data (documents, spreadsheets, meetings, messages), generates a data schema in supported connectors, builds the app with data sources connected, and updates it live as the conversation continues. The app preview renders beside the conversation.
• Data and identity: apps use connectors (incl. Work IQ for organizational context) and respect Microsoft Entra identity and connector policies by default. Apps are created in the maker's personal developer environment following existing environment-routing policies; connected data is accessed on behalf of the signed-in user.
• Enterprise plumbing: full-stack apps use open standards, Git-backed source control, deployment stages, and version isolation. Microsoft hosts the infrastructure; no provisioning or pipeline configuration required (company claim).
• Publishing and sharing: apps publish to the organization; users discover them at managedapps.cloud.microsoft. Sharing is link-based like a Word document ("Anyone with the link can open and use the app, including all its data" — Learn, an important security caveat).
• Admin controls: Microsoft 365 admin center → Apps → Overview: "Choose where people can make apps" (Copilot Studio path recommended/on by default; Cowork path gated by Frontier); app inventory; block/disable/retire/restrict sharing; credit caps per user or per group; separate build vs. runtime meters.
• Billing: build and runtime each consume Copilot Credits; Power Apps Premium license covers runtime within request limits; beyond limits or without license, runtime bills via Copilot Credits (Tech Community, Sep 15).

• Democratization at the largest enterprise software vendor: Microsoft puts working, governed application development within reach of information workers — the same population that was earlier given agent-building. This is a step-change in who can ship software inside an organization.
• Apps + agents + workflows unify: Copilot Studio stops being only an agent platform. Microsoft is explicitly competing to be the one place a business process gets its interactive UI, its conversational layer, and its automation — a direct shot at the "composable enterprise app" market held by Power Apps, ServiceNow, Salesforce (which launched its own agent platform AIforce later the same week, Sep 15), and low-code players.
• Governance is the moat: rather than letting natural-language app generation produce shadow IT, Microsoft wraps it in Entra identity, connector policies, admin-center inventory, credit caps, and lifecycle controls. Enterprise buyers' central objection to generative app-building (sprawl, data exposure, cost) is answered with admin surfaces — a credible enterprise argument.
• Copilot Credits become a real software-spend category: build + runtime metering extends usage-based billing to a new artefact class inside M365, changing cost governance conversations for Copilot deployments.

• A non-programmer can go from "I need an onboarding tracker for my team" to a published, governed, data-connected app in a single conversation — then hand it to IT to observe, cap, block, or retire.
• Teams can compose an end-to-end business process in one platform: interactive app + agent + workflow (e.g., onboarding, field-service guided steps with write-back to third-party systems).
• Admins can run a governed "citizen app factory": choose where apps can be made (Studio vs. Cowork), set per-user maker budgets, and review the whole app estate in one inventory.
• Apps built in Cowork can be opened and further edited in Copilot Studio (Message Center MC1469329), giving a low-friction path from casual chat prototype to formal production artifact.

• GA timeline for both paths, and whether /app remains Cowork-only or becomes a Copilot-wide capability.
• Environment-level credit caps and more granular cost controls (promised as "when they arrive").
• Interop: how far editing a Cowork-built app in Copilot Studio goes; whether apps can export to Power Apps/pro-code pipelines cleanly; MCP/tooling breadth.
• Third-party connector coverage for the new apps and whether Work IQ grounding works consistently outside Microsoft 365 data.
• Market reaction: whether enterprises adopt app-building inside Copilot Studio or keep Power Apps/ServiceNow/Salesforce for production workloads — and how Microsoft prices GA versus OpenAI Agents API and Salesforce AIforce.
• Security track record: how Microsoft's "publishing never grants new data access" claim holds under real-world sharing and delegated scenarios.

• Rollout completes: Copilot Studio app building reaches all eligible environments in the days following Sep 10 (already happening within the research window; the Sep 15 admin guidance post implies broad rollout).
• Pricing and GA decisions: watch for GA announcements, environment-level credit caps, and any Copilot Credits rate changes for build/runtime meters (Copilot Credits Guide already lists both as of Sep 17).
• Ecosystem deepening: expect more connectors, MCP support for apps, and deeper Work IQ grounding; a path toward Power Apps/export interop is plausible.
• Competitive response: OpenAI and Salesforce will answer the governed-citizen-app angle; Microsoft will likely tout adoption metrics at Ignite (late 2026).
• First field evidence: independent reports on generated-app security, cost, and quality should appear within a quarter; regulators may scrutinise the "everyone is a maker" model for DLP/audit gaps.

Microsoft's Sep 10 move is one of the clearest signals yet that the enterprise software factory is becoming conversational — but the story is as much about governance as generation. By wrapping natural-language app creation in Entra identity, admin-centre inventory, credit caps, and lifecycle controls, Microsoft converts the "anyone can build" promise from a shadow-IT nightmare into a managed platform feature. For enterprises, the question is no longer whether employees will describe apps into existence; it is whether IT can govern, cap, and audit the estate before the first "anyone with the link can open the app, including all its data" incident teaches that lesson the hard way. The /app command is the headline; the admin centre is the substance.