Copilot Explainers · 7 min read

Apps in Copilot Studio: what they are, what preview means and what they cost to run

James Wilkinson

By James Wilkinson 30 October 2026

Copilot Studio can now build a working app from a plain-language description. What an app is for beside an agent, the two routes in, where the data lives, what preview limits and what it draws in Copilot Credits.

TL;DR
  • An app in Copilot Studio is a simple screen your team opens in the browser, built from a plain-language description and refined by describing what should change. The agent does the work; the app is where people see it, check it and approve it.
  • Two routes in. An App (Preview) tile in Copilot Studio, which needs the new Copilot Studio experience switched on and usage-based billing. Or the App skill in Copilot Cowork, started with /app, which needs the firm to be in Microsoft's Frontier programme.
  • The choice of connector is the choice of database. Settle where the data lives before the first description.
  • Apps are in preview. A generated app can be incomplete or wrong, the code view is read-only and sharing the app does not share the data behind it.
  • Building and running an app both draw Copilot Credits. People with Power Apps Premium have running the app included, but AI inside the app draws credits either way.

An app is a simple screen your team opens in the browser: a form to fill in, a list to work through, a button to approve. In Copilot Studio you describe the app in plain language and it builds a working first version, which you then refine by describing what should change. Microsoft puts apps alongside agents and workflows, so together they cover a whole piece of work: the agent does the checking and drafting, a workflow does the routine steps and the app is where your team sees what happened, checks it and approves it.

This post is the factual version: what an app is for, the two routes in, where the data lives, what preview means and what it costs. Nothing here is a Microsoft price; the current rates are in the Copilot Credits rate card.

What an app is for, beside an agent

Four examples that come up in professional services firms, each a screen beside an agent that does the work.

  • An intake form for new work. A new matter or job comes in through one form with the fields your team always needs, instead of an email chain. The onboarding agent starts from the form.
  • A team’s deadline tracker. Every deadline for one team on one screen, with who owns it, what is due this week and what is overdue. The chasing agent keeps it current.
  • A screen for approving drafts. A partner sees what an agent drafted, changes it if needed and approves it, with a record of who approved what.
  • A simple pipeline for one team. Contacts, opportunities and next steps for one team, in place of the spreadsheet everyone edits.

The pattern in each is the same. The app is not the clever part. It is the place where a person sees the agent’s work and decides.

Two routes in

Copilot Studio. An App (Preview) tile on the Copilot Studio home page. It needs the new Copilot Studio experience switched on and usage-based billing set up for your firm. The app is built in the personal environment of the person making it.

Copilot Cowork. An App skill, started with /app. It needs your firm to be in Microsoft’s Frontier programme. Apps built in Cowork can be opened and edited in Copilot Studio.

Both use the new Copilot Studio experience, the GitHub Copilot harness, which is why everything about them draws credits. Which harness your agents are built on matters here, because the choice is permanent and an app sits beside the agents it works with.

Describing it so the first version is close

What it is for, who uses it, what data it holds and what people do on it. A clear description gets a first version that is close, which saves rounds of changes later. Changes are made by describing what should be different, then testing in the preview on your own cases, including the awkward ones. The code view is read-only, and complex apps need building in steps, so build one small app well rather than a large one badly.

Where the data lives

An app keeps its data through a connector, so the choice of connector is the choice of database. Settle it before the first description, with the permissions and backups that come with it. For most firms that means a SharePoint list, with the permissions check a Firmwide install does in its foundation step, so an app built later has something reliable to work from.

Who can open the app and who can see the data behind it are separate questions. Sharing the app does not share the data, so both are set on purpose.

What preview means

Apps in Copilot Studio are a paid public preview that Microsoft is rolling out gradually, so they may not be switched on for your firm yet. In practice:

  • A generated app can be incomplete or wrong, so everything is tested on your own cases before anyone relies on it.
  • The code view is read-only. Changes are made by describing them.
  • Complex apps need building in steps.
  • Sharing an app does not automatically give people access to the data behind it. Data permissions are set separately.
  • Features and pricing can change before general availability.

So build a pilot now, and keep client data in your existing systems until apps are generally available and your app has been tested on your own cases. What carries over when preview ends is the discipline: describing an app well, choosing where its data lives, testing it on your own cases and sharing it safely.

