Microsoft announced the developer preview of Work IQ Developer Tools, or WIQD, on August 6, 2026. It targets Microsoft 365 Copilot extensibility and is designed to take a plugin from an empty folder to a product that can be published and monitored, rather than simply adding another CLI for scaffolding.
WIQD covers skills, connectors, and declarative agents. Microsoft describes it as an agentic experience: a developer can ask it to create a support-triage agent, add a knowledge-base connector, configure a SKILL.md skill and a remote MCP connector, then validate the package and generate evaluations. The tool is therefore helping an agent build the kind of plugin that agents will later use.
The published lifecycle is create, configure, validate, provision, package, share, ask, eval, publish, and monitor. For enterprise teams, that sequence matters more than scaffolding alone. The difficult part of Copilot extensibility is often the gap between a first demo and the manifest, permissions, deployment, testing, and publishing steps required for a real product.
The developer surface includes an agent plugin, a language server, and machine-readable output. The language server provides live diagnostics for declarative agent manifests, plugin manifests, and adaptive cards. Commands also provide JSON output and stable exit codes so the same workflow can move into CI/CD. During the build phase, WIQD discovers dependencies such as MCP tools, API plugins, agent connectors, and skills, then wires their schemas into the manifest.
Microsoft also treats the plugin as the reusable product unit rather than forcing every capability into one agent. A plugin can contain a declarative agent, SKILL.md skills, remote MCP connectors, and metadata that binds those capabilities into a Microsoft 365 app package. A focused capability can be published to a shared registry and composed into multiple agent experiences.
The quality loop is another central part of the preview. WIQD reads a manifest and generates targeted evaluations in YAML. Developers can run them locally or in CI/CD and compare regressions across runs. After publishing, wiqd agent monitor brings usage, health, and adoption telemetry back to the terminal so teams can feed real usage back into evaluations and republish when needed.
The end-to-end flow still has clear boundaries. Microsoft labels WIQD a developer preview. Publishing to the Microsoft 365 Store through Partner Center is marked as coming soon, and the preview requires Node.js, a Microsoft 365 tenant, and a Copilot license. Centralizing the workflow does not by itself solve tenant permissions, data governance, or production reliability.
The broader signal is that enterprise agent development is moving from “can we build an agent?” to “can we manage an agent product?” Once a plugin has versions, permissions, evaluations, audience targeting, adoption data, and monitoring, its lifecycle needs the same discipline as other enterprise software. That is closer to the practical deployment problem than simply adding another model capability.
