Copilot or an agent?
Options
- 1Copilot in the programs, with clean permissions
- 2An agent in Copilot Studio with sources, actions and triggers
Our recommendation: Copilot, as long as a person triggers the task and uses the result themselves, for instance when summarising, drafting and analysing. An agent, as soon as fixed sources, actions in line-of-business systems or a start without being asked come into play, or several people should do the same task in the same way.
What we advise against: An agent for a task nobody has yet described cleanly by hand. Without sources, permitted actions and a point where a person decides, the test set measures nothing.
Copilot Studio or Microsoft Foundry?
Options
- 1Copilot Studio with connectors, agent flows and MCP
- 2Foundry with model catalogue, Agent Service and your own code
- 3Both, with the agent in Teams as the way into the Foundry application
Our recommendation: Copilot Studio when the agent lives in Teams or Copilot, answers from SharePoint and Dataverse and your business team maintains it itself. Foundry when a specific model, a workflow in code, processing without a chat, an interface outside Microsoft 365 or private networks are required. Both together when employees should stay in Teams while the work behind it happens in an application.
What we advise against: Foundry for an agent the business team wants to adjust itself next week, or Copilot Studio for a pipeline that processes documents in batches overnight.
Prompt agent or hosted agent in Foundry?
Options
- 1A prompt agent from instructions, model and tools, without code of your own
- 2A hosted agent with your code in a container, with Agent Framework or LangGraph
- 3A pipeline without an agent that runs in batches
Our recommendation: A prompt agent when instructions, a model and tools from the toolbox carry the task and your team should maintain it in the portal. A hosted agent when the workflow has several stages, waits for approvals or needs libraries that exist only in code. A pipeline without an agent when nobody talks to the system and documents run through in batches overnight.
What we advise against: A hosted agent for a task a prompt agent solves in the portal; every line of code wants to be operated.
Who builds, and who maintains?
Options
- 1The business team in Copilot Studio
- 2Your developers or we on Foundry
- 3Both: the business team in front, development behind it
Our recommendation: The business team maintains what lives in the Copilot Studio interface: sources, topics, connectors, agent flows. Developers maintain code, pipelines and hosted agents on Foundry. In combined solutions the agent in Teams belongs to the business team and the application behind it to development, with one shared test set.
What we advise against: An agent nobody maintains after handover. Sources go stale, instructions stay as they were, and the test set no longer runs.