Muistiinpano
Tämän sivun käyttö edellyttää valtuutusta. Voit yrittää kirjautua sisään tai vaihtaa hakemistoa.
Tämän sivun käyttö edellyttää valtuutusta. Voit yrittää vaihtaa hakemistoa.
Retire a plugin when people should no longer use it. Stop distribution and access, clean up resources used only by the plugin, and keep shared resources working.
The plugin owner coordinates retirement. Microsoft 365 administrators manage organizational access. Service owners clean up connections and external services.
Before you begin
Decide whether you're retiring the plugin in your organization or for all customers. Ending a Marketplace offer and removing access in customer organizations are separate actions.
Identify:
- The plugin name and active package versions.
- How users received it: sharing, administrator upload, or Microsoft Marketplace.
- The affected users, organizations, and Microsoft 365 experiences.
- The connections and services it uses, including those shared with other solutions.
- The retirement date and owners responsible for completing the work.
Keep any records your organization's retention policies require.
Plan the retirement
- List every place where the plugin is published, shared, or installed. Check the plugin's status, availability, and installation in Agents > Tools > Plugins; see Manage plugin availability for users.
- Choose the actions needed to stop distribution and access.
- Identify resources to remove and shared resources to preserve.
- Assign an owner and completion date to each action.
- Notify affected users and support teams. Include the retirement date and any replacement they should use.
For administration locations, see the Manage plugins with Microsoft Agent 365 administration map.
Stop distribution and access
Complete the actions needed for your retirement scope. You might need more than one. For example, block access and then remove an administrator installation.
| What you need to do | Action | Who acts |
|---|---|---|
| Block access in your organization | Block the plugin in Agents > Tools > Plugins. | Microsoft 365 administrator |
| Remove an administrator-deployed installation | Uninstall the plugin. Also restrict availability or block access if users must not add it again. | Microsoft 365 administrator |
| Delete a package uploaded by your organization | Delete the uploaded package. This action isn't available for Marketplace packages. | Microsoft 365 administrator |
| Stop direct sharing | Follow the authoring tool's removal procedure, where supported. Check whether recipients retain access and arrange blocking when needed. For Cowork, see Block a plugin that's already been shared. | Plugin owner and administrator |
| End public distribution | Follow the applicable Partner Center offer procedure; start from Publish your plugin through Microsoft Marketplace. Notify customers and coordinate retirement of existing installations with their administrators. | Publisher and customer administrators |
After applying the controls:
- Confirm that the plugin is blocked, removed, or no longer shared as planned.
- Review plugin access requests in Agents > Tools > Requests and assign an owner to resolve any that remain.
- Check for any remaining distribution or access paths.
Blocking can take effect differently across Microsoft 365 experiences. In Cowork, a block applies to new conversations; conversations already using the plugin continue until they end. See Block a plugin that's already been shared.
Blocking the package also blocks its included agents, but leaves associated MCP servers and connectors available to other plugins. See Block a tool. If an agent also exists separately with its own Agent Registry controls, check the applicable agent actions.
Clean up resources
Blocking or removing the plugin doesn't revoke consent, remove indexed data, or stop external services. For each resource, ask: Does another solution still need it?
| If the resource is... | Do this |
|---|---|
| Used only by the retired plugin | Have its owner revoke access and remove or disable it through the owning product. |
| Shared with another solution | Keep it working. Remove only access specific to the retired plugin. |
| Required for retention or another documented reason | Retain it with appropriate access restrictions, an owner, and a recorded reason. |
Review:
- Connections, permissions, consent, and service accounts. For user connector sign-in and consent in Cowork, see Manage connector authentication.
- App registrations, secrets, and certificates.
- Remote MCP servers and other hosted services. Before you block an MCP server, confirm that other plugins don't depend on it.
- Connector connections and indexed data. To review connection state before cleanup, see View connection details.
- Infrastructure, scheduled jobs, alerts, and support processes.
For an alpha Work IQ Dev Tools project, the plugin guide describes wiqd plugin delete as tearing down resources provisioned for the selected environment. Check the command's effects before running it, then verify and clean up any remaining package records, connections, credentials, and external services through their owning products.
Verify retirement
- Ask a user who previously had access to try the plugin in each affected Microsoft 365 experience. Test in a new conversation; check active sessions according to that experience's documented behavior.
- Confirm that distribution and sharing have stopped within the agreed scope.
- Ask the administrator to confirm the intended plugin status in Agents > Tools > Plugins and review any pending requests in Agents > Tools > Requests.
- Confirm that plugin-specific access and resources have been removed, disabled, or retained under a documented exception.
- Test that shared connections and services still work for other solutions.
- Archive the source, final package, and release records according to your organization's requirements.
Retirement is complete when access ends within the agreed scope, distribution stops as planned, and resource cleanup is complete. Any retained resources and unresolved requests must have an owner and a documented next action.
Record the retirement
Record:
- Plugin name, versions, retirement scope, and date.
- Distribution and access actions completed.
- Resources removed, disabled, or retained.
- Verification results.
- Remaining exceptions, owners, and follow-up dates.