Four Microsoft ways to create agents, from no-code to pro-code
Diesen Beitrag auf Deutsch lesen
SharePoint agents, Agent Builder, Copilot Studio and Microsoft Foundry serve different creators, complexity levels and control needs.
Original article from October 1, 2026: Cuatro formas de crear agentes en Microsoft, by Ramón Rautenstrauch, on Consultor 365. Read the original
This is our own summary, not a republication or full translation.
TL;DR
Microsoft presents four agent entry points: SharePoint agents for existing content, Agent Builder for natural-language no-code agents, Copilot Studio for actions and integrations, and Microsoft Foundry for deeper model, code and architecture control.
Why it matters
- Makers: Use SharePoint agents or Agent Builder for knowledge-focused scenarios, then consider Copilot Studio when the agent must perform actions.
- Admins/IT: Match each option to the required integrations, autonomy, governance and development control instead of treating them as interchangeable.
- Leadership/Business: Decide who should create each agent and provide the appropriate entry point, from no-code experiences to professional development.
Frequently asked questions
When should I use Copilot Studio instead of Agent Builder?
Use Copilot Studio when the agent must connect to external systems, execute actions, trigger workflows or use APIs. Agent Builder suits simpler projects.
What can SharePoint agents use as knowledge sources?
SharePoint agents can use selected SharePoint sites, libraries, folders or files as an agent knowledge base without programming.
What development controls does Microsoft Foundry provide for agents?
Microsoft Foundry supports model, framework, runtime architecture and integration choices, alongside APIs, SDKs, CI/CD, observability and deployment practices.