Set up WorkIQ Copilot and query it safely
Practical guide to the plugin, sign-in, precise Microsoft 365 queries, and privacy boundaries.
- Skill Road
- Set up WorkIQ Copilot and query it safely
Published on 09.09.2026
WorkIQ Copilot combines the guidance in GitHub's official repository with WorkIQ access to Microsoft 365 context. According to the provider, the capability is in Public Preview.
Check prerequisites
Use GitHub Copilot CLI and confirm that your Microsoft 365 tenant allows WorkIQ. First use may require accepting the EULA, completing browser sign-in, and obtaining administrator consent. Decide in advance which account and tenant should be used.
Use the preferred plugin path
The official skill file recommends the WorkIQ plugin for Copilot CLI. Add the official Copilot plugin marketplace, install WorkIQ, and restart Copilot CLI afterward. Use the current syntax and plugin names from the GitHub source rather than copying commands from old blog posts.
Narrow the first query
Start with a harmless read-only question and include a timeframe, topic, and source. A suitable request might ask for your meetings during the current week or recent documents about one clearly named project. Compare the answer with known information before turning it into tasks, recommendations, or external messages.
Alternatives and MCP
When using another MCP-capable client, Microsoft's official guide describes the standalone WorkIQ CLI and MCP route. The WorkIQ runtime must be available and sign-in must occur in the intended tenant. This catalog entry does not describe secret credentials and deliberately contains no real tokens.
Privacy and approvals
Request only the data needed for the current task. Do not share complete email or Teams content when an abstract summary is sufficient. Review every answer for confidential information and follow your tenant's retention, access, and policy requirements. Mutating follow-up actions, such as sending a message or creating a meeting, should happen only after clear human confirmation.
Frequently asked questions
Common questions concern preview status, administrator consent, and the boundary between the skill and the service. The FAQ attached to this guide summarizes the official boundaries and does not replace current GitHub and Microsoft documentation.
Frequently asked questions
Is WorkIQ Copilot a separate MCP server?
No. This entry describes an instructional skill from GitHub awesome-copilot. Microsoft 365 context is accessed through WorkIQ CLI or the WorkIQ MCP server.
Why might first use require consent?
The official guidance says that an EULA, browser sign-in, and Microsoft 365 administrator consent may be required. The skill cannot bypass tenant controls.
How should I handle confidential results?
Request only necessary context, review the answer before sharing it, and follow tenant policies. Mutating follow-up actions require human confirmation.