Custom CoPilot Agent AI accessible from the CRM

(4) Share

Report

Posted on by Jimmy Owen

Hi,

I created a custom CoPilot Agent AI in CoPilot Studio and published it. It's goal is to assist and help end users of the Dynamics 365 CRM in every day work. I know there is a way to embed the AI Agent to Teams, but how to do it, so that the end users of the system have a direct access to it from the CRM? Is there a simple way to embed the chatbot's widget or iframe?

I don't want to use the CoPilot for Customer Service, I want to use the custom AI Agent that I have created.

Thanks,

Jimmy Owen

Categories:

Dynamics 365 Customer Service

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Suggested answer

Holly Huffman 6,554 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!
Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!

To embed your custom CoPilot Agent AI into Dynamics 365 CRM for direct access by end users, you can follow these steps:

1. Enable Dynamics 365 Channel in CoPilot Studio

Go to your CoPilot Studio portal.

Navigate to the "Channels" section in the left menu.

Select "Dynamics 365" and complete the configuration wizard.

This will allow your custom AI Agent to integrate with Dynamics 365 CRM.

2. Embed the Chat Widget

In Dynamics 365 CRM, go to Settings > Administration.

Select Omnichannel Administration.

Configure the chat widget settings and link it to your custom CoPilot Agent AI.

Set up routing rules and agent assignments as needed.

3. Use an Iframe

If you prefer embedding the chatbot as an iframe, retrieve the web chat embed code from CoPilot Studio (under Channels > Web).

Add an iframe or HTML control to the Dynamics 365 CRM interface.

Insert the embed code into the HTML property and configure the height, width, and any trigger actions or context variables.

4. Test and Validate

Thoroughly test the integration to ensure the chatbot is accessible and functioning as intended.

Verify authentication flows if your bot requires user identity.

These methods should allow your custom CoPilot Agent AI to be accessible directly from Dynamics 365 CRM.

Was this reply helpful? Yes No
Verified answer

Daivat Vartak (v-9d... 7,841 Moderator on at

Like (1)

Report
Copy link

Link copied!
Hello Jimmy,

You're looking to embed your custom Copilot Studio agent directly into Dynamics 365 CRM for easy access by end-users, bypassing the standard Copilot for Customer Service and Teams integration. While there isn't a direct "widget" or simple iframe embedding method offered out-of-the-box, you can achieve this through a combination of techniques, primarily using Power Pages or custom web resources.

Here's a breakdown of how you can approach this:

1. Power Pages Integration (Recommended):

Concept:

Power Pages allows you to create external-facing websites that integrate with Dynamics 365 data.

You can use Power Pages to host your Copilot Studio bot and then embed it into Dynamics 365.

Implementation:

Create a Power Pages Site:

If you don't have one already, create a Power Pages site connected to your Dynamics 365 environment.

Add an Iframe or Web Component:

In Power Pages, create a new web page or use an existing one.

Use an iframe or a custom web component to embed your Copilot Studio bot.

To get the Iframe code, you will need to go to the publish area of your CoPilot Studio bot. There you will find the Iframe code.

Embed the Bot:

Use the Copilot Studio bot's embed code (typically an iframe) to insert the bot into your Power Pages page.

Embed Power Pages into Dynamics 365:

Create a web resource (HTML) in Dynamics 365.

In the HTML web resource, use an iframe to embed the Power Pages page where your bot resides.

Add the web resource to a Dynamics 365 form or dashboard.

Security Considerations:

Make sure that the security settings of the Power Page, and the CoPilot studio bot are properly configured.

Advantages:

Relatively straightforward.

Leverages existing Power Platform components.

Provides a clean and integrated user experience.

Disadvantages:

Requires setting up and managing a Power Pages site.

Adds an extra layer of complexity.

2. Custom Web Resource (JavaScript and Iframe):

Concept:

Create a custom web resource (HTML and JavaScript) that loads the Copilot Studio bot's iframe directly into Dynamics 365.

Implementation:

Get Embed Code:

Retrieve the embed code (iframe) from your published Copilot Studio bot.

Create Web Resource:

Create an HTML web resource in Dynamics 365.

In the HTML, use JavaScript to dynamically create an iframe and insert the bot's embed code.

Add Web Resource to Form/Dashboard:

Add the web resource to a Dynamics 365 form or dashboard where you want the bot to appear.

Security considerations:

Make sure that the security settings of the CoPilot studio bot are properly configured.

Advantages:

More direct integration.

Less overhead than Power Pages.

Disadvantages:

Requires JavaScript development.

May be less flexible in terms of styling and customization.

3. Custom PCF Control (Advanced):

Concept:

Develop a custom Power Apps component framework (PCF) control to embed the Copilot Studio bot.

This provides the most control over the bot's appearance and behavior.

Implementation:

PCF Development:

Develop a PCF control that uses JavaScript and the Copilot Studio bot's embed code to render the bot.

Deployment:

Deploy the PCF control to your Dynamics 365 environment.

Add to Form/Dashboard:

Add the PCF control to a Dynamics 365 form or dashboard.

Advantages:

Maximum control and flexibility.

Seamless integration.

Disadvantages:

Requires significant development effort.

Steeper learning curve.

Recommendations:

Power Pages (Option 1) is generally the most practical and recommended approach for most users. It provides a good balance of flexibility and ease of implementation.

Custom Web Resource (Option 2) is suitable for simpler integrations where you don't need the full features of Power Pages.

Custom PCF Control (Option 3) is only recommended for advanced users who require highly customized bot integration.

Remember to thoroughly test your integration and consider security implications.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more. If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,

Daivat Vartak

Was this reply helpful? Yes No
Vahid Ghafarpour 12,258 on at

Like (1)

Report
Copy link

Link copied!

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No
CU12100948-0 on at

Like (0)

Report
Copy link

Link copied!

I’ve dealt with similar setups where the technical side looks clean on paper, but day-to-day usage still creates friction for teams and end users. Integrations are powerful, but they only shine when they actually simplify work instead of adding another layer to manage. That’s why I ended up relying on a tool ai for business operations. It doesn’t replace complex systems like CRM platforms, but it supports them by handling routine communication, reminders, and coordination, so the tech stack feels lighter and people can focus on real work instead of navigating tools all day.

Was this reply helpful? Yes No