Copilot Cowork App Builder: Access, Pricing and Copilot Studio Differences

What is the Copilot Cowork App Builder?

Microsoft added natural-language app building to Copilot Cowork and Copilot Studio in September 2026. In Cowork, the feature appears as a built-in App skill, commonly invoked with /app. Instead of beginning with a traditional canvas, data model, or code project, you start by describing the business problem, the users, the data involved, and the actions the app should support.

Microsoft’s current Cowork documentation calls these lightweight, interactive apps that can be created without writing code. Its broader launch announcement goes further and describes apps created through Cowork and Copilot Studio as full-stack apps built using open standards. The difference is useful: the Cowork experience is intentionally lightweight for the maker, while the underlying platform is designed to produce governed business applications rather than temporary chat mockups.

A prompt could be as simple as “Build an app to run my daily scrum with my team.” Cowork can create the app, generate a data schema in supported connectors, connect data sources, let you refine the interface conversationally, preview the result, and publish it for other people in your organization.

Official sources: Microsoft Learn: Build apps with the App skill and Microsoft Copilot Blog: Build business apps with Copilot Cowork and Copilot Studio.

Who can access the Copilot Cowork App Builder?

The most important detail is that Cowork itself is generally available, but app creation inside Cowork is still a Frontier preview. Having a normal Microsoft 365 account is not enough.

Microsoft says Frontier enrollment requires a Microsoft Copilot license and is controlled through the Microsoft 365 admin center. Administrators can go to Copilot → Settings → View all → Copilot Frontier and assign access to all users or selected users. Microsoft notes that a Frontier change can take up to about three hours to appear.

That means a user can have a valid Microsoft 365 Copilot subscription, see Cowork normally, and still not see the App skill because the tenant has not enrolled that user in Frontier.

Official access guidance: Get started with Copilot Cowork and Get started with the Microsoft Copilot Frontier Program.

How to build an app in Copilot Cowork

The workflow is designed to feel more like delegating a software task than manually assembling a low-code application.

1. Open Microsoft Copilot and switch to Cowork. Cowork appears as a toggle next to Chat for eligible users.
2. Describe the business outcome. Explain who will use the app, what information they need, what actions they should be able to take, and which organizational data matters.
3. Invoke the App skill. You can explicitly use /app, or Cowork can invoke the App skill when your request clearly describes an app.
4. Let Cowork generate the first version. The App skill can create the interface and, where supported, generate a data schema and connect the necessary data sources.
5. Refine it conversationally. Ask for changes such as different cards, fields, screens, actions, or layouts. Microsoft says the app updates as you make changes.
6. Open and test it. Preview the app as the eventual user would experience it.
7. Publish and share it. Publishing makes the current version available. In Cowork, you can generate a share link for people in your organization who can use Microsoft 365 Copilot.

This is different from asking an AI model to generate a loose HTML prototype. The app can connect to organizational systems and can write results back through supported connectors, subject to the user’s permissions and the organization’s policies.

What kinds of apps is Microsoft targeting?

Microsoft’s examples are deliberately business-oriented. One example is an employee onboarding tracker that shows onboarding progress, surfaces learning resources, and updates onboarding records. Another is a field service app that retrieves product information from a third-party system, guides the worker through steps, and writes results back to connected systems.

That positioning matters. The current Cowork App Builder is best understood as an internal enterprise app generator, not as a replacement for every kind of consumer web-development platform. Microsoft’s current documentation focuses on apps that live inside an organization, use Microsoft 365 or business data, respect tenant identity and connector policies, and are shared with organizational users.

Useful early scenarios could include project trackers, onboarding dashboards, meeting workflows, service checklists, internal request forms, operations dashboards, inventory views, approval tools, or team-specific utilities that need a structured interface rather than another chat response.

How much does the Copilot Cowork App Builder cost?

There is no separate flat App Builder subscription price announced by Microsoft. The cost has two layers: the license required to use Cowork and the usage consumed by Cowork and the app.

1. Microsoft 365 Copilot license

Copilot Cowork requires the Microsoft 365 Copilot User Subscription License. Microsoft’s current Copilot Studio product page lists Microsoft 365 Copilot at $30 per user per month, paid yearly, subject to market availability and the requirement for a qualifying Microsoft 365 business or enterprise plan.

2. Usage-based Copilot Credits

Cowork then uses Copilot Credits. Microsoft says normal Cowork task cost is determined by the work performed, including model use, context retrieval, tool calls, and runtime. For the new app capability specifically, Microsoft states that app building and app running follow the usage-based billing model.

What Microsoft does not currently publish is a universal number such as “building one app costs 500 credits.” That would be misleading because the amount depends on what the app-generation session does and how the finished app is used. A simple internal tracker and an app that repeatedly uses richer data, models, connectors, and actions should not be assumed to consume the same amount.

