Summary
You now compare Power Platform extension options across the client, server, cloud, connector, and agent runtimes, matching each choice to a specific requirement in the equipment-provisioning scenario. You also recognize how solutions, publishers, and components package those choices so they move between environments as one coherent unit.
What you learned
- Every piece of extension logic runs in one of five runtimes: client, server, cloud, connector, or agent. Recognizing where logic belongs, and what triggers it, is the first decision you make before picking a specific technology.
- Client scripts, Power Apps component framework (PCF) controls, code apps, and generative pages each fit a different need in the client and application runtime. Needs range from quick field validation to a reusable control to natural-language page scaffolding.
- Plug-ins, custom APIs, cloud flows, Azure Functions, custom connectors, MCP servers, and Copilot Studio or Microsoft Foundry agents each answer a different server, cloud, connector, or agent requirement. Requirements range from logic that must fire automatically on every record change to a tool surface several agents share.
- Solutions package tables, forms, scripts, plug-ins, cloud flows, and every other component together under a publisher identity. Moving from an editable unmanaged solution to a locked managed solution carries that whole set safely from development into test and production.