Existing Copilot Studio Agent to Power Pages Site

Add an Existing Copilot Studio Agent

to Your Power Pages Site

Muhammad Uzair Power Platform Consultant  |  Power Pages  |  Copilot Studio  |  Azure AI muzairsuleman.blogspot.com  |  March 2025  |  Power Pages & Copilot Studio

 

What This Feature Actually Does

For a long time, adding a conversational agent to a Power Pages site meant either using the default system-generated agent or going through a fairly manual embedding process with limited control. That has changed.

Microsoft has released a significant update to how agents work inside Power Pages. You can now bring any agent you have already built in Copilot Studio — a customer support agent, an HR assistant, a product guide, anything — and embed it directly into your Power Pages site through the Setup Workspace. No custom code required for the basic setup.

More importantly, you now have three things you didn’t have before: support for all Copilot Studio authentication types, the ability to test agents directly from Copilot Studio without switching tools, and web role-based visibility so the agent only shows up for the users you intend it for.

 

ℹ️  Who Should Read This This is aimed at Power Platform developers and consultants who are already familiar with Power Pages and Copilot Studio basics. If you have built an agent in Copilot Studio and want to surface it on a Power Pages site — this is your guide.

 

Four New Capabilities at a Glance

 

🔐  All Authentication Types Supported Configure agent authentication using any identity provider your organisation already uses — including Microsoft Entra ID. The agent now fully aligns with your site’s existing security setup.

 

🤖  Bring Your Own Agent Add any existing Copilot Studio agent to your site without rebuilding it. Your agent, your knowledge sources, your configuration — just surfaced on Power Pages.

 

👥  Web Role Visibility Control Restrict the agent to specific user groups using Power Pages web roles — the same mechanism you use to control page and data access. Show the right agent to the right users.

 

🧪  Test Inside Copilot Studio Validate your agent’s conversation and authentication flow directly from within Copilot Studio — no need to keep switching between tools during development.

 

 

Prerequisites

Before you start, make sure all three of these conditions are met in your environment. Missing any one of them will cause the agent integration to either fail silently or not appear at all.

 

☑	Tenant admin has enabled "Publish Copilots with AI features" This setting lives in the Power Platform Admin Center. Without it, agents cannot be published or embedded anywhere — including Power Pages. Ask your tenant admin to confirm it is switched on.
☑	HTTP connector is not blocked in your environment Agents added from Power Pages use the HTTP node to communicate with the site. If your environment’s DLP policy has blocked the HTTP connector, the agent will not be able to send or receive messages. Check your environment’s DLP policy in the Admin Center.
☑	Sufficient Copilot Studio capacity in the environment Agents use Copilot Studio generative answers, which consume message capacity. Newly created agents start as trials and then draw from available capacity once the trial ends. Verify your environment has capacity available.

 

⚠️  Custom Domain Warning If you plan to update your site’s custom domain after adding an agent — you must first turn the agent off, update the domain, and then turn it back on. Skipping this step will break the agent’s communication with the site. Also, if you turn an agent off, wait a few minutes before turning it back on to allow background operations to complete.

 

 

Two Ways to Add an Agent

Power Pages gives you two distinct approaches depending on whether you want to create a new agent on the spot or use one you’ve already built in Copilot Studio.

 

OPTION A Create a New Agent from Power Pages Power Pages creates a brand new Copilot Studio agent automatically, pre-configured with your site as its knowledge source. → Auto-configured with site context → Uses Generic OAuth 2 with token pass-through → Works with all identity providers including anonymous → Starts as a trial, then uses environment capacity

OPTION B Add an Existing Copilot Studio Agent Bring an agent you’ve already built — with all its existing knowledge sources, topics, and actions — and embed it without rebuilding. → Preserves all existing agent configuration → Supports all Copilot Studio auth types → Control visibility with web roles after adding → Same agent can power multiple sites or channels

 

💡  Which Should You Use? If you are starting fresh and want a site-aware agent quickly, go with Option A. If you have already invested time building a Copilot Studio agent — with custom topics, knowledge sources, Power Automate actions, or Dataverse integration — go with Option B and preserve all that work.

 

 

