Sr. Content Developer at Microsoft, working remotely in PA, TechBash conference organizer, former Microsoft MVP, Husband, Dad and Geek.
137874 stories
·
31 followers

Integrate Custom Azure AI Agents with CoPilot Studio and M365 CoPilot

1 Share

Integrating Custom Agents with Copilot Studio and M365 Copilot

 

In today's fast-paced digital world, integrating custom agents with Copilot Studio and M365 Copilot can significantly enhance your company's digital presence and extend your CoPilot platform to your enterprise applications and data. This blog will guide you through the integration steps of bringing your custom Azure AI Agent Service within an Azure Function App, into a Copilot Studio solution and publishing it to M365 and Teams Applications.

 

When Might This Be Necessary:

 

Integrating custom agents with Copilot Studio and M365 Copilot is necessary when you want to extend customization to automate tasks, streamline processes, and provide better user experience for your end-users. This integration is particularly useful for organizations looking to streamline their AI Platform, extend out-of-the-box functionality, and leverage existing enterprise data and applications to optimize their operations. Custom agents built on Azure allow you to achieve greater customization and flexibility than using Copilot Studio agents alone.

 

What You Will Need: To get started, you will need the following:

  • Azure AI Foundry
  • Azure OpenAI Service
  • Copilot Studio Developer License
  • Microsoft Teams Enterprise License
  • M365 Copilot License

Steps to Integrate Custom Agents:

Create a Project in Azure AI Foundry: Navigate to Azure AI Foundry and create a project. Select 'Agents' from the 'Build and Customize' menu pane on the left side of the screen and click the blue button to create a new agent.

Customize Your Agent: Your agent will automatically be assigned an Agent ID. Give your agent a name and assign the model your agent will use. Customize your agent with instructions:

 

 

 

Add your knowledge source:  You can connect to Azure AI Search, load files directly to your agent, link to Microsoft Fabric, or connect to third-party sources like Tripadvisor. In our example, we are only testing the CoPilot integration steps of the AI Agent, so we did not build out additional options of providing grounding knowledge or function calling here. 

 

Test Your Agent: Once you have created your agent, test it in the playground. If you are happy with it, you are ready to call the agent in an Azure Function.

 

Create and Publish an Azure Function: Use the sample function code from the GitHub repository to call the Azure AI Project and Agent. Publish your Azure Function to make it available for integration. azure-ai-foundry-agent/function_app.py at main · azure-data-ai-hub/azure-ai-foundry-agent

 

