To put a Copilot Studio agent inside a Power Apps app in 2026, publish the agent to Teams and Microsoft 365, then turn on Microsoft 365 Copilot for the app. Users open Copilot in the app and pick the agent.
Older guides still say to insert a Chatbot control. That control is gone, and since February 2, 2026 the Copilot control can’t be added to new canvas apps either.
In this tutorial, we’ll add a Copilot Studio agent to Power Apps the current way, cover model-driven and code apps, and fix a missing Copilot button. I did every step today, and I’ll show you exactly where it stopped.
The Sample App and Agent We’ll Use
- Service Desk Demo, a canvas app on our SharePoint Service Requests list (one list, which matters later).
- SPGuides IT Help Desk, a Copilot Studio agent. No agent yet? Create a new agent in Copilot Studio first.
- Our default environment, in a region the canvas app rollout hasn’t reached yet. Keep that in mind.
What Happened to the Chatbot Control?
In Power Apps Studio, I searched the Insert pane of the same app for “chatbot”, “chat”, “copilot” and “agent”. Every search returned No match found:

Learn now says existing apps keep the old Copilot control for a limited time, and Microsoft Copilot in canvas apps replaces it. That’s what we’ll set up.
Method 1: Add the Agent to a Canvas App Through Microsoft 365 Copilot (Recommended)
Use this for any canvas app. Publish the agent, switch the feature on for the environment and the app, then publish the app.
Step 1: Publish the Agent to Teams and Microsoft 365
In Copilot Studio, open the agent, select Publish > Add channel and pick Teams and Microsoft 365:

Under availability, choose Microsoft Copilot and Microsoft Teams (the app’s Copilot uses agents that are available in Microsoft Copilot):

Select Add channel, then Publish agent:

Ours showed “Your agent published successfully” and a Published badge:

Step 2: Turn On Microsoft 365 Copilot for the Environment
A Power Platform admin does this once. In the Power Platform admin center, go to Copilot > Settings. Under Power Apps, the section is now called Copilot in apps:

Open Microsoft 365 Copilot, pick the environment, select Edit setting, set canvas apps to On and save. Both switches were already on in ours:

Step 3: Turn On M365 Copilot in the Canvas App
Here’s the catch: on make.powerapps.com, the app’s Settings > General page has no Copilot option. Open the same app on make.preview.powerapps.com, and you’ll find M365 Copilot in canvas apps (Preview) with Default, On and Off:

Set it to On and select Save. We got “All changes are saved.”:

Step 4: Publish the App
Studio’s Play mode won’t show Copilot, because the setting only applies to the published app. Select Publish > Publish this version:

I then played the same app on apps.powerapps.com and apps.preview.powerapps.com. The header had Share, full screen, download, settings, help and my profile, but no Copilot button:

