|
| 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. |
0 commit comments