Browse .github/plugins/dataverse/skills/ for the full source.

Prerequisites

A Microsoft Dataverse environment, available through Power Apps, Dynamics 365, or Power Platform plans, or via the free Power Apps Developer Plan.

Install

GitHub Copilot

/plugin install dataverse@awesome-copilot

Claude Code

/plugin install dataverse@claude-plugins-official

Verify the install

After installation, ask your agent:

"Connect to Dataverse"

The dv-connect skill walks through tool checks, authentication, and MCP registration. When it finishes, you should see a dataverse-<orgname> MCP server registered with your agent, and pac auth list should show your active environment.

Try these prompts

After the connect flow finishes, describe what you want — the plugin picks MCP, the Dataverse CLI, the Python SDK, or PAC CLI for you.

• "Show me my open deals over $100K closing this quarter"
• "Import this CSV into the contacts table"
• "Create a customer feedback table with name, rating, and comment columns"
• "Pull the schema and pack it into a solution"
• "Bulk delete activities older than 2024"
• "Add a teammate to the sales team on the dev environment"

Safety & Security

The plugin is designed around a least-privilege model — it cannot exceed the permissions of the authenticated user. Key safeguards:

• MCP authorization — MCP access requires developer auth, tenant admin consent, and per-environment allowlisting; other plugin tools (SDK, PAC CLI) authenticate directly.
• Security role enforcement — every API call is authorized server-side by Dataverse; the plugin cannot bypass or escalate permissions.
• Application-level telemetry only — outbound Dataverse requests may carry application metadata (plugin / version / skill / agent labels) so server-side dashboards can attribute traffic. No prompts, tool arguments, or record data are transmitted.
• Token security — credentials are stored in your OS native credential store or held in memory only; never passed to external services.

For the full safety model — including confirmation flows, logging, irreversible operation handling, and planned improvements — see docs/safety-and-guardrails.md.

Contributing

We welcome contributions — new skills, improvements to existing ones, and bug fixes. See CONTRIBUTING.md for guidelines and local-development instructions.

Trademarks

This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.

License

This project is licensed under the MIT License.

Code of Conduct

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.