The safest way to budget is to treat the $0.01 figure as the price of one pay-as-you-go credit, not the price of an app. Organizations can monitor usage, set spend limits, allocate budgets, and inspect consumption at tenant, group, and user levels.

Official pricing sources: Copilot Cowork is now generally available, Copilot Credit purchase options, and Microsoft Copilot Studio product and pricing page.

Copilot Cowork App Builder vs Copilot Studio: what is the difference?

The easiest mistake is to think Microsoft created one app builder in Cowork and a completely different competing app builder in Copilot Studio. Microsoft says the opposite: the same app-building capabilities can be entered from either Cowork or Copilot Studio. The major difference is the environment in which you start and how much of the broader maker platform you want around you.

So the practical difference is less “simple product versus professional product” and more conversational entry point versus dedicated maker environment. Cowork is the fastest place to start when the thought begins as “I need an app that does this.” Copilot Studio becomes more natural when the app is part of a larger business process involving agents, workflows, development environments, governance, or deeper maker controls.

Microsoft’s launch explanation: Build business apps with Copilot Cowork and Copilot Studio.

How the apps connect to Microsoft 365 and business data

Microsoft is trying to make these generated apps useful inside real organizations rather than isolated prototypes. Apps can use connectors to reach business data and can use Work IQ for organizational context.

This means an app can do more than display a static AI-generated screen. Depending on the connected system and permissions, it can retrieve data, present it in a structured experience, trigger actions, and write results back to business systems.

Microsoft also says the platform respects the user’s identity and the organization’s connector and data policies. In practice, that makes permissions part of the app design. A generated app does not magically grant a user access to data the organization has not authorized.

Publishing, sharing and enterprise governance

An app saves automatically while you work in Cowork. Publishing makes the latest version available to the people you share it with. Microsoft’s Cowork documentation says the maker can generate a share link, similar to sharing a Word document or PowerPoint deck, and send it to people in the organization who can use Microsoft 365 Copilot.

That share step deserves attention because Microsoft warns that a user with the link can open and use the app, including the data available through the app. The normal organizational permission model still matters, but makers should not treat app sharing as a casual public-link feature.

At the administration level, published apps appear in the Microsoft 365 admin center, where IT can see an inventory and apply operational controls. Microsoft also says users will be able to discover shared enterprise apps through managedapps.cloud.microsoft.com.

The app platform is also designed for a more conventional software lifecycle than a disposable AI artifact. Microsoft says apps can use Git-backed source control, deployment stages, and version isolation, allowing a team to work on the next version without disrupting the live version.

Why you may not see the /app skill or App tile yet

If Microsoft’s announcement says the feature exists but you cannot find it, that does not automatically mean your account is broken.

• You may not have Microsoft 365 Copilot. Cowork requires an active Microsoft 365 Copilot license.
• Cowork may not be enabled for your account. Your organization controls availability.
• Usage-based billing may not be configured. Microsoft lists Cowork billing as a prerequisite.
• You may not be enrolled in Frontier. The Cowork App skill is currently Frontier-only.
• Your Frontier change may still be propagating. Microsoft says enrollment changes can take up to about three hours.
• The Copilot Studio App tile may still be rolling out. Microsoft announced the Studio experience on September 10 with public-preview rollout over the following week.

For Cowork specifically, the most useful check is with your Microsoft 365 administrator: confirm that your license is assigned, Cowork and its billing are enabled, and your user is included in the tenant’s Frontier configuration.

What to know before treating this as a finished app platform

The App Builder is new enough that expectations should stay realistic. Microsoft labels the Cowork App skill as preview functionality and explicitly warns that preview features can have restricted functionality, can change over time, and are not guaranteed to reach general availability in their current form.

Three limits matter most today. First, Microsoft’s current documentation is focused on enterprise and organizational apps, not anonymous consumer websites. Second, pricing is usage-based rather than a simple fixed app fee, which means teams need cost visibility before scaling usage. Third, generated software still needs human review: data access, actions, security boundaries, workflow correctness, and the user experience all need to be tested before a business process depends on the app.

Microsoft’s launch post also emphasizes that advanced makers and developers can inspect underlying code. That is a useful reminder that natural-language generation reduces the amount of manual construction required; it does not eliminate the need for software judgment.

Should you start in Cowork or Copilot Studio?

Start in Copilot Cowork when the need begins as a work problem and you want to get from a description to a usable internal app with the least ceremony. It is especially attractive when the app is closely tied to Microsoft 365 context and the person building it is an information worker rather than a dedicated app maker.

Start in Copilot Studio when you already know the app is part of a broader automation or agent project, need to work alongside agents and workflows, want a dedicated maker environment, or expect deeper lifecycle and structural control to be central from the beginning.

Neither path locks you into a fundamentally different class of app. Microsoft’s own announcement stresses that the same core capabilities underpin both experiences. The strategic shift is that Microsoft is making business-app creation available at the point where the idea appears: a conversation in Cowork for everyday users, or the Copilot Studio environment for makers building a larger solution.