Step-by-Step: Add Your Agent

The entire setup happens inside the Power Pages Setup Workspace. Here is the exact sequence of steps.

 

1

Open the Setup Workspace in Power Pages Log into make.powerpages.microsoft.com, select your site, and navigate to the Set up workspace from the left navigation panel. This is your central hub for all site configuration outside of design.  Navigation path: make.powerpages.microsoft.com → Select Site → Set up workspace → AI assistance → Agents

 

2	Navigate to Agents under AI Assistance Inside the Setup Workspace, find the AI assistance section in the left panel and select Agents. This opens the agent management page where you can see any agents already connected to the site and where you add new ones.

 

3

Add Your Copilot Studio Agent Click Add agent. A panel will appear showing all agents available in the current environment. Select the Copilot Studio agent you want to embed. Only agents in the same Power Platform environment as your Power Pages site will appear in this list.  If you want to create a new agent instead, toggle on the Site agent option and Power Pages will provision one automatically.

 

4

Configure Authentication for the Agent After adding the agent, you will be prompted to configure authentication. This is where the new update matters most — you can now select any authentication type your agent uses in Copilot Studio. The configuration should match what you have set in your Copilot Studio agent settings.

 

5

Assign Web Roles to Control Visibility Once the agent is added, assign the web roles that should have access to it. This is the same web role system you use to control page visibility and table permissions throughout Power Pages.  Examples: • Authenticated Users role → agent visible to all logged-in users • Anonymous Users role → agent visible to all visitors • Custom role (e.g. “Premium Members”) → agent visible only to that group

 

6

Test from Copilot Studio You can now test the agent’s conversation flow and authentication directly inside Copilot Studio — without needing to open your Power Pages site in a separate browser tab. Use the test panel in Copilot Studio to simulate user interactions and verify authentication is working as expected before making the site live.

 

7	Publish and Verify on the Live Site Save your changes in the Setup Workspace and preview or publish your Power Pages site. The agent chat widget will appear for users who match the web roles you assigned. Test with a user account that has the correct role to confirm the full end-to-end experience.

 

 

Authentication: The Critical Detail

Authentication is the part of this setup that most developers get wrong the first time. Power Pages agents now support all authentication types available in Copilot Studio. Here is what each one means and when to use it.

 

Authentication Type	When to Use	Status
No Authentication (Anonymous)	Public-facing support agents, FAQ bots, general enquiry assistants where no user identity is required. Best for portals with anonymous visitors.	Standard
Generic OAuth 2 (Token Pass-Through)	Default method for agents created from Power Pages. Works seamlessly with all identity providers configured for the site, including third-party providers like LinkedIn or Google.	Standard
Microsoft Entra ID	Internal employee portals or any scenario where the agent needs to act on behalf of the authenticated user. Enables identity-aware responses and Dataverse access scoped to the user.	New ✓
Azure AD B2C / External Providers	Customer-facing portals using Azure AD B2C or other external identity providers. The customer’s B2C login automatically extends to the agent session.	New ✓

 

🔗  Authentication Alignment is Critical The authentication method configured on the agent in Copilot Studio and the method you set in the Power Pages agent setup must match. If they are misaligned, the agent will either refuse to respond for authenticated users, or users will be prompted to log in again — creating a broken experience. Always confirm your Copilot Studio agent authentication settings before starting the Power Pages configuration.

 

 

Web Role Visibility — Full Control

Web role-based visibility is one of the most useful aspects of this update. You control agent access the same way you control page access in Power Pages — by assigning roles. This means your existing understanding of the Power Pages security model applies directly here.

 

👤  Anonymous Users Public visitors, not logged in. Ideal for FAQ agents and public-facing portals.

🔐  Authenticated Users Any logged-in user. Use for support or service agents on portals requiring login.

⭐  Custom Role Specific user groups only — e.g. “Premium Members”, “Managers”, or “Partners”.

 

The practical implication is powerful. You could have a general FAQ agent visible to anonymous visitors, a support agent visible to all authenticated users, and a specialist agent visible only to premium subscribers or verified partners — all running on the same Power Pages site, each governed by its own web role assignment.

 

