Choose the right platform and harness
Match the agent scenario to the right authoring surface, runtime harness, level of control, integration model and operating environment.
Microsoft Foundry & Copilot Studio training
One agent strategy The right build path
Hands-on training for teams choosing the right platform and harness, then designing, building, evaluating and governing enterprise agents across Microsoft Foundry and Copilot Studio.
The outcome
Build the right agent, not simply the fastest prototype
Ground agents in useful knowledge
Design instructions, knowledge and retrieval around a defined business task instead of building a generic conversational layer.
Connect action safely
Add tools, workflows and enterprise systems with explicit identity, permissions, failure handling and human oversight.
Test before you scale
Use traces, test sets, evaluations and monitoring to move from a promising prototype to an agent the organisation can operate.
Platform choice
Know where each path earns its place
The workshop connects the platforms without pretending they are interchangeable. Teams learn to choose from the scenario outward.
01 / Pro code
Microsoft Foundry
Build with models, agents and code
For teams that need Azure-based control over models, prompt or hosted agents, application code, deployment and observability.
- Model selection and project setup
- Prompt agents and hosted agents
- Agent Framework, LangGraph, OpenAI Agents SDK and custom code
CS / 02
Copilot Studio
Build agents and workflows with low code
For teams extending Microsoft 365 or business processes through managed authoring, knowledge, tools, workflows and channels.
- GitHub Copilot, standard and Copilot chat harnesses
- Instructions, knowledge, tools, skills, memory and connected agents
- Testing, evaluation, publishing, monitoring and administration
Built for
The team around the agent, not one role in isolation
Developers and architects
Understand the full agent lifecycle and where code, Azure services and deeper integration belong.
Makers and automation specialists
Build focused agents and workflows while recognising the identity, data and governance decisions behind them.
Platform and security teams
Set practical boundaries for environments, access, publishing, monitoring and organisational ownership.
Curriculum
From platform decision to governed operation
The final agenda is scoped around the platforms, environments and agent scenarios your organisation intends to use.
Scenario, platform and harness fit
Start with the business task, users and operational boundary before selecting a platform or runtime.
- Agent use-case framing and success criteria
- Foundry, Copilot Studio and Microsoft 365 agent options
- GitHub Copilot, standard and Copilot chat harness selection
Microsoft Foundry foundations
Build an Azure-based agent path with the right project, model and development surface.
- Foundry projects, model selection and portal or code-first delivery
- Prompt agents, hosted agents and managed endpoints
- Framework choice, tools, knowledge, identity and application integration
Copilot Studio foundations
Create a focused agent on the harness that fits how the work should be done.
- Identity, instructions, knowledge, tools, skills, model and memory
- Connected agents, agent flows and orchestration choices
- Preview, evaluation, publishing, channels and monitoring
Knowledge and action
Connect enterprise context and tools without losing control of access or behaviour.
- Grounding, retrieval and Microsoft Foundry Toolbox patterns
- Connectors, APIs, tools, skills and MCP where relevant
- Authentication, permissions and human approval points
Evaluation and observability
Create evidence that an agent is useful, traceable and ready for its intended audience.
- Test cases, test sets and evaluation criteria
- Activity traces, debugging and failure analysis
- Monitoring quality, usage and operational signals
Security and lifecycle
Move from workshop build to a governed release and improvement cycle.
- Identity, RBAC, data policies and environment controls
- Publishing, channels, versioning and application lifecycle
- Responsible AI, ownership and operating guardrails
Programme brief
Scoped around a real agent decision
Every engagement starts with the scenario, participant roles and environment constraints. That determines the platform depth, labs and governance decisions, not a fixed feature checklist.
- Duration
- 2–3 days
- Primary audience
- Developers, architects, makers and platform teams
- Delivery
- Virtual or on-site
- Platform focus
- Microsoft Foundry, Copilot Studio or a connected programme
- Approach
- Hands-on build, evaluation and governance exercises
Practice-informed
Platform depth, translated into team capability
Fedorai founder Arafat Tehsin is a Microsoft MVP in AI, applied AI leader, solution architect and international speaker. The programme combines technical platform depth with the decisions teams face when agents move into real organisations.
About Arafat and Fedorai Questions
What teams usually ask before booking
How long is the Microsoft Foundry and Copilot Studio training?
The focused programme typically runs for two to three days. The final duration depends on the selected platform depth, participant roles, environment readiness and the amount of hands-on build time required.
Does the programme cover both platforms?
Yes, when that supports the team's goals. The programme can connect Microsoft Foundry and Copilot Studio through one agent lifecycle, or go deeper on one platform when the organisation has already chosen its primary build path.
Does the programme cover Copilot Studio harnesses?
Yes. The curriculum can compare the GitHub Copilot harness for reasoning-heavy multistep work, the standard harness for structured and rule-based experiences, and the Copilot chat harness for extending Microsoft 365 Copilot Chat with enterprise knowledge.
Do we need to adopt both Microsoft Foundry and Copilot Studio?
No. A core part of the training is learning when each surface fits. The right choice depends on the scenario, target users, required integrations, engineering control, existing Microsoft estate and governance model.
Can the workshop include Microsoft 365 Copilot agents?
Yes. The Copilot chat harness for extending Microsoft 365 Copilot Chat can be included where it fits the intended users, enterprise knowledge, licensing and distribution model.
Can we use our own tenant, data or business scenario?
Private team engagements can adapt the exercises to your scenario and environment where access, licensing, data protection, confidentiality and workshop setup permit. We confirm those constraints before finalising the agenda.
Is this certification or exam-preparation training?
No. The programme is designed around practical platform decisions, hands-on building and enterprise delivery rather than preparation for a certification exam.