Publish a Copilot Studio Agent to a Demo Website or Embed It in Your Website

You built an agent and it works in the test pane. Now people outside Copilot Studio need to try it, and later it has to live on a real page where employees or customers already go.

In this tutorial, we’ll set up the Copilot Studio demo website for quick testing, copy the embed code, and add the agent to a SharePoint page. We tested every step on 11/4/2026 on both a GitHub Copilot agent and a standard agent, because their screens differ.

Quick answer: Switch authentication to No authentication and select Publish. On a GitHub Copilot agent that’s … > Settings > Safety & access, and the Demo website channel appears on its own. On a standard agent it’s Settings > Security > Authentication, then Channels > Demo website. Copy the iframe from the Embed tab (GitHub Copilot) or Channels > Web app (standard) and paste it into your page.

<iframe src="https://copilotstudio.microsoft.com/environments/<environment-id>/bots/<agent-schema-name>/webchat?__version__=2"
  frameborder="0" style="width: 100%; height: 600px;"></iframe>

What You Need Before You Start

• An agent in Copilot Studio that already answers questions in the test pane. If you’re starting from zero, first create an agent in Microsoft Copilot Studio.
• Permission to edit and publish that agent (you’re its owner or an editor in the environment).
• For the SharePoint part: edit rights on the page, plus a site collection admin who can change HTML Field Security.
• A decision about sign-in. The demo website and the iframe only work for an agent anyone with the link can use, so don’t connect it to private data that needs the user’s own credentials.

We built two small test agents for this guide, SPGuides Website Assistant (GitHub Copilot) and SPGuides Website Assistant – Standard, each with the same instructions. You can find our other agent tutorials on the Copilot Studio tutorials hub.

Demo Website vs Live Website: Which One Do You Need?

Copilot Studio gives you two web options, and they solve different problems. The demo website is a page Microsoft hosts for you. A live website is your own page with the agent embedded in it.

	Demo website	Live website (embed code)
Who it’s for	Teammates and stakeholders testing the agent	Employees or customers using the agent for real
Where it runs	A page hosted on copilotstudio.microsoft.com	Your site, an intranet page or a SharePoint page
Setup	Share the link (standard agents also get a welcome message and starters)	Copy the iframe and paste it into your HTML
Production use	No, Microsoft says not to share it with customers	Yes

Step 1: Check Which Kind of Agent You Have

Open the Agents list in Copilot Studio and look at the Powered by column. It says GitHub Copilot for agents made from the new Agent card on the home page, and Standard for agents made under Other ways to build > Build with standard orchestration.

What you need to do	GitHub Copilot agent	Standard agent
Find authentication	… (More options) > Settings > Safety & access	Settings > Security > Authentication
Authentication options	No authentication, Authenticate with Microsoft	No authentication, Authenticate with Microsoft, Authenticate manually
Find the channels	+ next to Channels on the Build page	Channels tab (under +3 when the window is narrow)
Demo website	Added automatically when you pick No authentication	Share a preview > Demo website
Embed code	Demo website > Embed tab (also in the App channel)	Other channels > Web app
Welcome message on the demo page	Not in the dialog	Welcome message + conversation starters

The rest of this guide shows both. Follow the part that matches your agent and skip the other.

Step 2: Set Authentication to No Authentication

New agents use Authenticate with Microsoft by default. That’s right for Teams and Microsoft 365 Copilot, but it hides the demo website and the web embed. Changing it is the step people miss most often.

GitHub Copilot agent

Select the + next to Channels on the right side of the Build page. With sign-in still on, the Add a channel dialog grays out Demo website:

Hover over it and Copilot Studio tells you exactly what to change:

Close the dialog, select the … (More options) button at the top of the agent, then Settings. Open Safety & access and pick No authentication in the Authentication dropdown. GitHub Copilot agents only offer these two choices:

As soon as we picked it, the Demo website channel showed up under Channels without any extra click. Close the settings dialog when you’re done:

New GitHub Copilot agents also come with the Work IQ tool. We removed it from our public test agent because a website visitor isn’t signed in to Microsoft 365.

Standard agent

Open the Channels tab. If the window is narrow, it hides under +3:

With Microsoft authentication, a banner says only Teams, Microsoft 365 and SharePoint are available, and the web channels don’t appear at all:

Select Settings at the top, then Security and Authentication:

Choose No authentication and select Save:

Copilot Studio asks you to confirm and reminds you that the change only takes effect after you publish. Select Save again:

Important: with No authentication, anyone who has the link can chat with the agent, and it can’t use tools that run with the user’s credentials. A standard agent can use manual authentication in Copilot Studio instead; that keeps the demo website available, but not the iframe embed.

Step 3: Publish the Agent

The demo website and the embed code serve the published version, not your draft. Publish after the authentication change and after every change you make later.

GitHub Copilot agent

Select Publish at the top right. The Publish dialog lists the channels (or asks you to add one), and Publish agent starts it:

It took about a minute for us. The status changes to Published and a success message appears:

Standard agent

Select Publish. The dialog warns that the agent doesn’t require end user authentication (and, if it searches the web, that it will). That’s expected here, so select Publish:

The header shows the new publish date when it finishes:

Step 4: Share the Copilot Studio Demo Website

GitHub Copilot agent

Select the Demo website chip under Channels. The dialog has two tabs. Demo website holds the link to copy and an Open demo website button:

We opened it and asked “What is a SharePoint list view threshold?” The agent answered with sources, just like in the test pane:

Standard agent

On the Channels tab, Demo website now sits under Share a preview and Web app under Other channels:

Select Demo website. Here you can add a Welcome message and Conversation starters (trigger phrases, one per line), then copy the link under Share your website and select Save:

