Marketplace Policy

This policy describes the lifecycle of tools published in the Power Platform ToolBox Marketplace. Tool lifecycle status describes the availability and support of a tool package; it does not describe the maturity or compatibility of PPTB APIs.

Tool lifecycle states

Publisher requests and responsibilities

To request a tool status change, reach out in the PPTB Discord server and tag the @TeamMember role. Include the tool name and ID, requested status, reason, effective date, expected retirement date if known, replacement tool or migration guidance if available, compatibility and update impact, and how existing users will be notified.

Publishers are responsible for accurate lifecycle information and for notifying their users through their normal release notes or support channels. Give reasonable advance notice of planned retirement; where practical, provide at least 30 days. If urgent security, legal, safety, or compatibility concerns require faster action, explain the urgency and effective date in the request.

The Marketplace team reviews requests, may ask for clarification, and manages the listing status and discovery visibility. The team may deprecate or retire a tool without a publisher request when necessary to protect users or the service, and may delist a tool immediately for urgent security, legal, or policy reasons.

What users should expect

Deprecation does not itself uninstall a tool or guarantee that it will stop running for users who already installed it. However, continued operation, compatibility, support, and future updates are not guaranteed. Users should review the publisher's migration guidance, move to a recommended replacement when available, and uninstall the tool when it is no longer needed.

Retirement prevents new installations and removes the tool from normal discovery. Existing copies may continue to run locally, but users should not expect further support or updates. Marketplace status changes do not guarantee an individual notification; users should check the listing and publisher announcements.

Lifecycle requests are handled manually while Marketplace lifecycle metadata and dedicated user notifications are being developed. Until then, publishers should not assume that every listing can display all lifecycle details or that users will be notified automatically.

Tool lifecycle vs. API maturity

Tool deprecation and retirement apply to a publisher's Marketplace tool. PPTB API deprecation is a separate compatibility and maturity concern described by the Tool Maturity Model. A tool can be deprecated without a PPTB API change, and an API deprecation does not by itself retire a Marketplace tool.

View Terms of Service