OneRange

Microsoft Copilot for Developers: Mastery — Extending Copilot

Extend Copilot with current connectors, declarative agents/API actions and Teams integrations, backed by code-enforced authorization and tenant governance

What this course covers

The course runs across 9 topics, each one a short adaptive session rather than a recorded lecture. The tutor explains the idea, works an example, checks understanding, and adjusts the next step to the answer given.

  • Microsoft 365 Copilot extensibility choices — Distinguish declarative agents, custom engine agents, Studio and Teams extensions. Choose by requirements and available approvals.
  • Copilot connectors: synced and federated — Microsoft 365 Copilot connectors: synced external content indexed into Microsoft Graph; federated query-time retrieval via MCP where supported. Preserve source ACLs.
  • Graph indexing and access boundaries — Plan schema, identities, external items/ACLs and incremental updates; never use prompt-level tenant filtering as authorization.
  • Declarative agents and API plugins — Define instructions/knowledge and supported action/plugin manifests with OpenAPI schemas; verify current manifest support instead of old generic plugin promises.
  • Teams extensions and deployment — Design a Teams message extension/integration contract and approved packaging; verify supported Copilot integration on current docs. No forced live tenant install.
  • OAuth and application-owned authorization — Keep secrets in approved secret storage, validate scopes/tenant/action arguments and obtain approval before consequential writes.
  • Tenant administration and governance — Separate permissions, publishing approval, Purview/data policies, auditing and lifecycle ownership; do not change a real tenant.
  • Resilience and operations — Bound retries, idempotency, safe errors and minimal logs. Monitor authorized usage and source freshness without exposing secrets.
  • Capstone: guarded extensibility handoff — Implement a fake action authorizer, mock connector ACL mapping and deterministic tests, plus manifests/Teams/admin governance plan.

Skills you build

Results are measured against named skills in the OneRange taxonomy of more than 10,000 skills, so a manager sees proficiency per skill rather than a completion tick.

Who it is for

Software developers and technical builders. The material is pitched at expert level, and takes roughly 180 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

It sits in the Tool: Microsoft Copilot track of the Vero AI Catalog, and can be assigned to one person, a team, or the whole company.

How it is delivered and assessed

Delivery is conversational and interactive. There is no video to sit through and no slide deck to click past.

Understanding is checked with a code assessment of 5 items, with a pass mark of 70%.

Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Also in this track

Related

Frequently asked questions

How long does this course take?

It runs roughly 180 minutes at a typical pace. Because every session adapts, someone who already knows a topic moves through it quickly instead of sitting through an explanation they do not need.

How is it assigned to a team?

An administrator assigns it from the Vero dashboard to one person, a team, a department or the whole company, and sees progress and results per person and per skill.

Can we customise it with our own documents and terminology?

Yes. Administrators can copy this course into their own library and adapt it — edit the outline, change the duration, swap the assessment format, or ground it in internal documentation so answers cite the company's own source material.

Course code TUL-COP-DEV-301.