Copilot Cowork and Copilot Studio Can Now Build Full-Stack Business Apps from Natural Language

Microsoft has added natural-language app building to Copilot Cowork and Copilot Studio. Users describe the app they need, and Copilot generates a working, full-stack application that connects to company data and stays under IT governance. Ryan Cunningham, CVP of Copilot Studio and Power Platform, announced the feature.

Details

• How it works: You describe the business outcome, the users, the data, and the actions you need. Copilot Studio then uses agentic coding to generate an app scaffold, which you can refine through conversation, preview, and inspect at the code level
• Who it’s for: Information workers as well as advanced makers and professional developers
• Data and actions: Apps use connectors and Work IQ for organizational context. They can read data, take actions, and write results back to business systems, all within the Microsoft 365 tenant boundary. Microsoft’s examples include an employee onboarding tracker and a field service app
• Engineering and governance: Apps are full-stack and built on open standards, with Git-backed source control, deployment stages, and version isolation. Microsoft Entra identity and organizational data and connector policies apply by default, and IT admins can manage published apps in the Microsoft 365 admin center
• Sharing: Users can find shared apps at managedapps.cloud.microsoft.com
• Billing: Building and running apps is billed by usage
• Availability: In Copilot Cowork, the feature is available now through the /app skill for Microsoft Frontier program members. In Copilot Studio, it rolls out in public preview over the following week through a new “apps” tile

What happened next

Two weeks later, Microsoft folded this direction into “the new Copilot,” announced on September 25. That launch introduced a dedicated Code experience for building apps and the Copilot Managed Runtime to host apps built in Cowork, Code, and Copilot Studio inside the tenant. The September 10 launch was the first concrete step in Microsoft’s push to make “vibe-coded” internal tools a governed, billable part of Microsoft 365, rather than shadow IT built on outside services.