Build a Flow in Power Platform: Move into the Power Platform (https://make.powerapps.com) to build out a flow that connects your Copilot Studio solution to your Azure Function App.

When creating a new flow, select 'Build an instant cloud flow' and trigger the flow using 'Run a flow from Copilot'.

 

 

Add an HTTP action to call the Function using the URL and pass the message prompt from the end user with your URL. The output of your function is plain text, so you can pass the response from your Azure AI Agent directly to your Copilot Studio solution.

 

 

 

Create Your Copilot Studio Agent: Navigate to Microsoft Copilot Studio and select 'Agents', then 'New Agent'.

 

 

Now select ‘Create’ button at the top of the screen  

 

 

From the top menu, navigate to ‘Topics’ and ‘System’. We will open up the ‘Conversation boosting’ topic.

 

 

When you first open the Conversation boosting topic, you will see a template of connected nodes. Delete all but the initial ‘Trigger’ node.

 

 

Now we will rebuild the conversation boosting agent to call the Flow you built in the previous step. Select 'Add an Action' and then select the option for existing Power Automate flow. Pass the response from your Custom Agent to the end user and end the current topic.

 

 

Make Agent Available in M365 Copilot: Navigate to the 'Channels' menu and select 'Teams + Microsoft 365'.

 

 

Be sure to select the box to 'Make agent available in M365 Copilot'. Save and re-publish your Copilot Agent.

 

 

It may take up to 24 hours for the Copilot Agent to appear in M365 Teams agents list. Once it has loaded, select the 'Get Agents' option from the side menu of Copilot

 

 

and pin your Copilot Studio Agent to your featured agent list

 

 

Now, you can chat with your custom Azure AI Agent, directly from M365 Copilot!

 

 

 

 

 

Conclusion: By following these steps, you can successfully integrate custom Azure AI Agents with Copilot Studio and M365 Copilot, enhancing you’re the utility of your existing platform and improving operational efficiency. This integration allows you to automate tasks, streamline processes, and provide better user experience for your end-users. Give it a try!

 

Curious of how to bring custom models from your AI Foundry to your CoPilot Studio solutions?

Check out this blog

Read the whole story
alvinashcraft
10 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Announcing the Release of SSMS 21 Preview 6

1 Share

Today the SQL Tools team is happy to announce the release of SQL Server Management Studio (SSMS) 21 Preview 6. If you’ve got update notifications turned on, you should get a message that there is a new update available. If you don’t see anything, head to Help > Check for Updates to find the latest version. If you don’t have the preview yet, learn more about how to download and install SSMS 21 Preview.  

The team packed lots of awesome stuff into this Preview release and we can’t wait for you to try it out. Some highlights include:

  • The introduction of the migration component (preview)
  • The introduction of the modern connection dialog (preview)
  • The return of presenter mode
  • Bug fixes from SSMS Developer Community reported items

Of course, our release notes are a great way to get a detailed summary of what's new in each release. 

Migration component (preview)

The migration component (preview) can help you with migrating SQL Server versions or cross-platform databases. It runs compatibility checks, identified issues, and runs a feature parity check. The component generates an assessment report that helps you understand potential impacts, possible causes, and remediation steps. It can also physically migrate your database, following the backup-copy-restore technology to move data from the source to the target. To learn more about the migration component (preview), be sure to check out this blog post and our documentation

To install the migration component (preview), head to the Visual Studio Installer. If you're downloading SSMS 21 Preview for the first time, you can find it under the Individual Components tab. If you already have SSMS 21 Preview on your machine, as you're updating to Preview 6, you can open the Visual Studio Installer, select Modify, and go to Individual Components

Modern connection dialog (preview)

We are excited to unveil a new connection dialog experience - the Modern connection dialog (preview) for connecting to SQL Server database engines! Our design was informed by user feedback we've collected and inspired by the new look and feel of the SSMS 21 Preview. We've made improvements to the way recent connections are displayed, moved frequently used fields to the main connection properties section, and added the ability to pin up to 10 of your favorite connection profiles for easy access. There are even more features coming in future previews (including dark mode, cloud resource browsing, and support for registered servers). We'd love to hear your feedback on the new design and how it's working for you!

You can enable this experience two ways: when you first open SSMS 21 Preview 6, a pop up will ask if you'd like to enable it. If you dismiss the pop up, or want to try it out later, you can navigate to Tools > Options > Environment > Connection Dialog and select Modern from the drop down menu. To go back to the Classic connection dialog experience, you can do so at any time by navigating to Tools > Options > Environment > Connection Dialog and select Classic from the drop down menu. 

At this time, the Modern connection dialog (preview) only supports connection to SQL Server database engines. If you need to connect to SQL Server Analysis Services (SSAS) or SQL Server Reporting Services (SSRS), select Connect from Object Explorer (this will bring up the Classic connection dialog, even if you have the Modern connection dialog (preview) enabled) or switch your connection dialog experience back to Classic in the Tools > Options menu. 

Note: The SQL Tools team has received reports of an error message that can pop up when enabling the Modern connection dialog (preview). We are aware of the issue and investigating a fix. For the time being, this error can be ignored by selecting OK

Presenter mode

With SSMS 21 Preview 6, we've reinstated presenter mode and given it a home in the View menu. Presenter mode allows you to enlarge and customize your environment font to help increase readability when sharing your SSMS screen in a presentation. To turn presenter mode on or off, select View > Presenter Mode > Toggle Presenter Mode or use the keyboard command Ctrl+Shift+F5. You can customize your presenter mode settings in View > Presenter Mode > Edit Presenter Mode Settings

Bug fixes from the SSMS Developer Community

In February we launched a new way to leave feedback: the SSMS Developer Community. We love how many feedback and suggestion tickets the community has created! In this preview release, we addressed several items: 

Please keep the feedback coming - your suggestions play a huge role in how we shape the future of SSMS. 

 

Phew! That was a lot of updates. We really hope you enjoy Preview 6, and that you're enjoying the SSMS 21 Preview overall. Thanks for reading, and we can't wait to hear from you!

Read the whole story
alvinashcraft
10 hours ago
reply
Pennsylvania, USA
Share this story
Delete

.NET 10 Preview 3 - Extension Properties & Null-Conditional Assignment for C# 14!

1 Share
From: dotnet
Duration: 17:29
Views: 2,760

Get .NET 10 Previews - https://dot.net/next

Kathleen and Mads are here to talk about the latest C# 14 features that just landed in .NET 10 Preview 3 including new null-conditional assignments for better null safety support and a long awaited feature for extensions including new static support and property support!

Full Release Notes: https://github.com/dotnet/core/blob/main/release-notes/10.0/preview/preview3/csharp.md
Full Live Stream: https://www.youtube.com/watch?v=3Kxp4DKkwj8

#dotnet #dotnet10 #csharp#commandline #developer

Read the whole story
alvinashcraft
10 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Audio-Video in .NET with Elias Puurunen

1 Share
Can you integrate performant audio-video into your .NET application? Carl and Richard talk to Elias Puurunen about his work at Tractus Events, where he uses the NDI protocols to bring real-time audio and video streams into his C# application. Elias talks about the power of P/Invoke to access the underlying libraries for controlling video streams, including utilizing NVidia GPUs for extremely fast encoding and decoding. You could write this code in C++, but why?



Download audio: https://dts.podtrac.com/redirect.mp3/api.spreaker.com/download/episode/65588051/dotnetrocks_1946_audio_video_in_dot_net.mp3
Read the whole story
alvinashcraft
10 hours ago
reply
Pennsylvania, USA
Share this story
Delete

How to Not Hate PowerShell with Barbara Forbes

1 Share

Are some of your team members starting to hate PowerShell? Richard talks to Barbara Forbes about her experiences with teams frustrated by PowerShell. Barbara talks about overcomplicating PowerShell scripts—the kind the most senior folks can create but no one else can maintain. Eventually, nobody will want to touch those scripts. Then there is the question of business value—does everything need to be automated? And by how much? Often, the appropriate solution solves 80% of the cases; the other 20% are best done by hand because the cost and complexity of the last 20% are too high. Focus on the return on investment for the business, and you'll keep the love of PowerShell alive!

Links

Recorded February 24, 2025





Download audio: https://cdn.simplecast.com/audio/c2165e35-09c6-4ae8-b29e-2d26dad5aece/episodes/b0981fd4-50cf-4524-a4dd-3181be65e676/audio/4faa5462-6b5e-4b35-8f99-56d12231ef86/default_tc.mp3?aid=rss_feed&feed=cRTTfxcT
Read the whole story
alvinashcraft
10 hours ago
reply
Pennsylvania, USA
Share this story
Delete

Scott & Mark Learn To… ShaderGlass and Vibe Coding

1 Share
From: Scott Hanselman
Duration: 34:20
Views: 1,493

In this episode of Scott and Mark Learn To, Scott Hanselman and Mark Russinovich dive into a lively mix of tech nostalgia, AI-driven code attribution, and shader programming mishaps. Scott introduces "ShaderGlass," an app that overlays CRT-style shaders on windows, leading to a chaotic live troubleshooting session when it renders invisibly. They also explore AI-assisted code attribution, joke about their legendary Zoomit skills, and poke fun at "vibe coding" among younger developers.

Listen to other episodes at https://scottandmarklearn.to

Discover other Microsoft podcasts at https://microsoft.com/podcasts

Code: TEERCUTBZJCZSOHR

Read the whole story
alvinashcraft
10 hours ago
reply
Pennsylvania, USA
Share this story
Delete
Next Page of Stories