Keep the welcome message short. It becomes the big headline on the page, and ours got cut off after “Ask me about”. The chat itself worked fine. To change what the chat says first, customize the welcome message in Copilot Studio:

If the demo link asks testers to sign in or won’t open, the agent is still on Authenticate with Microsoft or wasn’t republished; our Copilot Studio demo website authentication error fix walks through it.

Step 5: Copy the Embed Code

GitHub Copilot agent

In the same Demo website dialog, open the Embed tab and select the copy icon next to the code:

The App channel in Add a channel shows the same embed code plus a Microsoft 365 Agents SDK connection string for developers. It showed the code even while sign-in was still on, but Microsoft’s docs say the default Web Chat embed needs No authentication, and that’s the setup we tested:

The GitHub Copilot agent’s iframe ends with two extra parameters. Keep them as they are:

<iframe src="https://copilotstudio.microsoft.com/environments/<environment-id>/bots/<agent-schema-name>/webchat?__version__=2&enableFileAttachment=false&cliAgent=true"
  frameborder="0" style="width: 100%; height: 600px;"></iframe>

Standard agent

Select Web app under Other channels and select Copy under Embed code:

Both versions copy a small HTML page around the iframe:

<!DOCTYPE html>
<html>
<body>
<iframe src="https://copilotstudio.microsoft.com/environments/<environment-id>/bots/<agent-schema-name>/webchat?__version__=2&enableFileAttachment=true" frameborder="0" style="width: 100%; height: 100%;"></iframe>
</body>
</html>

For a page you control, paste it where the chat should appear. For SharePoint, keep only the <iframe>...</iframe> part and change height: 100% to a fixed height such as 600px, so the chat has room to scroll.

Step 6: Add the Agent to a SharePoint Page

On your site, open Site contents > Site Pages, select New, then Site Page. We named ours SPGuides Website Assistant. It’s the same Embed web part we use to embed Power Apps in a SharePoint modern page:

Add a section (we used two columns, one per agent), select the + in a column, search for Embed and select it:

Paste the iframe into Website address or embed code in the pane on the right. The chat loads right away:

We added a second Embed web part for the standard agent, so both sit side by side:

SharePoint’s toolbox also has a newer Agent link web part under AI. That’s a different feature, so we stuck with Embed here.

Step 7: Allow copilotstudio.microsoft.com in HTML Field Security

On many sites, the first paste fails with this message:

SharePoint only allows iframes from approved domains, and copilotstudio.microsoft.com isn’t on the default list. A site collection administrator adds it once per site collection:

1. Select the gear icon, then Site information > View all site settings.
2. Under Site Collection Administration, select HTML Field Security.
3. Keep Allow contributors to insert iframes only from the following domains, type copilotstudio.microsoft.com, select Add, then OK.

Our /sites/SPGuides site already had the domain from an earlier test, which is why our paste in Step 6 worked the first time.

Step 8: Publish the Page and Test Both Agents

Select Publish page. You can close the Promote pane that opens. On the published page, both agents greeted us and answered “What is Power Automate?”:

The embed code doesn’t change when you edit the agent. After a change, publish again in Copilot Studio and the page picks it up. Existing chats keep the old version until a new session starts, which in most channels happens after 30 minutes of inactivity.

Authentication and Web Channel Cheat Sheet

Authentication setting	Demo website	Web embed code (iframe)	Teams and Microsoft 365 Copilot
Authenticate with Microsoft (default)	Not available	Not available	Available, Entra ID sign-in
Authenticate manually (standard agents only)	Available	Not available	Available
No authentication	Available	Available	Available

If your users already live in Microsoft 365, read how to publish a Copilot Studio agent to Teams and SharePoint; those channels keep Entra ID sign-in.

Common Mistakes to Avoid

• Demo website is grayed out (GitHub Copilot agent) or missing (standard agent): authentication is still Authenticate with Microsoft. Switch to No authentication and publish.
• Looking for Settings > Security on a GitHub Copilot agent: it’s under … > Settings > Safety & access.
• Looking for a Web app tile on a GitHub Copilot agent: the embed code is on the Embed tab of the Demo website dialog, or in the App channel.
• Testers see an old answer: you saved but didn’t publish, or the tester is still in the old session. Publish and start a new chat.
• “Embedding content from this website isn’t allowed”: add copilotstudio.microsoft.com in HTML Field Security, then paste the code again.
• Pasting the whole HTML page into the Embed web part: keep only the iframe.
• A long welcome message: on the standard demo website it becomes the headline and gets cut off.
• Sharing the demo website with customers: it’s for testing only. Embed the agent on your own site instead.

Can You Embed a Copilot Studio Agent That Requires Sign-In?

Not with the default iframe. It needs No authentication. If the agent must know who’s chatting, developers can connect a custom web app through the Microsoft 365 Agents SDK (the connection string in the App or Web app panel) or Direct Line. For internal users, the Teams or SharePoint channel is usually the simpler choice.

Next Steps

Once the agent is live on the page, give it better answers. A good next move is to add a public website as a knowledge source so the agent can answer from your existing help content.

Then tune agent instructions and conversation starters. Our Copilot Studio training course covers publishing and channels end to end.

We built these agents and features in the same tenant, if you want to keep going:

• Create an Agent Flow Using Designer in Copilot Studio
• How to Use SharePoint List as Knowledge in Copilot Studio [Dynamic Filters and Natural Language]
• Build and Deploy a Smart HR Assistant Bot Using Copilot Studio [Step-by-Step]
• How to Add Copilot to Power Apps?

Frequently Asked Questions