Each business skill describes a specific process \u2014 the detailed steps-by-step instructions involved, the information required, and the business rules that apply. Agents connected to the Dataverse MCP server<\/a> discover relevant skills automatically and use them to complete tasks according to your organization\u2019s standards. <\/p>\n\n\n\n Because skills are defined once and stored centrally in Dataverse, any agent can use them \u2014 whether it\u2019s running in Copilot Studio, GitHub Copilot, VS Code, Azure AI Foundry, or any MCP-compatible client. When multiple agents reference the same skill, they follow the same process. Update the skill, and the change applies everywhere \u2014 no need to track down and patch individual agent configurations.<\/p>\n\n\n Skills are fully governed with built-in sharing and visibility controls, and they\u2019re solution-aware \u2014 which means you can add them to your power platform solutions and move them across environments as part of your existing ALM process. <\/p>\n\n\n\n Previously, asking an agent to follow a multi-step business process \u2014 like assigning vendors to open issues \u2014 meant the agent had no context for how<\/em> your team actually handles that work. The result was generic at best and unable to adapt to the changing processes. <\/p>\n\n\n\n With business skills, the same request produces a precise, grounded result. The agent discovers the relevant business skill, follows your documented process step by step, and completes the task across your Dataverse data \u2014 no custom code, no workflow builder, no app switching. <\/p>\n\n\n\n![\"Build](\"https:\/\/cm-edgetun.pages.dev\/en-us\/power-platform\/blog\/wp-content\/uploads\/2026\/04\/image-50-1024x480.webp\")
<\/figure>\n\n\n\nSeeing it in action <\/h2>\n\n\n\n