Build your first action for declarative agents with API plugin by using Visual Studio Code: Review
Named reviewer score2.5/ 5
Teaching2.0
Hands-on3.0
Freshness4.0
Value3.0
Career fit2.0
Reviewed by Sofia R. · CS student and self-directed learner
Provider:Microsoft LearnFormat: Self-paced reading module with a single hands-on exercise.Time: About 30-45 minutes, depending on setup.Price:The module is free. Any associated certification exams may have a cost. — Check current pricing on the official site.
This catalog page is listed from an official provider feed. It is not independently verified for search indexing yet.
It's a quickstart guide, not a tutorial. It shows you the 'what' (a JSON file) but skips the 'why' and the 'how'. Useful only if you're already in the M365 ecosystem and need the specific file structure.
Decision summary
2.5/5 Last verified: August 31, 2026
Best for
Developers who already have a Microsoft 365 Developer tenant and just need a quick 'hello world' for declarative agent plugins.
Watch for
The exercise is just a copy-paste of a large JSON block; you don't build the logic.
Teaching2.0
Hands-on3.0
Freshness4.0
Value3.0
Career fit2.0
Who it's for
Developers who already have a Microsoft 365 Developer tenant and just need a quick 'hello world' for declarative agent plugins.
Who should skip it
Absolute beginners to APIs or anyone without an M365 developer environment.
Pros
Provides a concrete, step-by-step recipe to build a minimal API plugin.
Uses current tools (VS Code, Teams Toolkit v5).
The exercise sandbox gives you a working dev environment without local setup.
Points to the official OpenAPI spec for the 'why' behind the JSON structure.
Cons
The exercise is just a copy-paste of a large JSON block; you don't build the logic.
Doesn't explain what a 'declarative agent' is conceptually or how it differs from other agents.
Relies heavily on having a pre-existing, correctly configured M365 Developer tenant, which is a huge barrier.
The 'Knowledge Check' is trivial and doesn't test understanding.
That giant manifest JSON in the exercise unit is pretty much the entire 'course'. I was expecting to build an API or at least write some functions, but the main task is just copying their pre-written OpenAPI description into a file. The Teams Toolkit sets up the scaffolding, which is nice, but then you just paste. I finished the exercise and felt like I hadn't learned how anything actually worked, just how to follow a recipe.
My main frustration is the unstated prerequisite: a fully working Microsoft 365 Developer tenant. The module links to setting one up, but that's a whole separate project that can take hours or even days to get provisioned correctly. Without it, you can't test the plugin in Copilot, which is the entire point. So the advertised 30 minutes is misleading; it's 30 minutes if you've already spent a day getting your dev environment ready.
It feels like documentation that was repurposed into a 'learning module'. It shows you the final artifact—the declarative JSON manifest—but doesn't teach the design principles behind it. Why does the agent need `descriptionForModel`? How do you decide what goes into the operation details? The module doesn't explore this. It's a quick win for Microsoft to add a module to their catalog, but not a great learning experience. I had to go find the Adaptive Cards module afterward to make any sense of the UI part.
Last verified: August 31, 2026. We re-check course details periodically — see our methodology. Pricing and availability can change; always confirm on the official site.
Community reviews
No community reviews yet — be the first to share your experience.
Reader-submitted experiences, separate from the named reviewer score above.
Sign in to write a review
Community reviews are open to registered readers — it keeps them real.