Copilot Code: building an application with SharePoint

Building a business interface on top of a SharePoint list no longer necessarily means developing the whole application by hand. Copilot Code turns a natural-language description into an application, but its preview status, billing and permission model call for a few checks before you get started.

Copilot Code remains a Frontier feature

Copilot Code is a tab in Microsoft Copilot, the new name for the Microsoft 365 Copilot app. According to the Microsoft Learn documentation, it can produce applications, dashboards, internal tools, static sites or scripts from a description, then display a live preview.

As of 28 October 2026, Microsoft Learn still restricts this feature to the Frontier programme, the channel that provides access to preview experiences. On 25 September 2026, Microsoft announced that it would arrive in Frontier at the end of the month, followed by wider availability in the following weeks. It is therefore safer to rely on the status shown in the documentation rather than on the forecast timeline in the Home, Code and Autopilot announcement.

Access requires a Microsoft 365 Copilot (Premium) licence and usage-based billing through Copilot Credits being enabled. Copilot Code is not a feature included at no extra cost in the monthly licence.

The Microsoft Copilot app now uses the main address copilot.cloud.microsoft. Administrators must allow *.cloud.microsoft in their filtering mechanisms to avoid a network block. Our analysis of the new generation of Microsoft Copilot also places Code alongside Home and Autopilot.

Four concepts to distinguish before you start

Copilot Code brings together a generation interface, a credit system and a runtime environment. These elements are linked, but they do not address the same need.

Copilot Managed Runtime can be compared to a managed workshop in which the application is installed and run. The analogy stops at hosting, however: this environment does not on its own decide who can view the SharePoint data, because the source's permissions continue to apply.

Microsoft also states that App Builder is being replaced. Older applications can be rebuilt in Copilot Cowork, also offered in Frontier with a Copilot licence, or in Apps in Copilot Studio, in public preview. Both destinations use Copilot Credits; our guide on creating an application with Copilot Cowork lets you compare the approaches.

A business prompt beats a simple application request

Take the case of a team that tracks its invoices in a SharePoint list, that is, a structured data table stored in Microsoft 365. The list contains, among other things, the invoice ID, customer, amount, status, priority and due date.

A request that is too vague, such as "create an invoicing application", leaves the artificial intelligence (AI) to decide many elements on its own. A better prompt describes the source, the objective, the expected screens and how to handle ambiguities:

Create an application named Project Green Space Invoice Tracker and connect it to the indicated SharePoint list. This list contains the project's submitted and settled invoices. Provide a tab to view invoices, a form to add them and an analytics dashboard. Add filters by status, priority and due date, with selection by month and year. If any information is missing, ask me a question before choosing.

This wording provides enough context to produce a usable first version. Excel documents and sheets can also be attached to enrich the request, but they do not replace an explicit description of the business rules.

The prototype may then choose to load invoices in batches, make certain fields mandatory or assign colours to statuses. These generated decisions should be considered proposals: the business owner must validate them before publication.

Building, correcting and testing the application

Publishing and sharing without bypassing permissions

Once published, the application can be opened outside the build interface and shared with named users or, if the need justifies it, more widely across the organisation. For an application containing financial data, named sharing is preferable to a link accessible to all employees.

Sharing the application does not automatically grant access to the SharePoint list. On first opening, each user authorises the connection with their own account; their SharePoint rights then determine which data they can actually read or modify.

This separation works like two successive doors: the first gives access to the application, the second to the data. The analogy stops at access controls, because running the application can also consume credits even if the user already has the necessary permissions.

Applications created or received appear in the "My apps" area. After publication, always test with a representative user: the creator's account often has broader rights than the intended audience.

The build cost is only part of the bill

In the invoice-tracking scenario, the first build took less than 15 minutes and cost less than 3 dollars. This result describes one specific prototype: it is neither a guaranteed price nor an estimate of running costs.

Microsoft Learn states that cloud applications running in Copilot Managed Runtime require a Power Apps Premium plan or credits. Each application programming interface (API) call, that is, each automated exchange with a service, consumes 0.1 credit, plus a cost at each launch.

Credits are pooled at tenant level, that is, the organisation's Microsoft 365 environment. Administrators track them in the Microsoft 365 admin center under Copilot > Cost management. The documentation on usage-based billing also mentions a one-year prepaid plan called P3.

Finally, the Copilot Code security card states that the tool can run locally or in an isolated cloud environment. Complex projects with many dependencies may not be built correctly; Microsoft therefore recommends limited iterations and a rollback in case of failure.

Frequently asked questions

Is Copilot Code available to all Microsoft Copilot users?

No. As of 28 October 2026, Microsoft's documentation still places it in the Frontier programme. Its presence also depends on the licence and the tenant configuration.

Is the Microsoft 365 Copilot licence enough?

No. Copilot Code requires a Microsoft 365 Copilot (Premium) licence as well as usage-based billing through Copilot Credits. The build is not included at no extra cost in the licence.

Does sharing the application give access to the SharePoint list?

No. The user must sign in with their own account and keep the necessary rights on the SharePoint list. Sharing the interface and authorising data access are two separate controls.

Can Copilot Code be used for a critical application?

Copilot Code and Copilot Managed Runtime are still in preview. Critical use therefore requires, at a minimum, functional validation, a permissions check, a credit budget and a rollback procedure.

Three decisions to make before the first project

If your organisation does not yet master usage-based billing, start with a pilot limited to a few users and a reversible data source. If it already has Power Platform and Copilot governance, add Copilot Code to that framework rather than creating a parallel process.

Going further

• Copilot Code (Frontier) – Microsoft Learn documentation — to check prerequisites, getting started and publishing.
• Copilot Code application card — to review consents, limitations and security controls.
• Copilot Credits cost management — to track and manage tenant consumption.
• Announcement of Home, Code and Autopilot — to understand Code's place in Microsoft Copilot.
• Microsoft Copilot Managed Runtime SDK — to dig deeper into hosting, execution and associated licences.