Skip to content

Commit ab471bc

Browse files
authored
Merge pull request #53510 from ivorb/new-agents
New agents
2 parents 9d7e4bd + 0d971b9 commit ab471bc

20 files changed

Lines changed: 830 additions & 3 deletions

learn-pr/paths/develop-ai-agents-azure/index.yml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@ hidden: true
44
metadata:
55
title: Develop AI Agents on Azure
66
description: Learn how to develop AI agents on Azure using the Microsoft Foundry Agent Service and Microsoft Agent Framework. AI-3026
7-
ms.date: 02/12/2026
8-
author: wwlpublish
7+
ms.date: 02/18/2026
8+
author: ivorb
99
ms.author: berryivor
1010
ms.topic: learning-path
1111
ms.collection: wwl-ai-copilot
@@ -33,8 +33,8 @@ modules:
3333
- learn.wwl.build-agent-with-custom-tools
3434
- learn.wwl.connect-agent-to-mcp-tools
3535
- learn.wwl.introduction-foundry-iq
36+
- learn.wwl.integrate-foundry-agent-with-m365
3637
- learn.wwl.build-agent-workflows-microsoft-foundry
37-
- learn.wwl.develop-multi-agent-azure-ai-foundry
3838
- learn.wwl.develop-ai-agent-with-semantic-kernel
3939
- learn.wwl.orchestrate-sk-multi-agent-solution
4040
- learn.wwl.discover-agents-with-a2a
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.introduction
3+
title: Introduction
4+
metadata:
5+
title: Introduction
6+
description: Introduction to integrating Microsoft Foundry agents with Microsoft 365.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 3
13+
content: |
14+
[!include[](includes/1-introduction.md)]
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.understand-publishing-options
3+
title: Understand Foundry agent publishing options
4+
metadata:
5+
title: Understand Foundry agent publishing options
6+
description: Learn about the different channels and approaches for publishing Microsoft Foundry agents, including Microsoft 365, web applications, APIs, and third-party platforms.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 6
13+
content: |
14+
[!include[](includes/2-understand-publishing-options.md)]
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.publish-agent-foundry-portal
3+
title: Publish an agent from Foundry portal to Teams
4+
metadata:
5+
title: Publish an agent from Foundry portal to Teams
6+
description: Learn the step-by-step process to publish a Microsoft Foundry agent to Microsoft Teams and Microsoft 365 Copilot.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 10
13+
content: |
14+
[!include[](includes/3-publish-agent-foundry-portal.md)]
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.agents-toolkit-advanced
3+
title: Advanced - Use Microsoft 365 Agents Toolkit
4+
metadata:
5+
title: Advanced - Use Microsoft 365 Agents Toolkit for complex integration scenarios
6+
description: Learn about the Microsoft 365 Agents Toolkit as an alternative approach for complex Foundry agent integration scenarios.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 6
13+
content: |
14+
[!include[](includes/4-agents-toolkit-advanced.md)]
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.access-m365-data-workiq
3+
title: Access Microsoft 365 data with Work IQ
4+
metadata:
5+
title: Access Microsoft 365 data with Work IQ
6+
description: Learn how to use Microsoft Work IQ to provide your Foundry agents with access to Microsoft 365 data like emails, meetings, and documents.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 8
13+
content: |
14+
[!include[](includes/5-access-m365-data-workiq.md)]
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.test-iterate-agent
3+
title: Test and iterate your integrated agent
4+
metadata:
5+
title: Test and iterate your integrated agent
6+
description: Learn best practices for testing and troubleshooting Foundry agents after publishing to Microsoft Teams.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 6
13+
content: |
14+
[!include[](includes/6-test-iterate-agent.md)]
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.exercise
3+
title: Exercise - Publish a Foundry agent to Teams
4+
metadata:
5+
title: Exercise - Publish a Foundry agent to Teams
6+
description: Interactive exercise to create a simple agent in Microsoft Foundry and publish it to Microsoft Teams.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 30
13+
content: |
14+
[!include[](includes/7-exercise.md)]
Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.knowledge-check
3+
title: Knowledge check
4+
metadata:
5+
title: Knowledge check
6+
description: Check your knowledge of integrating Microsoft Foundry agents with Microsoft 365.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 3
13+
quiz:
14+
title: Check your knowledge
15+
questions:
16+
- content: What Azure resource does the Foundry portal automatically create when you publish an agent to Microsoft Teams?
17+
choices:
18+
- content: Azure Functions
19+
isCorrect: false
20+
explanation: Incorrect. Azure Functions is used for serverless compute but isn't automatically created during agent publishing.
21+
- content: Azure Bot Service
22+
isCorrect: true
23+
explanation: Correct. The publishing process automatically creates an Azure Bot Service resource that routes messages between Microsoft Teams and your Foundry agent.
24+
- content: Azure Cosmos DB
25+
isCorrect: false
26+
explanation: Incorrect. Cosmos DB is a database service and isn't automatically created during agent publishing.
27+
- content: Azure Logic Apps
28+
isCorrect: false
29+
explanation: Incorrect. Logic Apps is a workflow automation service and isn't automatically created during agent publishing.
30+
- content: What is the main difference between shared scope and organization scope when publishing an agent?
31+
choices:
32+
- content: Shared scope requires more Azure resources
33+
isCorrect: false
34+
explanation: Incorrect. Both scopes use the same Azure resources.
35+
- content: Organization scope requires admin approval before the agent is available to all users
36+
isCorrect: true
37+
explanation: Correct. Organization scope requires an administrator to approve the agent in the Microsoft 365 admin center before it becomes available organization-wide.
38+
- content: Shared scope only works in the Foundry playground
39+
isCorrect: false
40+
explanation: Incorrect. Shared scope publishes the agent to Teams, not just the Foundry playground.
41+
- content: Organization scope provides better agent performance
42+
isCorrect: false
43+
explanation: Incorrect. The publish scope doesn't affect agent performance.
44+
- content: What happens to tool permissions when you publish an agent from Foundry to Teams?
45+
choices:
46+
- content: Permissions are automatically transferred to the published agent
47+
isCorrect: false
48+
explanation: Incorrect. Permissions aren't automatically transferred when publishing.
49+
- content: Tools are disabled after publishing
50+
isCorrect: false
51+
explanation: Incorrect. Tools can work after publishing, but permissions need to be reassigned.
52+
- content: The published agent gets a new identity and needs permissions reassigned
53+
isCorrect: true
54+
explanation: Correct. The published agent uses its own distinct identity, so any RBAC permissions for Azure resources must be assigned to this new identity.
55+
- content: Permissions only work in organization scope
56+
isCorrect: false
57+
explanation: Incorrect. Permission requirements are the same regardless of publish scope.
58+
- content: What is Microsoft Work IQ?
59+
choices:
60+
- content: A machine learning model for workplace analytics
61+
isCorrect: false
62+
explanation: Incorrect. Work IQ is a CLI and MCP server, not a machine learning model.
63+
- content: A CLI and MCP server that connects AI agents to Microsoft 365 data
64+
isCorrect: true
65+
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.
66+
- content: A replacement for Microsoft Teams
67+
isCorrect: false
68+
explanation: Incorrect. Work IQ complements Microsoft 365 services, it doesn't replace them.
69+
- content: A Visual Studio Code extension for building agents
70+
isCorrect: false
71+
explanation: Incorrect. Work IQ is a CLI/MCP server. The Microsoft 365 Agents Toolkit is a VS Code extension.
72+
- content: When should you consider using the Microsoft 365 Agents Toolkit instead of direct publishing from Foundry?
73+
choices:
74+
- content: For all production deployments
75+
isCorrect: false
76+
explanation: Incorrect. Direct publishing is suitable for most production scenarios.
77+
- content: When you need custom SSO, middleware logic, or multi-environment deployment
78+
isCorrect: true
79+
explanation: Correct. The Agents Toolkit is valuable for complex scenarios requiring custom single sign-on, middleware processing, or sophisticated deployment pipelines.
80+
- content: When publishing to shared scope
81+
isCorrect: false
82+
explanation: Incorrect. Both shared and organization scope work with direct publishing.
83+
- content: When your agent doesn't use any tools
84+
isCorrect: false
85+
explanation: Incorrect. The choice between approaches doesn't depend on whether tools are configured.
Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
### YamlMime:ModuleUnit
2+
uid: learn.wwl.integrate-foundry-agent-with-m365.summary
3+
title: Summary
4+
metadata:
5+
title: Summary
6+
description: Summary of integrating Microsoft Foundry agents with Microsoft 365.
7+
ms.date: 02/17/2026
8+
author: ivorb
9+
ms.author: berryivor
10+
ms.topic: unit
11+
ai-usage: ai-assisted
12+
durationInMinutes: 2
13+
content: |
14+
[!include[](includes/9-summary.md)]

0 commit comments

Comments
 (0)