Skip to content

Oskar Busch-Jensen Recruit Completion Submission #740

@BoskarEmul

Description

@BoskarEmul

Curriculum Completion Validation

  • I verify that I have completed the Agent Academy - Recruit curriculum.

Solution Verification

  • I verify that I have uploaded a screenshot of the Agent configuration with my environment name shown into the field below.
  • I verify that I have uploaded a screenshot of the final solution file with my environment name shown into the field below.

Final Solution Screenshots

Image Image

Key Learnings and Takeaways

What the Recruit path covers
• The missions have equipped me to:
o Understand what “agents” are in the context of Copilot Studio.
o Explore how large language models (LLMs), retrieval-augmented generation (RAG), and orchestration come together to form an agent.
o Build both declarative and custom agents.
o Enhance agents with features like Topics, Adaptive Cards, Agent Flows and event triggers.
o Deploy agents to platforms like Microsoft Teams and Microsoft 365 Copilot.
o Securing Your Recruit Badge – earn your badge once completed.

Key takeaways
• Agents aren’t just chatbots: The material emphasises that in this context, an “agent” is more than a simple conversational interface — it involves grounding in knowledge sources, orchestration of workflows, integration of UI (Adaptive Cards), and event-based logic.
• Declarative vs Custom Agents: The path guides you through both simpler declarative agents (prompt-based) and more advanced custom agents built from your own knowledge sources. This is important because you’ll often start simple and then evolve.
• Modular building blocks: The components “knowledge”, “skills”, “autonomy” (from the fundamentals lesson) suggest that building an agent is modular: you define what the agent knows, what it can do, and how autonomous it is (triggered by events vs purely reactive).
• UI and workflow matter: It’s not just about the LLM replying; you also craft UI elements (Adaptive Cards), define flows (backend logic) and use triggers (user input or events). That elevates the agent from simple Q&A to integrated enterprise-grade tool.
• Deployment and lifecycle: The path covers not just build, but also packaging (solutions), deployment (Teams / 365 Copilot), licensing, and release (badge). That means you learn the full lifecycle of agent development, not just proof-of-concept.
• Skill integration: For people familiar with Microsoft ecosystems (SharePoint, Power Platform, Power Fx) this leverages that existing skillset. So if you're already working in Microsoft 365 environment, this is a natural fit.
• Learning by doing: The structure being “missions” indicates a hands-on approach. The emphasis is on building actual agents rather than just reading conceptual slides.

Challenges Faced

During "Mission 09: Add an agent flow to your Topic for automation". I had issues with selecting the "DeviceSharePointId" in the Dynamic Content.
It said that I had no Dynamic Content available. (This was not an issue anywhere else)

Image

Final Thoughts

I think it was fine. As someone with minimal coding-experience it was easy to follow and understand the guide.

Badge validation form

  • I verify that I have completed the badge validation form.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions