draft integrate m365 module

Author: ivorb

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/1-introduction.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.introduction
+title: Introduction
+metadata:
+  title: Introduction
+  description: Introduction to integrating Microsoft Foundry agents with Microsoft 365.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 3
+content: |
+  [!include[](includes/1-introduction.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/2-understand-publishing-options.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.understand-publishing-options
+title: Understand Foundry agent publishing options
+metadata:
+  title: Understand Foundry agent publishing options
+  description: Learn about the different approaches for publishing Microsoft Foundry agents to Microsoft Teams and Microsoft 365 Copilot.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 8
+content: |
+  [!include[](includes/2-understand-publishing-options.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/3-publish-agent-foundry-portal.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.publish-agent-foundry-portal
+title: Publish an agent from Foundry portal to Teams
+metadata:
+  title: Publish an agent from Foundry portal to Teams
+  description: Learn the step-by-step process to publish a Microsoft Foundry agent to Microsoft Teams and Microsoft 365 Copilot.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 10
+content: |
+  [!include[](includes/3-publish-agent-foundry-portal.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/4-agents-toolkit-advanced.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.agents-toolkit-advanced
+title: Advanced - Use Microsoft 365 Agents Toolkit
+metadata:
+  title: Advanced - Use Microsoft 365 Agents Toolkit for complex integration scenarios
+  description: Learn about the Microsoft 365 Agents Toolkit as an alternative approach for complex Foundry agent integration scenarios.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 6
+content: |
+  [!include[](includes/4-agents-toolkit-advanced.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/5-access-m365-data-work-iq.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.access-m365-data-work-iq
+title: Access M365 data with Work IQ
+metadata:
+  title: Access Microsoft 365 data with Work IQ
+  description: Learn how to use Microsoft Work IQ to provide your Foundry agents with access to Microsoft 365 data like emails, meetings, and documents.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 8
+content: |
+  [!include[](includes/5-access-m365-data-work-iq.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/6-test-iterate-agent.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.test-iterate-agent
+title: Test and iterate your integrated agent
+metadata:
+  title: Test and iterate your integrated agent
+  description: Learn best practices for testing Foundry agents before and after publishing to Microsoft Teams.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 7
+content: |
+  [!include[](includes/6-test-iterate-agent.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/7-exercise.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.exercise
+title: Exercise - Publish a Foundry agent to Teams
+metadata:
+  title: Exercise - Publish a Foundry agent to Teams
+  description: Hands-on exercise to create a simple agent in Microsoft Foundry and publish it to Microsoft Teams.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 25
+content: |
+  [!include[](includes/7-exercise.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/8-knowledge-check.yml

@@ -0,0 +1,85 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.knowledge-check
+title: Knowledge check
+metadata:
+  title: Knowledge check
+  description: Check your knowledge of integrating Microsoft Foundry agents with Microsoft 365.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 3
+quiz:
+  title: Check your knowledge
+  questions:
+  - content: What Azure resource does the Foundry portal automatically create when you publish an agent to Microsoft Teams?
+    choices:
+    - content: Azure Functions
+      isCorrect: false
+      explanation: Incorrect. Azure Functions is used for serverless compute but isn't automatically created during agent publishing.
+    - content: Azure Bot Service
+      isCorrect: true
+      explanation: Correct. The publishing process automatically creates an Azure Bot Service resource that routes messages between Microsoft Teams and your Foundry agent.
+    - content: Azure Cosmos DB
+      isCorrect: false
+      explanation: Incorrect. Cosmos DB is a database service and isn't automatically created during agent publishing.
+    - content: Azure Logic Apps
+      isCorrect: false
+      explanation: Incorrect. Logic Apps is a workflow automation service and isn't automatically created during agent publishing.
+  - content: What is the main difference between shared scope and organization scope when publishing an agent?
+    choices:
+    - content: Shared scope requires more Azure resources
+      isCorrect: false
+      explanation: Incorrect. Both scopes use the same Azure resources.
+    - content: Organization scope requires admin approval before the agent is available to all users
+      isCorrect: true
+      explanation: Correct. Organization scope requires an administrator to approve the agent in the Microsoft 365 admin center before it becomes available organization-wide.
+    - content: Shared scope only works in the Foundry playground
+      isCorrect: false
+      explanation: Incorrect. Shared scope publishes the agent to Teams, not just the Foundry playground.
+    - content: Organization scope provides better agent performance
+      isCorrect: false
+      explanation: Incorrect. The publish scope doesn't affect agent performance.
+  - content: What happens to tool permissions when you publish an agent from Foundry to Teams?
+    choices:
+    - content: Permissions are automatically transferred to the published agent
+      isCorrect: false
+      explanation: Incorrect. Permissions aren't automatically transferred when publishing.
+    - content: Tools are disabled after publishing
+      isCorrect: false
+      explanation: Incorrect. Tools can work after publishing, but permissions need to be reassigned.
+    - content: The published agent gets a new identity and needs permissions reassigned
+      isCorrect: true
+      explanation: Correct. The published agent uses its own distinct identity, so any RBAC permissions for Azure resources must be assigned to this new identity.
+    - content: Permissions only work in organization scope
+      isCorrect: false
+      explanation: Incorrect. Permission requirements are the same regardless of publish scope.
+  - content: What is Microsoft Work IQ?
+    choices:
+    - content: A machine learning model for workplace analytics
+      isCorrect: false
+      explanation: Incorrect. Work IQ is a CLI and MCP server, not a machine learning model.
+    - content: A CLI and MCP server that connects AI agents to Microsoft 365 data
+      isCorrect: true
+      explanation: Correct. Work IQ is a command-line interface and Model Context Protocol server that enables AI agents to access Microsoft 365 data like emails, meetings, and documents.
+    - content: A replacement for Microsoft Teams
+      isCorrect: false
+      explanation: Incorrect. Work IQ complements Microsoft 365 services, it doesn't replace them.
+    - content: A Visual Studio Code extension for building agents
+      isCorrect: false
+      explanation: Incorrect. Work IQ is a CLI/MCP server. The Microsoft 365 Agents Toolkit is a VS Code extension.
+  - content: When should you consider using the Microsoft 365 Agents Toolkit instead of direct publishing from Foundry?
+    choices:
+    - content: For all production deployments
+      isCorrect: false
+      explanation: Incorrect. Direct publishing is suitable for most production scenarios.
+    - content: When you need custom SSO, middleware logic, or multi-environment deployment
+      isCorrect: true
+      explanation: Correct. The Agents Toolkit is valuable for complex scenarios requiring custom single sign-on, middleware processing, or sophisticated deployment pipelines.
+    - content: When publishing to shared scope
+      isCorrect: false
+      explanation: Incorrect. Both shared and organization scope work with direct publishing.
+    - content: When your agent doesn't use any tools
+      isCorrect: false
+      explanation: Incorrect. The choice between approaches doesn't depend on whether tools are configured.

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/9-summary.yml

@@ -0,0 +1,14 @@
+### YamlMime:ModuleUnit
+uid: learn.wwl.integrate-foundry-agent-with-m365.summary
+title: Summary
+metadata:
+  title: Summary
+  description: Summary of integrating Microsoft Foundry agents with Microsoft 365.
+  ms.date: 02/17/2026
+  author: ivorb
+  ms.author: berryivor
+  ms.topic: unit
+  ai-usage: ai-generated
+durationInMinutes: 3
+content: |
+  [!include[](includes/9-summary.md)]

learn-pr/wwl-data-ai/integrate-foundry-agent-with-m365/includes/1-introduction.md

@@ -0,0 +1,20 @@
+Imagine you've built an AI agent in Microsoft Foundry that helps your team answer questions about company policies and procedures. The agent works great in the Foundry playground, but your users spend most of their day in Microsoft Teams. They want to interact with the agent directly in Teams chat, or even through Microsoft 365 Copilot, without switching to a separate application. How do you bridge this gap?
+
+Microsoft Foundry provides built-in capabilities to publish your agents directly to Microsoft Teams and Microsoft 365 Copilot. This integration allows users to interact with your custom AI agents in the same tools they already use for collaboration and productivity. Whether you need a support agent that answers IT questions, a knowledge assistant that helps onboard new employees, or a specialized advisor for your business domain, you can make these agents available where your users work.
+
+In this module, you learn how to publish Microsoft Foundry agents to Microsoft 365. You explore the publishing workflow from the Foundry portal, understand when you might need advanced integration options, and discover how to use Work IQ to give your agents access to Microsoft 365 data like emails, meetings, and documents.
+
+## Learning objectives
+
+By the end of this module, you'll be able to:
+
+- Explain the options for publishing Foundry agents to Microsoft 365
+- Publish an agent from the Foundry portal to Teams and Microsoft 365 Copilot
+- Use Work IQ to access Microsoft 365 data in your agents
+- Test and troubleshoot agents integrated with Microsoft 365
+
+## Prerequisites
+
+- Familiarity with Azure and the Azure portal
+- Experience building agents in Microsoft Foundry (recommended: [Develop AI agents with Microsoft Foundry and Visual Studio Code](/training/modules/develop-ai-agents-azure-vs-code/) module)
+- A Microsoft 365 subscription with access to Teams