Introduction
Unit 1 of 8 · Module 11: Integrate your agent with Microsoft 365
Read this lesson
From the test kitchen to the plaza
Picture a chef who has perfected a dish in a quiet test kitchen. Every tasting goes well, but the hungry people are across town in an office plaza, and they won't walk over to the kitchen. Your agent can end up in the same spot. Say you've built an agent in Microsoft Foundry that answers questions about company policies and procedures. It shines in the Foundry playground, but your colleagues spend their day in Microsoft Teams. They want to ask it right there in a Teams chat, or through Microsoft 365 Copilot, without opening yet another app. So instead of asking people to come to the kitchen, you drive a food truck to the plaza.
What this module covers
Foundry can publish an agent straight to Teams and Microsoft 365 Copilot, so people use it inside the tools they already have open. That works for an IT help desk agent, an onboarding buddy for new starters, or an advisor for your own line of business. In this module, you'll compare the ways to publish a Foundry agent, then publish one from the Foundry portal to Teams and Copilot. You'll see when the Microsoft 365 Agents Toolkit is worth the extra work. You'll use Work IQ to bring in Microsoft 365 data like email, meetings, and documents. And you'll learn how to test and troubleshoot an agent once it's live. To follow along, you'll want some Azure experience, an agent you've built in Foundry, and a Microsoft 365 subscription with Teams. First stop: your publishing options.
Facts from Microsoft's documentation: Publish agents to Microsoft Copilot and Microsoft Teams (CC BY 4.0), rewritten in Loop's own words and examples. Narration, animation, and quiz by Loop. Microsoft, Azure, and Microsoft Foundry are trademarks of Microsoft. Loop is independent and not affiliated with or endorsed by Microsoft.