Microsoft lets you build full-stack business apps through conversation in Copilot Cowork and Copilot Studio
Microsoft's new app-building experience lets you describe a business app in plain language and deploy it without writing code, grounded in your org's data.
Microsoft has extended its agentic authoring ambitions in a meaningful direction. From 8 September 2026, users in the Frontier programme can describe a business application in plain language inside Copilot Cowork and get a working, deployable, full-stack app out the other side. The same capability is rolling out to Copilot Studio in public preview over the following weeks. No coding required at any point.
This matters because generating a prototype is the easy part. The harder problem has always been making an app that connects to real business data, respects your organisation’s security policies, and fits into the processes people actually use. Microsoft is claiming this experience does all three from the start.
How it works
There are two ways in. In Copilot Cowork, you type /app in a chat and describe what you want to build. In Copilot Studio, you choose App (Preview) from the home screen. From either entry point, you describe the business outcome you are after: the users it serves, the data it needs, and the actions it should take.
From that description, Copilot Studio’s agentic coding generates a working scaffold. The underlying model is GPT-5, and it is not optional for this feature. You can then preview the app, iterate on it in natural language, or inspect the code directly if you want that level of control. When you are satisfied, you publish it.
Apps built this way are not throwaway prototypes. They use open standards, support Git-backed source control, deployment stages, and version isolation. That last point means you can keep improving a next version without disrupting the live experience for users.
Connectivity is built in from the outset. The tool can create a data schema and connect to supported sources such as SharePoint. It also taps into Work IQ, the intelligence layer behind Microsoft 365 Copilot, which gives the app access to organisational context including documents, spreadsheets, meetings, and messages. Apps can read and write back to connected systems, so they are not just dashboards.
Apps created in Cowork can be opened and further edited in Copilot Studio, which means you are not locked into one surface.
What this means for people who build things at work
The experience is aimed squarely at the person who has a clear problem to solve but no interest in writing code. Someone managing a supplier approval process, running an employee onboarding programme, or tracking project milestones across teams can now describe what they need and get something usable quickly.
To make that concrete: an onboarding solution could combine an app showing tasks and due dates, a conversational agent that answers questions using company documentation, and a workflow that updates the HR system when tasks are completed. All of that is buildable from within Copilot Studio without switching tools.
For people who do want to go deeper, the code is accessible. The intent is that information workers and professional developers can both use the same experience, just at different depths.
What IT administrators need to know
The app-building experience in Copilot Cowork is in preview through the Frontier programme and requires a Microsoft 365 Copilot licence and usage-based billing. The Copilot Studio experience will be enabled by default for eligible makers when it reaches public preview, but administrators can turn it on or off in the Microsoft 365 admin centre and limit access to specific security groups.
Governance is built in rather than bolted on. Microsoft Entra identity is applied by default, and organisational data connector policies are respected throughout. During development, apps run in a sandboxed personal environment, so there is no risk of an in-progress build touching live infrastructure. Once published, IT gets a centralised inventory of apps in the Microsoft 365 admin centre alongside operational controls for managing them across their lifecycle.
One thing worth noting for admins scoping the rollout: the App Builder feature accessed through Microsoft Copilot (as opposed to Copilot Studio) is currently limited to English and the United States.
The broader shift this represents
Microsoft has been moving away from encouraging customers to build through traditional low-code tools like Power Platform and towards a model where the AI does the heavy lifting. Copilot Cowork is reportedly the fastest growing feature in the history of the Frontier programme, and this update extends what users can build there from workflows and agents into full custom applications.
The significance of that shift is practical. Previously, connecting AI-generated outputs to real enterprise systems, data sources, and security policies required either a developer or a reasonably technical power user. The claim here is that the connection layer is handled by the platform, meaning the person closest to the business problem can build the solution without a handoff.
Whether the reality matches that claim in practice will become clearer as the public preview expands. The Message Center announcement (MC1469329), last modified on 9 September 2026, confirms the Cowork rollout ran from 8 September to 14 September 2026. The Copilot Studio experience is expected to follow in the weeks after that.
If your organisation is already in the Frontier programme, the /app skill is worth trying with a real process rather than a toy example. The governance controls are in place, the environment is sandboxed, and the fastest way to understand what this can and cannot do is to describe something your team actually needs.