Summary
Unit 8 of 8 · Module 11: Integrate your agent with Microsoft 365
Read this lesson
Where people already work
In this module, you took your agent to where people already work: Microsoft Teams and Microsoft 365 Copilot. Every Foundry agent has a stable endpoint and its own identity, so publishing means handing that endpoint to Microsoft 365. Publishing from the portal sets up Azure Bot Service, builds the Teams app package, and puts your agent in the store. Choose Just you for testing, or your whole organization once an admin approves it. Because the agent signs in as itself, give its identity roles on anything its tools use. For complex needs like custom sign-in or middleware, the Microsoft 365 Agents Toolkit builds a proxy app in between. Work IQ brings in Microsoft 365 data through MCP, and only what you're allowed to see. And after launch, you test in Teams, fix the common faults, and keep watching.
Further reading and what's next
To go further, read Microsoft's articles on publishing agents to Microsoft Copilot and Teams, on Work IQ, on the Microsoft 365 Agents Toolkit, and on agent identity in Foundry. Next, in Module 12, you'll connect agents together into workflows.
Facts from Microsoft's documentation: Publish agents to Microsoft Copilot and Microsoft Teams; Microsoft Work IQ CLI; Migrate from Agent Applications to the new Microsoft Foundry agent model (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.