💡  A site can have multiple agents You are not limited to a single agent per site. Each agent can have its own web role assignment, its own authentication configuration, and its own conversation scope. Design your agent architecture based on user segments rather than trying to build one agent that handles everything.

 

 

What Changed: Before vs After

Here is a clear comparison of how the agent integration worked previously versus what is now available.

 

Capability	Before This Update	Now
Authentication types	Limited — mainly anonymous or basic	✓ All Copilot Studio auth types including Entra ID
Bring existing agent	Manual and inconsistent	✓ Native ‘Add agent’ from Setup Workspace
Test during development	Required switching to live site preview	✓ Test directly inside Copilot Studio
Control who sees the agent	Limited visibility options	✓ Full web role-based visibility control
Multiple agents per site	— Not natively supported	✓ Multiple agents, each with its own role
Identity-aware responses	— Agent could not identify the user	✓ Entra ID auth enables user-aware responses

 

 

Real-World Scenarios

Here are three practical examples of how this integration works in actual client projects — the kind of scenarios you’ll encounter as a Power Platform consultant.

 

Scenario 1 — B2B Customer Portal with Account-Aware Agent A company runs a Power Pages portal for their enterprise clients. Each client logs in via Microsoft Entra ID. The Copilot Studio agent is configured with Entra ID authentication and has actions connected to Dataverse via Power Automate. When a client asks “What is the status of my open support tickets?”, the agent queries Dataverse using the authenticated user’s identity — and only returns tickets belonging to that client’s account.  Web Role: Authenticated Users  |  Auth Type: Microsoft Entra ID

 

Scenario 2 — Public Knowledge Base with FAQ Agent A product company has a public-facing Power Pages site. They add a Copilot Studio agent configured with no authentication — it uses the site’s content as its knowledge source and answers product questions for any visitor. No login required, no identity needed.  Web Role: Anonymous Users  |  Auth Type: None

 

Scenario 3 — Employee Portal with Department-Specific Agents An internal HR portal has three agents: a general HR information agent visible to all employees, a payroll and benefits agent visible only to users with the “Finance Role” web role, and a manager-specific agent for performance review workflows visible only to users with the “Manager” web role. All three run on the same Power Pages site with independent web role assignments.  Web Role: Per agent  |  Auth Type: Microsoft Entra ID

 

🏗️  Consultant Tip When scoping a Power Pages project that includes conversational AI, plan the agent architecture alongside the page permissions architecture — they use the same web role system, so a well-designed role structure supports both. Don’t design them independently.

 

 

Quick Summary

If you need to refer back to the key points from this guide without re-reading the full article, here they are.

 

Key Point	Detail
Where to Configure	Setup Workspace → AI assistance → Agents
Agent Sources	Create new from Power Pages, or add existing Copilot Studio agent
Authentication	All Copilot Studio types supported — Anonymous, OAuth 2, Entra ID, B2C
Visibility Control	Assign web roles — same system as pages and table permissions
Testing	Test agent conversations and auth directly inside Copilot Studio
Multiple Agents	A single site can have multiple agents, each with its own role
Key Prerequisite	"Publish Copilots with AI features" must be ON in Power Platform Admin Center
Custom Domain Warning	Turn agent OFF before changing custom domain, then turn it back ON

 

 

Official Documentation

Microsoft’s official documentation for this feature is across three separate pages. Here are the direct links.

 

🔧  Add an agent from the Setup Workspace https://learn.microsoft.com/power-pages/getting-started/enable-agent

 

🔐  Configure user authentication for agents https://learn.microsoft.com/power-pages/getting-started/configure-user-authentication-for-agent

 

🏢  Configure Microsoft Entra ID authentication for agents https://learn.microsoft.com/power-pages/getting-started/configure-entra-id-authentication-for-agent

 

📣  Official Microsoft Power Pages Blog Announcement https://www.microsoft.com/en-us/power-platform/blog/power-pages/seamlessly-embed-copilot-studio-agents-into-power-pages/