Notitie
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen u aan te melden of de directory te wijzigen.
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen de mappen te wijzigen.
Choose what you want to build, then follow the applicable supported path. If you're building a plugin, follow the plugin lifecycle from planning through monitoring, updates, and retirement.
Choose the applicable journey
| Your goal | Start with |
|---|---|
| Bring supported capabilities together in a plugin for Microsoft experiences | Plugins for Microsoft 365 Copilot |
| Build an app that uses Microsoft 365 work context or Copilot capabilities | Build Copilot-powered apps and agents |
| Build an agent with your own orchestration, models, hosting, or runtime | Custom engine agents |
For a complete comparison, see Ways to extend Microsoft 365 Copilot.
Follow the plugin lifecycle
For a plugin, complete each stage in order.
| Step | Result | Start with |
|---|---|---|
| Prepare to build your plugin | Defined outcome, audience, target experiences, capabilities, tools, dependencies, constraints, and owners | Plan your plugin |
| Build or reuse capabilities | Working components with recorded versions, dependencies, owners, limitations, and development evidence | Build or reuse capabilities for your plugin |
| Package and test | Integrated components and an exact versioned package tested for structure, references, dependencies, permissions, target-experience behavior, and agent quality when required | Integrate capabilities |
| Publish and distribute | The tested plugin published or shared through a supported route, with the destination and next owner recorded | Choose how to publish and distribute your plugin |
| Make available and govern | Intended users can access and use the plugin, required connections work, and applicable controls are applied | Make plugins and agents available and govern access |
| Monitor, update, and retire | Usage and feedback reviewed, behavior evaluated when appropriate, updates tested and released, ownership or access adjusted, and retirement completed safely | Monitor, update, and retire |
Define the required capabilities and target Microsoft experiences before you select a development tool. Then use Choose development tools for your plugin to compare the available authoring and packaging paths, including Microsoft 365 Agents Toolkit for supported Microsoft 365 app packages.
Before implementation, confirm that the required identities, environments, services, permissions, licenses, and owners are available.