Luke Steward

A practical map of Microsoft 365 Copilot agent types, how you deploy them (including across customer tenants if you are an MSP), and when to pick each one, as of August 2026. Spoiler from my own delivery work: Copilot Studio declarative agents (agents for Microsoft 365 Copilot) are the path I enjoy building most for customers. The Studio tool and knowledge surface is wide enough for real work, and you still stay on Copilot’s orchestrator.

Microsoft documents two approaches (declarative vs custom engine). Everything else is a builder, runtime, or legacy name. Confusing those three is why “classic agent,” “Copilot Studio declarative,” and “Agents Toolkit” feel like four different products fighting in a trench coat.

Connect CIPP to Microsoft Copilot Studio as a declarative agent over the CyberDrain MCP endpoint, so engineers can work agentically against tenant data through CIPP.

This is a proof of concept. The companion master prompt and skills are only minimally trained, cover a small skillset, and need further training before you treat them as production-ready. Official CIPP API and MCP setup lives in the CIPP API documentation; this post covers Copilot Studio declarative-agent wiring on top of that.

Every so often a project comes out of a conversation you weren't even trying to turn into a project. JayQuery is one of those. It's a free Chrome and Edge extension that checks a website's DMARC, SPF, and DKIM (plus a handful of the DNS records around them) the moment you land on a tab, and scores what it finds out of 10. This post is the story of why it exists and what it's actually for.

This project provides two versions of a PowerShell script to ship logs from Cisco Umbrella Portal to Huntress using the HEC (HTTP Event Collector) format.