This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
What Azure resource does the Foundry portal automatically create when you publish an agent to Microsoft Teams?
Azure Functions
Azure Bot Service
Azure Cosmos DB
Azure Logic Apps
What is the main difference between shared scope and organization scope when publishing an agent?
Shared scope requires more Azure resources
Organization scope requires admin approval before the agent is available to all users
Shared scope only works in the Foundry playground
Organization scope provides better agent performance
What happens to tool permissions when you publish an agent from Foundry to Teams?
Permissions are automatically transferred to the published agent
Tools are disabled after publishing
The published agent gets a new identity and needs permissions reassigned
Permissions only work in organization scope
What is Microsoft Work IQ?
A machine learning model for workplace analytics
A CLI and MCP server that connects AI agents to Microsoft 365 data
A replacement for Microsoft Teams
A Visual Studio Code extension for building agents
When should you consider using the Microsoft 365 Agents Toolkit instead of direct publishing from Foundry?
For all production deployments
When you need custom SSO, middleware logic, or multi-environment deployment
When publishing to shared scope
When your agent doesn't use any tools
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?