What it costs to build and run

Building an app and running it both draw Copilot Credits. People with Power Apps Premium have running the app included, but AI inside the app, such as an agent it calls, draws credits either way. Without Power Apps licences, running the app draws credits too, so it is worth knowing which licences the firm already holds before deciding which route to use.

Power Apps is still the right home for a governed app on Dataverse, with its own tools and licences. An app in Copilot Studio is generated from a description and paid for by usage, which suits a small, well-defined app that needs to exist quickly. Apps in Copilot Cowork and Copilot Studio: build a CRM without buying Dynamics compares them in more detail.

And Copilot Code

Copilot Code is a tab in Copilot where anyone can describe an app or automation and get one, and it runs on the same Microsoft hosting as apps from Cowork and Copilot Studio. The difference is where the app sits: in Copilot Studio it sits beside the agents, which is where an app for a firm’s process usually belongs. Copilot Code and the managed runtime covers the rest.

In a Firmwide install, an app is built where an agent needs a screen: a form to start the onboarding agent, a tracker the chasing agent keeps current or a place to approve what an agent drafted. How the agents are put together is the technical page for your IT lead.

Related reading

More on Copilot Explainers

Copilot Explainers Copilot Code and managed runtime: anyone in your firm can build an app now. Who owns it? Copilot Code lets anyone describe an app or automation and get one, running on Copilot Managed Runtime inside your tenant. What it is, what it costs and where Copilot Studio still fits. Copilot Explainers What AI models does Microsoft Copilot use? The current list, by surface Which models power Microsoft Copilot (formerly Microsoft 365 Copilot) right now in Chat, Word, Excel, PowerPoint, Cowork and Copilot Studio, how each is billed and the admin and UK data points. Kept up to date. Copilot Explainers Copilot Chat vs Cowork: what's actually different? Microsoft 365 Copilot can already draft emails and manage your calendar. So what does Cowork add? The difference explained, including the agentic harness. Copilot Licensing Apps in Copilot Cowork and Copilot Studio: build a CRM without buying Dynamics Copilot Cowork and Copilot Studio now build a working app from a description. What it means for firms paying for Dynamics they barely use, and what it costs in credits. Copilot Licensing Copilot Credits explained: what each Microsoft workload costs in October 2026 Copilot Credits in one page, from Microsoft's October 2026 guide. How to buy them, what Cowork, Code, SharePoint, Copilot Studio, Teams Phone Agent, apps, Work IQ and Dynamics draw and what the licence covers. Automation Which Copilot Studio harness should your agent be built on? An agent harness explained in plain English, why the GitHub Copilot harness costs more and how to decide which harness each agent build belongs on. The install Firmwide A fixed-price install, typically six to eight weeks: Copilot made safe and useful in your Microsoft 365, an agent and a skills pack for every department, handed over with training. Then Run keeps it working.

Common questions

Questions about Copilot Studio apps

What is an app in Copilot Studio?
A working app that Copilot Studio builds from a plain-language description of its purpose, its users, its data and what people do on it. You refine it in conversation, test it in the preview, then publish it and share it, and published apps show up for your admins in the Microsoft 365 admin centre. Microsoft positions apps alongside agents and workflows, so the agent does the work and the app is the screen where your team sees it, checks it and approves it.
How is it different from Power Apps?
Power Apps builds apps inside your Power Platform environments, with its own tools and licences, and it is still the right home for a governed app on Dataverse. An app in Copilot Studio is generated from a description and paid for by usage, which suits a small, well-defined app that needs to exist quickly.
Do we need to be in Microsoft's Frontier programme?
No. The Frontier programme is only needed for the /app skill in Copilot Cowork. Apps in Copilot Studio need the new Copilot Studio experience switched on and usage-based billing set up for your firm.
Do apps use Copilot Credits?
Yes. Building an app and running it both draw Copilot Credits. People with Power Apps Premium have running the app included, but AI inside the app, such as an agent it calls, draws credits either way. Microsoft's rates change, so the current figures are in our Copilot Credits rate card.
Is it ready for client data?
Not as the system of record yet. A generated app can be incomplete or wrong, and sharing an app does not automatically give people access to the data behind it. Build a pilot now, and keep client data in your existing systems until apps are generally available and your app has been tested on your own cases.