Important: That’s the regional rollout, not a missed step. Learn says the feature might not be available in your region yet, and our environment’s region doesn’t have it so far.
Step 5: Open Copilot and Pick Your Agent
Once the button arrives, Learn says users select Copilot near the upper-right corner, then choose an agent from the navigation panel or @mention it. I’ll add that screenshot when it reaches our tenant.
How does this work?
The agent isn’t placed on a screen. It’s published into Microsoft Copilot, and the app’s Copilot pane opens Microsoft Copilot, which is why Step 1 needs that availability.
With no agent picked, Copilot answers about the single Service Requests list. Pick SPGuides IT Help Desk and the agent answers instead, without the list data unless you configure it. Remove the selection to get list answers back.
If You Don’t See the Copilot Button
Same Service Desk Demo app, same setup. Check these in order:
- Region. The preview is rolling out by region; check your environment’s region in the admin center.
- Preview site. The app setting is only on make.preview.powerapps.com.
- Both switches. The admin center setting and the app setting must both be On.
- Publish. Play the published app, not Studio’s Play mode.
- License. Each user needs a Microsoft 365 Copilot license.
- Tenant and search. The tenant must allow Dataverse data available in Microsoft Copilot, and Dataverse Search must be Default or On.
- Mobile. The Power Apps mobile app isn’t supported; test in a browser.
Method 2: Add the Agent to a Model-Driven App
Model-driven apps use the same admin center setting. In the app editor, go to Settings > Features, turn on Microsoft Copilot in model-driven apps, save and publish. Users select Copilot > Chat and pick the agent.
Users need a Power Apps premium license plus a Microsoft 365 Copilot license. The app designer’s Agents tab (preview) also adds autonomous agents that use the Power Apps MCP server, in model-driven apps only.
How does this one work?
It’s the same Microsoft Copilot pane, grounded in Dataverse tables. Our app is SharePoint-based, so Method 1 is ours.
Method 3: Call the Agent From a Code App
In a Power Apps code app, add the Microsoft Copilot Studio connector and call the published agent with ExecuteCopilotAsyncV2 (Execute Agent and wait). Learn’s command:
pa app add data-source --connector "shared_microsoftcopilotstudio" --connection-id <connectionId>
How does this code work?
It adds the connector to power.config.json and generates a TypeScript service. Your code sends the user’s text with the agent name and reads lastResponse. You build the chat UI yourself.
Which Method Should You Use?
| Your app | Use | Why |
|---|---|---|
| Canvas app | Method 1 | The supported replacement for the old controls |
| Model-driven app | Method 2 | Same pane, Dataverse data |
| Code app | Method 3 | Full control over the chat UI |
Pro Tip: Not sure you need Copilot Studio? Read Microsoft 365 Copilot vs Copilot Studio; a custom agent in Agent Builder also shows up in Microsoft Copilot.
Things to Keep in Mind
- One data source type. SharePoint or Dataverse, not both, and only single-list SharePoint apps get answers in the preview.
- No environment-variable lists. Copilot won’t reference a list the app reaches through an environment variable.
- Read-only. Copilot only views data; to change records, give the agent its own tools.
- No app context yet. Agents can’t use in-app user context, so write clear instructions.
For the app side, browse our Power Apps tutorials. The agent side lives in our Copilot Studio tutorials.
For a guided path, the Copilot Studio training course covers agents end to end. Want the agent on a web page too? See how to publish an agent to a live or demo website.
If you’re building the agent side next, these help:
Frequently Asked Questions
Can I still add a Chatbot control to a Power Apps canvas app?
No. The Chatbot control is gone from the Insert pane, and since February 2, 2026 you can’t add the Copilot control to new canvas apps. Microsoft Copilot in canvas apps replaces it.
How do I add a Copilot Studio agent to a Power Apps canvas app?
Publish the agent to Teams and Microsoft 365 with Microsoft Copilot availability, turn on Microsoft 365 Copilot for the environment and in the app on make.preview.powerapps.com, then publish. Microsoft lists the prerequisites in Add Microsoft Copilot for app users in canvas apps.
Why don’t I see the Copilot button in my Power Apps app?
The preview is rolling out by region. Also check both settings, publish the app, confirm users have a Microsoft 365 Copilot license, and test in a browser instead of the mobile app.
Does this work in model-driven apps?
Yes. Use the same admin center setting, then turn on Microsoft Copilot in model-driven apps under Settings > Features. See Add Microsoft Copilot for app users in model-driven apps.
Can the agent update SharePoint list data from the app?
Not through Copilot alone. Microsoft Copilot in canvas apps is read-only, so the agent needs its own tools, such as an agent flow, to change records.

Hey! I’m Bijay Kumar, founder of SPGuides.com and a Microsoft Business Applications MVP (Power Automate, Power Apps). I launched this site in 2020 because I truly enjoy working with SharePoint, Power Platform, and SharePoint Framework (SPFx), and wanted to share that passion through step-by-step tutorials, guides, and training videos. My mission is to help you learn these technologies so you can utilize SharePoint, enhance productivity, and potentially build business solutions along the way.